Michael Gerz wrote:
Are there any known showstopper ATM? I intend to have a second look at
the plain text output but this can wait (marginal changes).
For the final release we need to have a look at CJK, since the old hacks no
longer work (see http://bugzilla.lyx.org/show_bug.cgi?id=3043).
Georg Baum wrote:
Michael Gerz wrote:
Are there any known showstopper ATM? I intend to have a second look at
the plain text output but this can wait (marginal changes).
For the final release we need to have a look at CJK, since the old hacks no
longer work (see
On Mon, Jan 22, 2007 at 12:06:06AM +0100, Enrico Forestieri wrote:
In the past we were moving to absolute paths
wherever possible in order to get rid of the Path class that is simply too
confusing to use.
Really? I find it quite clever ;-)
I'd be more likely to agree if it was named
Michael Gerz wrote:
> Are there any known showstopper ATM? I intend to have a second look at
> the plain text output but this can wait (marginal changes).
For the final release we need to have a look at CJK, since the old hacks no
longer work (see http://bugzilla.lyx.org/show_bug.cgi?id=3043).
Georg Baum wrote:
Michael Gerz wrote:
Are there any known showstopper ATM? I intend to have a second look at
the plain text output but this can wait (marginal changes).
For the final release we need to have a look at CJK, since the old hacks no
longer work (see
On Mon, Jan 22, 2007 at 12:06:06AM +0100, Enrico Forestieri wrote:
> > In the past we were moving to absolute paths
> > wherever possible in order to get rid of the Path class that is simply too
> > confusing to use.
>
> Really? I find it quite clever ;-)
I'd be more likely to agree if it was
On Sunday 21 January 2007 8:05:24 pm Enrico Forestieri wrote:
Currently, a converter path cannot contain non-ascii characters on systems
not using utf8 as the local encoding. Moreover, arguments are also passed
in utf8 encoding. This is clearly wrong and produces assertions, eg. on
Windows but
On Tue, Jan 23, 2007 at 05:47:14PM +, José Matos wrote:
On Sunday 21 January 2007 8:05:24 pm Enrico Forestieri wrote:
Currently, a converter path cannot contain non-ascii characters on systems
not using utf8 as the local encoding. Moreover, arguments are also passed
in utf8 encoding.
Enrico Forestieri schrieb:
[Personal note: Trying to understand what needs to be done before declaring
a freeze period before beta release.]
I hope this is not to late ;-)
Jose, please wait for a day or two. I have some important CT patches.
Michael
On Tuesday 23 January 2007 7:30:10 pm Michael Gerz wrote:
Jose, please wait for a day or two. I have some important CT patches.
I am searching for feedback, so no problem, I will wait. :-)
I just want to give a subtle sign that we should prepare for a beta. :-)
Michael
--
José Abílio
José Matos schrieb:
On Tuesday 23 January 2007 7:30:10 pm Michael Gerz wrote:
Jose, please wait for a day or two. I have some important CT patches.
I am searching for feedback, so no problem, I will wait. :-)
I just want to give a subtle sign that we should prepare for a beta.
On Tuesday 23 January 2007 9:37:24 pm Michael Gerz wrote:
Before the beta, we should have another look at Status.15x. Those bugs
that haven't been fixed yet should be added to bugzilla, and Status.15x
should be removed.
I agree.
We should also decide on the LyX installer before the beta
On Sunday 21 January 2007 8:05:24 pm Enrico Forestieri wrote:
> Currently, a converter path cannot contain non-ascii characters on systems
> not using utf8 as the local encoding. Moreover, arguments are also passed
> in utf8 encoding. This is clearly wrong and produces assertions, eg. on
> Windows
On Tue, Jan 23, 2007 at 05:47:14PM +, José Matos wrote:
> On Sunday 21 January 2007 8:05:24 pm Enrico Forestieri wrote:
> > Currently, a converter path cannot contain non-ascii characters on systems
> > not using utf8 as the local encoding. Moreover, arguments are also passed
> > in utf8
Enrico Forestieri schrieb:
[Personal note: Trying to understand what needs to be done before declaring
a freeze period before beta release.]
I hope this is not to late ;-)
Jose, please wait for a day or two. I have some important CT patches.
Michael
On Tuesday 23 January 2007 7:30:10 pm Michael Gerz wrote:
>
> Jose, please wait for a day or two. I have some important CT patches.
I am searching for feedback, so no problem, I will wait. :-)
I just want to give a subtle sign that we should prepare for a beta. :-)
> Michael
--
José
José Matos schrieb:
On Tuesday 23 January 2007 7:30:10 pm Michael Gerz wrote:
Jose, please wait for a day or two. I have some important CT patches.
I am searching for feedback, so no problem, I will wait. :-)
I just want to give a subtle sign that we should prepare for a beta.
On Tuesday 23 January 2007 9:37:24 pm Michael Gerz wrote:
> Before the beta, we should have another look at Status.15x. Those bugs
> that haven't been fixed yet should be added to bugzilla, and Status.15x
> should be removed.
I agree.
> We should also decide on the LyX installer before the
Enrico Forestieri wrote:
On Sun, Jan 21, 2007 at 10:41:29PM +0100, Georg Baum wrote:
Why non-absolute paths?
There's a comment in converter.C about the fact that some converters can
only output files to the current directory, so makeRelPath is used with
first and second arguments as utf8
On Mon, Jan 22, 2007 at 03:44:44PM +0100, Georg Baum wrote:
Enrico Forestieri wrote:
On Sun, Jan 21, 2007 at 10:41:29PM +0100, Georg Baum wrote:
In the past we were moving to absolute paths
wherever possible in order to get rid of the Path class that is simply
too confusing to use.
Enrico Forestieri wrote:
> On Sun, Jan 21, 2007 at 10:41:29PM +0100, Georg Baum wrote:
>> Why non-absolute paths?
>
> There's a comment in converter.C about the fact that some converters can
> only output files to the current directory, so makeRelPath is used with
> first and second arguments as
On Mon, Jan 22, 2007 at 03:44:44PM +0100, Georg Baum wrote:
> Enrico Forestieri wrote:
>
> > On Sun, Jan 21, 2007 at 10:41:29PM +0100, Georg Baum wrote:
> >> In the past we were moving to absolute paths
> >> wherever possible in order to get rid of the Path class that is simply
> >> too
Currently, a converter path cannot contain non-ascii characters on systems
not using utf8 as the local encoding. Moreover, arguments are also passed
in utf8 encoding. This is clearly wrong and produces assertions, eg. on
Windows but also on Solaris when using a locale different from utf8.
I had a
Enrico Forestieri wrote:
Currently, a converter path cannot contain non-ascii characters on systems
not using utf8 as the local encoding. Moreover, arguments are also passed
in utf8 encoding. This is clearly wrong and produces assertions, eg. on
Windows but also on Solaris when using a locale
On Sun, Jan 21, 2007 at 10:41:29PM +0100, Georg Baum wrote:
Enrico Forestieri wrote:
I had a look at the code and come to the conclusion that the FileName
class with its toFilesystemEncoding method is not of help here. This
is because we have to also deal with non-absolute paths and some
Currently, a converter path cannot contain non-ascii characters on systems
not using utf8 as the local encoding. Moreover, arguments are also passed
in utf8 encoding. This is clearly wrong and produces assertions, eg. on
Windows but also on Solaris when using a locale different from utf8.
I had a
Enrico Forestieri wrote:
> Currently, a converter path cannot contain non-ascii characters on systems
> not using utf8 as the local encoding. Moreover, arguments are also passed
> in utf8 encoding. This is clearly wrong and produces assertions, eg. on
> Windows but also on Solaris when using a
On Sun, Jan 21, 2007 at 10:41:29PM +0100, Georg Baum wrote:
> Enrico Forestieri wrote:
> > I had a look at the code and come to the conclusion that the FileName
> > class with its toFilesystemEncoding method is not of help here. This
> > is because we have to also deal with non-absolute paths
28 matches
Mail list logo
