"Asger K. Alstrup Nielsen" wrote:
> However, if the toolkit (or any other external component) can not
> handle Unicode, we will have the code in LyX to convert to whatever is
> appropriate.
XForm just only cannot support Unicode, or it cannot support multi-byte
in general? Oh, by the way,
> > Concerning the multi-byte encoding: We should have a discussion
>
> May I know what this "last year's argument" is? I joined this list
> for less than one month.
The argument of last year is to use Unicode as the document encoding
internally in LyX. Also, there is code in the old devel
Andre' Poenitz wrote:
> Concerning the multi-byte encoding: We should have a discussion
> whether
> it is sensible to use Unicode internally. The world is changing and
> last
> years' arguments won't fit anymore.
May I know what this "last year's argument" is? I joined this list
for less t
On Wed, 15 Dec 1999, Greg Lee wrote:
>
> On Wed, 15 Dec 1999, Asger K. Alstrup Nielsen wrote:
>
> > > Surely those voices didn't mean paragraph-level support without
> > > also sentence- and word-level support. When you cite from a
> > > different language, the citation is obviously not always
"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| Lgb, how long will it take to create those branches and give
| the relevant people write access to the repository?
To crate a branch takse close to no time, to give people asscess takes
longer. And a screening process is also needed.
In a
On Wed, 15 Dec 1999, Asger K. Alstrup Nielsen wrote:
> > Surely those voices didn't mean paragraph-level support without
> > also sentence- and word-level support. When you cite from a
> > different language, the citation is obviously not always
> > going to be a separate paragraph.
>
> As it
> Surely those voices didn't mean paragraph-level support without
> also sentence- and word-level support. When you cite from a
> different language, the citation is obviously not always
> going to be a separate paragraph.
As it happens, sub-paragraph-level support is markedly more
difficult tha
On Wed, 15 Dec 1999, Asger K. Alstrup Nielsen wrote:
...
> not affect the left-to-right 8-bit languages, except maybe for a
> small performance penalty. However, several voices say that
> paragraph-level language support is important, so it seems that
Surely those voices didn't mean paragraph-l
On Wed, 15 Dec 1999, Jules Bean wrote:
> My instinct says that most people aren't going to care in the slightest
> about a doubling of internal buffer sizes. The combination of cheap
> memory, cheap hard disks, and sensible VM systems makes this not much of
> an issue, IMO.
Can't you make it a
> My instinct says that most people aren't going to care in the slightest
> about a doubling of internal buffer sizes. The combination of cheap
> memory, cheap hard disks, and sensible VM systems makes this not much of
> an issue, IMO.
*grin* Well, I did not want to write obvious things ;-)
And
> "Jules" == Jules Bean <[EMAIL PROTECTED]> writes:
Jules> On Wed, 15 Dec 1999, Andre' Poenitz wrote:
>> Concerning the multi-byte encoding: We should have a discussion
>> whether it is sensible to use Unicode internally. The world is
>> changing and last years' arguments won't fit anymore.
On Wed, 15 Dec 1999, Andre' Poenitz wrote:
>
> Concerning the multi-byte encoding: We should have a discussion whether
> it is sensible to use Unicode internally. The world is changing and last
> years' arguments won't fit anymore. We could get rid of almost all of
> the encoding stuff at the pr
> I disagree. Merging branches after a year or so of development in these
> not-so-modular LyX sources is a major pain and I think it's a sure bet
> to assume that most of the work spent in these branches will be lost.
Oh, I disagree. It's very easy to keep a branch up-to-date.
It's only a matte
> So it's time to create a few cvs-branches.
I disagree. Merging branches after a year or so of development in these
not-so-modular LyX sources is a major pain and I think it's a sure bet
to assume that most of the work spent in these branches will be lost
(for quite a while at least). You see it
14 matches
Mail list logo
