Sanda Pavel wrote:
i filed bug 2906 concerning this.
both this bug and encoding problems affect only
1.4.3 of win lyx
I just managed to get gettext 0.15 and libiconv 0.11 (the latest
versions) to work with Windows and MSVC 2005. I'll publish patches soon.
It looks like this solves the probl
> but its strange, that inside the dialogs get english captions
> mixed with czech although all of them should be translated.
i filed bug 2906 concerning this.
both this bug and encoding problems affect only
1.4.3 of win lyx, not 1.4.2. also its not language
dependent, i have tried explitly czech
> but its strange, that inside the dialogs get english captions
> mixed with czech although all of them should be translated.
i get fresh BRANCH_1_4_X and under linux there is no problem,
all captions are czech.
pavel
> >works, too? For me, on Win2k, both iso-8859-2 and iso8859-2 will do.
>
> Both do not work for me on Windows XP. Although it does change
> something, I just get other incorrect characters.
could you post screenshots of these two incorrect versions ?
pavel
Sanda Pavel wrote:
Using Windows XP? Are you sure all characters have the correct accents?
as i wrote previously: using win-xp and all chars i see are correct.
It doesn't work on any of my Windows XP systems. I have no idea how to
solve this.
Joost
> >>A random string seems to reset the encoding to iso-8859-1. So you'll
> >>still get incorrect characters.
> >
> >no, they are correct (=that was meant by "work")
>
> Using Windows XP? Are you sure all characters have the correct accents?
as i wrote previously: using win-xp and all chars i s
Sanda Pavel wrote:
A random string seems to reset the encoding to iso-8859-1. So you'll
still get incorrect characters.
no, they are correct (=that was meant by "work")
Using Windows XP? Are you sure all characters have the correct accents?
Maybe it only works for Czech.
Joost
> A random string seems to reset the encoding to iso-8859-1. So you'll
> still get incorrect characters.
no, they are correct (=that was meant by "work")
pavel
Sanda Pavel wrote:
wow, when i set :
SET OUTPUT_CHARSET=blahblah
it works too ! :)
A random string seems to reset the encoding to iso-8859-1. So you'll
still get incorrect characters.
Joost
> 1. there is is difference, how use variables:
> OUTPUT_CHARSET=cp-1250 (flashes error in console)
> is not the same as
> SET OUTPUT_CHARSET=cp-1250 (works)
wow, when i set :
SET OUTPUT_CHARSET=blahblah
it works too ! :)
when i delete the whole line, then it doesnt work.
pavel
hi people,
i'm using win-xp.
1. there is is difference, how use variables:
OUTPUT_CHARSET=cp-1250 (flashes error in console)
is not the same as
SET OUTPUT_CHARSET=cp-1250 (works)
both output charsets iso-8859-2 and cp-1250 works as far as
the menu concerned.
but its strange, that inside the di
Enrico Forestieri wrote:
Do you mean on WinXP? Then, can you tell if
OUTPUT_CHARSET=iso8859-2
works, too? For me, on Win2k, both iso-8859-2 and iso8859-2 will do.
Both do not work for me on Windows XP. Although it does change
something, I just get other incorrect characters.
Joost
> "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> Enrico Forestieri wrote:
>> Oh, that's because I stupidly set OUTPUT_CHARSET to iso-8859-1. Is
>> it any better with "SET OUTPUT_CHARSET=iso-8859-2" ?
Joost> I don't think that will work. For Windows you should use the
Joost> codep
On Fri, Oct 06, 2006 at 01:06:55AM +0200, Uwe Stöhr wrote:
> Thanks for the hint,
> setting
>
> OUTPUT_CHARSET=cp-1250
>
> seems to bring up the correct menu names.
Do you mean on WinXP? Then, can you tell if
OUTPUT_CHARSET=iso8859-2
works, too? For me, on Win2k, both iso-8859-2 and iso8859-2
Thanks for the hint,
setting
OUTPUT_CHARSET=cp-1250
seems to bring up the correct menu names. Sanda could you please check
if all translations are correctly displayed.
thanks and regards
Uwe
Enrico Forestieri wrote:
I have Windows 2000 and don't even touch the system locale. I really
don't know why it does not work on WinXP.
It indeed works on Windows 2000 and not on Windows XP. Weird.
Joost
On Thu, Oct 05, 2006 at 08:44:47PM +0200, Joost Verburg wrote:
> Enrico Forestieri wrote:
> >Oh, that's because I stupidly set OUTPUT_CHARSET to iso-8859-1.
> >Is it any better with "SET OUTPUT_CHARSET=iso-8859-2" ?
>
> The screenshot looks nice, but I cannot get it that way.
>
> With:
>
> SET L
Enrico Forestieri wrote:
Oh, that's because I stupidly set OUTPUT_CHARSET to iso-8859-1.
Is it any better with "SET OUTPUT_CHARSET=iso-8859-2" ?
The screenshot looks nice, but I cannot get it that way.
With:
SET LANG=sk_SK
SET OUTPUT_CHARSET=iso-8859-2
all characters are still wrong. I'm usi
Enrico Forestieri wrote:
Oh, that's because I stupidly set OUTPUT_CHARSET to iso-8859-1.
Is it any better with "SET OUTPUT_CHARSET=iso-8859-2" ?
I don't think that will work. For Windows you should use the codepage
1250 instead of ISO-8859-2. Although parts of these charsets are
similar, they
On Thu, Oct 05, 2006 at 02:27:21PM +0200, Sanda Pavel wrote:
> > On Thu, Oct 05, 2006 at 12:48:59PM +0200, Joost Verburg wrote:
> > > Enrico Forestieri wrote:
> > > >I attach here two images. LANGUAGE.png refers to "SET LANGUAGE=ru_RU",
> > > >whereas LANG.png to "SET LANG=ru_RU".
> > >
> > > OK,
> On Thu, Oct 05, 2006 at 12:48:59PM +0200, Joost Verburg wrote:
> > Enrico Forestieri wrote:
> > >I attach here two images. LANGUAGE.png refers to "SET LANGUAGE=ru_RU",
> > >whereas LANG.png to "SET LANG=ru_RU".
> >
> > OK, so Russian works. But Slovak, Czech etc. not.
>
> They also work for me
On Thu, Oct 05, 2006 at 12:48:59PM +0200, Joost Verburg wrote:
> Enrico Forestieri wrote:
> >I attach here two images. LANGUAGE.png refers to "SET LANGUAGE=ru_RU",
> >whereas LANG.png to "SET LANG=ru_RU".
>
> OK, so Russian works. But Slovak, Czech etc. not.
They also work for me after I set OUTP
Enrico Forestieri wrote:
I attach here two images. LANGUAGE.png refers to "SET LANGUAGE=ru_RU",
whereas LANG.png to "SET LANG=ru_RU".
OK, so Russian works. But Slovak, Czech etc. not.
Joost
Enrico Forestieri wrote:
When I use "SET LANGUAGE=ru_RU" I get gibberish instead of cyrillic,
but "SET LANG=ru_RU" works.
I tried LANG, LANGUAGE, LC_ALL etc. It doesn't make any difference. You
are not talking about the native Windows version, are you?
Joost
On Wed, Oct 04, 2006 at 03:08:46PM +0200, Joost Verburg wrote:
> Jean-Marc Lasgouttes wrote:
> >How do you set the language?
>
> Using the LANGUAGE environment variable:
>
> SET LANGUAGE=en_EN
Please try
SET LANG=en_EN
as LANGUAGE is ignored by the intl library when using the C locale.
When I
Jean-Marc Lasgouttes wrote:
How do you set the language?
Using the LANGUAGE environment variable:
SET LANGUAGE=en_EN
Joost
> "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> Hello, I'd like to solve the long-standing issues related to
Joost> the LyX translations on Windows.
We should definitely do something for mac and unix too.
Joost> On Windows, the WINDOWS-1252 encoding (compatible with
Joost> ISO-
Hello,
I'd like to solve the long-standing issues related to the LyX
translations on Windows.
On Windows, the WINDOWS-1252 encoding (compatible with ISO-8859-1)
should be used for languages like English, French and German,
WINDOWS-1250 for Central European languages like Czech, Polish and
Slovak
28 matches
Mail list logo
