Hello developers,
Thomasz Luzak reported me that the .po files for LyX languages have to
use Windows codepages. That means
- pl.po, sk.po, and sv.po must use CP1250 instead of iso8859-2 (that is
needed on Linux)
- ru.po must use CP1251
So what should we do? I propose to add a new folder
Uwe Stöhr [EMAIL PROTECTED] writes:
| Hello developers,
|
| Thomasz Luzak reported me that the .po files for LyX languages have to
| use Windows codepages. That means
|
| - pl.po, sk.po, and sv.po must use CP1250 instead of iso8859-2 (that
| is needed on Linux)
|
| - ru.po must use CP1251
|
|
Uwe Stöhr wrote:
Hello developers,
Thomasz Luzak reported me that the .po files for LyX languages have to
use Windows codepages. That means
- pl.po, sk.po, and sv.po must use CP1250 instead of iso8859-2 (that is
needed on Linux)
- ru.po must use CP1251
So what should we do? I propose to
Lars Gullik Bjønnes writes:
Are you saying that the the po files won't work if they were utf-8
either?
Not yet, I'll test it but expect that it don't work. (german umlauts are
displayed correctly but UTF-8 encodes them different)
regards Uwe
Lars Gullik Bjønnes writes:
Are you saying that the the po files won't work if they were utf-8
either?
Now yes, they don't work.
Thomasz tested it. Screenshot of the result is attached.
regards Uwe
Am Dienstag, 10. Januar 2006 14:58 schrieb Uwe Stöhr:
Lars Gullik Bjønnes writes:
Are you saying that the the po files won't work if they were utf-8
either?
Now yes, they don't work.
Thomasz tested it. Screenshot of the result is attached.
What about translated strings in the text area
Georg Baum wrote:
Am Dienstag, 10. Januar 2006 14:58 schrieb Uwe Stöhr:
Lars Gullik Bjønnes writes:
Are you saying that the the po files won't work if they were utf-8
either?
Now yes, they don't work.
Thomasz tested it. Screenshot of the result is attached.
What about translated
Am Dienstag, 10. Januar 2006 20:54 schrieb Tomasz Łuczak:
Georg Baum wrote:
What about translated strings in the text area (e. g. the strings
Figure,
Table etc. in captions)?
I suspect that these work with the current encoding.
You are right.
Menu displays correct diacritics in CP1250
Georg Baum wrote:
Am Dienstag, 10. Januar 2006 20:54 schrieb Tomasz Łuczak:
Problem with encoding appear just now, from 1.3.7 version.
You mean 1.3.6 was OK? Then maybe this is a problem of the windows qt
port that is used, I don't think that anything changes in this regard
from 1.3.6
Tomasz Łuczak wrote:
Am Dienstag, 10. Januar 2006 20:54 schrieb Tomasz Łuczak:
Problem with encoding appear just now, from 1.3.7 version.
You mean 1.3.6 was OK? Then maybe this is a problem of the windows qt
port that is used, I don't think that anything changes in this regard
Uwe Stöhr wrote:
Tomasz Łuczak wrote:
Yes, 1.3.6 and previous were OK.
I tested LyX 1.3.6 and it is not OK on my system (when I use polish
windows settings). The diacritics ą, ł etc. are shown as a, l
etc. With the actual qtwin library ą is shown as ±. The latter is
correct when you view
Hello developers,
Thomasz Luzak reported me that the .po files for LyX languages have to
use Windows codepages. That means
- pl.po, sk.po, and sv.po must use CP1250 instead of iso8859-2 (that is
needed on Linux)
- ru.po must use CP1251
So what should we do? I propose to add a new folder
Uwe Stöhr <[EMAIL PROTECTED]> writes:
| Hello developers,
|
| Thomasz Luzak reported me that the .po files for LyX languages have to
| use Windows codepages. That means
|
| - pl.po, sk.po, and sv.po must use CP1250 instead of iso8859-2 (that
| is needed on Linux)
|
| - ru.po must use CP1251
|
Uwe Stöhr wrote:
Hello developers,
Thomasz Luzak reported me that the .po files for LyX languages have to
use Windows codepages. That means
- pl.po, sk.po, and sv.po must use CP1250 instead of iso8859-2 (that is
needed on Linux)
- ru.po must use CP1251
So what should we do? I propose to
Lars Gullik Bjønnes writes:
Are you saying that the the po files won't work if they were utf-8
either?
Not yet, I'll test it but expect that it don't work. (german umlauts are
displayed correctly but UTF-8 encodes them different)
regards Uwe
Lars Gullik Bjønnes writes:
Are you saying that the the po files won't work if they were utf-8
either?
Now yes, they don't work.
Thomasz tested it. Screenshot of the result is attached.
regards Uwe
Am Dienstag, 10. Januar 2006 14:58 schrieb Uwe Stöhr:
> Lars Gullik Bjønnes writes:
>
> > Are you saying that the the po files won't work if they were utf-8
> > either?
>
> Now yes, they don't work.
> Thomasz tested it. Screenshot of the result is attached.
What about translated strings in the
Georg Baum wrote:
Am Dienstag, 10. Januar 2006 14:58 schrieb Uwe Stöhr:
Lars Gullik Bjønnes writes:
Are you saying that the the po files won't work if they were utf-8
either?
Now yes, they don't work.
Thomasz tested it. Screenshot of the result is attached.
What about translated
Am Dienstag, 10. Januar 2006 20:54 schrieb Tomasz Łuczak:
> Georg Baum wrote:
> > What about translated strings in the text area (e. g. the strings
Figure,
> > Table etc. in captions)?
> > I suspect that these work with the current encoding.
> You are right.
> Menu displays correct diacritics in
Georg Baum wrote:
> Am Dienstag, 10. Januar 2006 20:54 schrieb Tomasz Łuczak:
>
>> Problem with encoding appear just now, from 1.3.7 version.
>
> You mean 1.3.6 was OK? Then maybe this is a problem of the windows qt
> port that is used, I don't think that anything changes in this regard
> from
Tomasz Łuczak wrote:
> Am Dienstag, 10. Januar 2006 20:54 schrieb Tomasz Łuczak:
>
>> Problem with encoding appear just now, from 1.3.7 version.
>
> You mean 1.3.6 was OK? Then maybe this is a problem of the windows qt
> port that is used, I don't think that anything changes in this
Uwe Stöhr wrote:
Tomasz Łuczak wrote:
Yes, 1.3.6 and previous were OK.
I tested LyX 1.3.6 and it is not OK on my system (when I use polish
windows settings). The diacritics "ą", "ł" etc. are shown as "a", "l"
etc. With the actual qtwin library "ą" is shown as "±". The latter is
correct
22 matches
Mail list logo
