Lars Gullik Bjønnes wrote:
> Georg Baum <[EMAIL PROTECTED]>
> writes:
>
> | Lars Gullik Bjønnes wrote:
> |
> | > Georg, how fast can you make this happen?
> |
> | Ah, you are already there. I'll see what I can do now and report back in
> | due course.
>
> Super.
I put it in.
Known problems:
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Jean-Marc Lasgouttes wrote:
>> What I say is that you can choose to implement only utf8 export for
>> now (we all know how lazy you all are :), but _please_ don't do it
>> in a way that locks the door to implementing other encodings af
Jean-Marc Lasgouttes wrote:
> What I say is that you can choose to implement only utf8 export for
> now (we all know how lazy you all are :), but _please_ don't do it in
> a way that locks the door to implementing other encodings after that.
I am almost finished with this now, and as I wrote seve
> "Asger" == Asger Ottar Alstrup <[EMAIL PROTECTED]> writes:
Asger> I've been playing around with LyX head for a few minutes now,
Asger> and there are so many problems. Math editing does not work *at
Asger> all*. Make a table, and it crashes all over the place.
I agree there are many problems
Jean-Marc Lasgouttes wrote:
"Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| I vote for utf8 only.
Lars> Asger and I agrees.
I do not see what the point is. Either the translation between utf8
and something else is trivial and we have
Abdelrazak Younes wrote:
Juergen Spitzmueller wrote:
Asger Ottar Alstrup wrote:
LaTeX can do UTF8, it seems.
http://mail.nl.linux.org/linux-utf8/2004-04/msg0.html
Just use "\usepackage[utf8]{inputenc}".
Note that there are still lots of packages that don't work with utf8.
For instan
> "Asger" == Asger Ottar Alstrup <[EMAIL PROTECTED]> writes:
Asger> First step: (Georg volunteered :-)
Asger> - Write UCS4 streams which are converted to UTF-8 by magic
Asger> - So the LaTeX file is in UTF-8 encoding
I do not understand the concern about the difficulty of doing
non-utf8. Wo
Jean-Marc Lasgouttes wrote:
And seriously, nobody will be pleased when you tell them that our TeX
files are utf8. This is not a good encoding for latex now.
I've been playing around with LyX head for a few minutes now, and there
are so many problems. Math editing does not work *at all*. Make a
> "Asger" == Asger Ottar Alstrup <[EMAIL PROTECTED]> writes:
Asger> Is that not something recode can do in a split second?
Recode does not have information on the context of a string. Are we
sure that a utf8 thingy in math or in text shall be treated the same
way, for example?
JMarc
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| I vote for utf8 only.
Lars> Asger and I agrees.
I do not see what the point is. Either the translation between utf8
and something else is trivial and we have iconv to do it from withi
Lars Gullik Bjønnes wrote:
> | Conversion to other encodings is a must.
>
> Not as a first step.
If the second step follows before 1.5 is released, then o.k.
> And it seems that someone needs to push utf8/unicode support in latex.
> Why not let that be us.
I'm sorry, but I doubt that the develop
Abdelrazak Younes wrote:
> I've read that about listing:
>
> http://www.tug.org/pipermail/macostex-archives/2006-April/021868.html
>
> Would that help?
Maybe, maybe not. There are also other workarounds (but they won't work for
soul or shortvrb, for instance).
Jürgen
Michael Gerz wrote:
> I agree that listings is a very important package (BTW: What does soul
> do?).
letterspacing, better underlining, strike-out letters, highlighting. It's a
standard package.
> However, what does "listings does not support unicode" mean? Does
> it mean that
>
> (a) latex
Lars Gullik Bjønnes wrote:
> Is the change required basically to replace ofstream with odocfstream?
> and update all functions to use this instead? If so I am progressing
> nicly with docbook, else I have no clue what I am doing.
Yes, that is it (almost: of course odocfstream should only be used
Georg Baum <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
|
| > Georg, how fast can you make this happen?
|
| Ah, you are already there. I'll see what I can do now and report back in due
| course.
Super.
| > (we should do the same with docbook btw.)
|
| Yes.
Is the change require
Lars Gullik Bjønnes wrote:
> Georg, how fast can you make this happen?
Ah, you are already there. I'll see what I can do now and report back in due
course.
> (we should do the same with docbook btw.)
Yes.
Georg
Georg Baum wrote:
You misunderstood me. My proposal was not to do the internal conversion. My
proposal was to the same with all latex() methods that I did with
plaintext(): Output to UCS4 streams and do the conversion to utf8 in the
file stream.
Sounds good to me. Lars talks about compression
On Thursday 19 October 2006 10:34, Abdelrazak Younes wrote:
> Georg Baum wrote:
> > Abdelrazak Younes wrote:
> >> The question is: should this conversion happens in C++/LyX or
> >> externally? I am all for only utf8 export from LyX.
>
> I understand... but IIRC Jose said at one point that he intend
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Georg Baum wrote:
| > Asger Ottar Alstrup wrote:
| >
| >> Perfect is the enemy of good. Why cares about those unicode characters?
| > I have no idea. Maybe they are not important at all, but I would not
| > be
| > surpised either if they were some ve
Michael Gerz <[EMAIL PROTECTED]> writes:
| Georg Baum schrieb:
| > I am currently not able to judge whether an external converter would be OK
| > or not, therefore I propose to either decide this in Denmark, or postpone
| > this decision even further until we have some experience with utf8 export.
Juergen Spitzmueller wrote:
Asger Ottar Alstrup wrote:
LaTeX can do UTF8, it seems.
http://mail.nl.linux.org/linux-utf8/2004-04/msg0.html
Just use "\usepackage[utf8]{inputenc}".
Note that there are still lots of packages that don't work with utf8. For
instance, listings and soul are two
Georg Baum wrote:
Asger Ottar Alstrup wrote:
Perfect is the enemy of good. Why cares about those unicode characters?
I have no idea. Maybe they are not important at all, but I would not be
surpised either if they were some very commonly used symbols.
We can hack those somehow if they are im
Georg Baum schrieb:
I am currently not able to judge whether an external converter would be OK
or not, therefore I propose to either decide this in Denmark, or postpone
this decision even further until we have some experience with utf8 export.
When do you meet in Denmark? I forgot the exact d
Abdelrazak Younes schrieb:
Juergen Spitzmueller wrote:
Note that there are still lots of packages that don't work with utf8.
For instance, listings and soul are two very common and useful
packages that do not support unicode.
I agree that listings is a very important package (BTW: What does sou
Georg Baum <[EMAIL PROTECTED]> writes:
| Abdelrazak Younes wrote:
|
| > The question is: should this conversion happens in C++/LyX or
| > externally? I am all for only utf8 export from LyX.
|
| If that would be possible that would really be great, but see below for
| possible problems.
|
| > Th
Asger Ottar Alstrup wrote:
> Perfect is the enemy of good. Why cares about those unicode characters?
I have no idea. Maybe they are not important at all, but I would not be
surpised either if they were some very commonly used symbols.
> We can hack those somehow if they are important.
Yes.
> T
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
| Asger Ottar Alstrup wrote:
| > LaTeX can do UTF8, it seems.
| >
| > http://mail.nl.linux.org/linux-utf8/2004-04/msg0.html
| >
| > Just use "\usepackage[utf8]{inputenc}".
|
| Note that there are still lots of packages that don't work with utf8
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| I vote for utf8 only.
Asger and I agrees.
--
Lgb
Georg Baum wrote:
I don't think either that there would be a performance problem. What might
be a problem is that an inset knows more about its content (and, more
importantly, about the context) and could do a better conversion than an
external converter could do. For example, I am 100% sure that
Georg Baum wrote:
Abdelrazak Younes wrote:
The question is: should this conversion happens in C++/LyX or
externally? I am all for only utf8 export from LyX.
If that would be possible that would really be great, but see below for
possible problems.
The conversion from LateX utf8 to some othe
Abdelrazak Younes wrote:
> The question is: should this conversion happens in C++/LyX or
> externally? I am all for only utf8 export from LyX.
If that would be possible that would really be great, but see below for
possible problems.
> The conversion from LateX utf8 to some other encoding can ha
Abdelrazak Younes wrote:
> The question is: should this conversion happens in C++/LyX or
> externally? I am all for only utf8 export from LyX.
I don't care where it happens. But I want to be able to set "latin-1" either
as a default for all of my documents or in single documents because
- I use a
Georg Baum wrote:
Asger Ottar Alstrup wrote:
LaTeX can do UTF8, it seems.
Yes, we know that, but it is still incomplete.
http://mail.nl.linux.org/linux-utf8/2004-04/msg0.html
Just use "\usepackage[utf8]{inputenc}".
Let's do UTF-8 all over the place as the first step.
I can't believe
Juergen Spitzmueller wrote:
Asger Ottar Alstrup wrote:
LaTeX can do UTF8, it seems.
http://mail.nl.linux.org/linux-utf8/2004-04/msg0.html
Just use "\usepackage[utf8]{inputenc}".
Note that there are still lots of packages that don't work with utf8. For
instance, listings and soul are two
Asger Ottar Alstrup wrote:
> LaTeX can do UTF8, it seems.
>
> http://mail.nl.linux.org/linux-utf8/2004-04/msg0.html
>
> Just use "\usepackage[utf8]{inputenc}".
Note that there are still lots of packages that don't work with utf8. For
instance, listings and soul are two very common and useful
Asger Ottar Alstrup wrote:
> LaTeX can do UTF8, it seems.
Yes, we know that, but it is still incomplete.
> http://mail.nl.linux.org/linux-utf8/2004-04/msg0.html
>
> Just use "\usepackage[utf8]{inputenc}".
>
> Let's do UTF-8 all over the place as the first step.
>
> I can't believe nobody
Georg Baum wrote:
No. What is exported currently to LaTeX is a mixture of utf8 (e.g.
InsetCommandParams) and ucs4 code points as numbers. It would be pretty
easy to always do utf8 export, but this does not make sense IMO before it
is clear how LaTeX export to other encodings than utf8 should lo
Am Mittwoch, 18. Oktober 2006 19:38 schrieb Asger Ottar Alstrup:
> Hi,
>
> Are there any preliminary patches for LaTeX export that we can build on?
No. What is exported currently to LaTeX is a mixture of utf8 (e.g.
InsetCommandParams) and ucs4 code points as numbers. It would be pretty
easy to
Hi,
Are there any preliminary patches for LaTeX export that we can build on?
Regards,
Asger
39 matches
Mail list logo
