Stephen Harris [EMAIL PROTECTED] writes:
Angus wrote:
Ok, you can grab this iconv-aware version of LyX 1.3.7 here:
http://wiki.lyx.org/uploads/Windows/LyX137/lyx-1.3.7_win32_setup_v3.exe
This is probably not what is supposed to be tested, but
the spellchecker fails The spellchecker has
Angus Leeming [EMAIL PROTECTED] writes:
As yo suggest, this is all to do with the aspell 0.5 to 0.6 change. aspell 0.6
expects to find its dictionaries in a different location to 0.5. Haven't got
time to help here I'm afraid but the aspell pages are quite explicit (as you
pointed out), so it'd
Stephen Harris <[EMAIL PROTECTED]> writes:
> Angus wrote:
> Ok, you can grab this iconv-aware version of LyX 1.3.7 here:
> http://wiki.lyx.org/uploads/Windows/LyX137/lyx-1.3.7_win32_setup_v3.exe
> This is probably not what is supposed to be tested, but
> the spellchecker fails "The spellchecker
Angus Leeming <[EMAIL PROTECTED]> writes:
> As yo suggest, this is all to do with the aspell 0.5 to 0.6 change. aspell 0.6
> expects to find its dictionaries in a different location to 0.5. Haven't got
> time to help here I'm afraid but the aspell pages are quite explicit (as you
> pointed out),
Uwe Stöhr wrote:
It seems like Lyx/Win uses KOI8-R
even when LANG is explicitly assigned to ru_RU.CP1251.
This should be fixed in version 1.0 and 1.1 of this installer:
I use 1.1. It still exists.
To get it to work you need to set your win locale settings to russian
(date format and
You mean that you're making changes to the LyX code/support files?
That's bad. All such changes should go into the LyX repository.
I only changed the encoding of the russian .po-file from ISO to windows
CP 1250 and compiled a .mo from this.
This should fix the problems as users reported this
Uwe == Uwe Stöhr [EMAIL PROTECTED] writes:
You mean that you're making changes to the LyX code/support files?
That's bad. All such changes should go into the LyX repository.
Uwe I only changed the encoding of the russian .po-file from ISO to
Uwe windows CP 1250 and compiled a .mo from this.
Jean-Marc Lasgouttes wrote:
My answer at the time was that gettext will deliver the text in the
locale you ask for, and will convert as needed as long as iconv
support is compiled in. Does it find iconv when configuring?
This is the problem: The iconv version available for windows seems to be
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
My answer at the time was that gettext will deliver the text in the
locale you ask for, and will convert as needed as long as iconv
support is compiled in. Does it find iconv when configuring?
My understanding is that Uwe has always used my
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus My understanding is that Uwe has always used my executable, so
Angus you're probably asking the wrong man :)
I did not dare bring you back from the dead. ..
Angus Michael's post last night has just kickstarted me into trying
Angus to build
Uwe Stöhr wrote:
I only changed the encoding of the russian .po-file from ISO to windows
CP 1250 and compiled a .mo from this.
This should fix the problems as users reported this to me.
I asked on the list to have two different .po files, one in ISO and one
in Windows CP, but this proposal
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
Angus When I get to the configure LyX stage I'll see if I can use the
Angus installed gettext/libiconv rather than the gettext that comes
Angus with the LyX sources.
Very good. Or maybe building against the included gettext and
installed
Angus Leeming [EMAIL PROTECTED] writes:
Jean-Marc Lasgouttes Jean-Marc.Lasgouttes at ... writes:
Angus When I get to the configure LyX stage I'll see if I can use the
Angus installed gettext/libiconv rather than the gettext that comes
Angus with the LyX sources.
Very good. Or maybe
Angus wrote:
Ok, you can grab this iconv-aware version of LyX 1.3.7 here:
http://wiki.lyx.org/uploads/Windows/LyX137/lyx-1.3.7_win32_setup_v3.exe
I've no idea how to go about testing it. Jean-Marc?
--
This is probably not
> Uwe Stöhr wrote:
>
>>> It seems like Lyx/Win uses KOI8-R
>>> even when LANG is explicitly assigned to "ru_RU.CP1251".
>
>> This should be fixed in version 1.0 and 1.1 of this installer:
>
> I use 1.1. It still exists.
To get it to work you need to set your win locale settings to russian
(date
> You mean that you're making changes to the LyX code/support files?
> That's bad. All such changes should go into the LyX repository.
I only changed the encoding of the russian .po-file from ISO to windows
CP 1250 and compiled a .mo from this.
This should fix the problems as users reported
> "Uwe" == Uwe Stöhr <[EMAIL PROTECTED]> writes:
>> You mean that you're making changes to the LyX code/support files?
>> That's bad. All such changes should go into the LyX repository.
Uwe> I only changed the encoding of the russian .po-file from ISO to
Uwe> windows CP 1250 and compiled a
Jean-Marc Lasgouttes wrote:
My answer at the time was that gettext will deliver the text in the
locale you ask for, and will convert as needed as long as iconv
support is compiled in. Does it find iconv when configuring?
This is the problem: The iconv version available for windows seems to be
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> My answer at the time was that gettext will deliver the text in the
> locale you ask for, and will convert as needed as long as iconv
> support is compiled in. Does it find iconv when configuring?
My understanding is that Uwe has always used my
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> My understanding is that Uwe has always used my executable, so
Angus> you're probably asking the wrong man :)
I did not dare bring you back from the dead. ..
Angus> Michael's post last night has just kickstarted me into trying
Uwe Stöhr wrote:
I only changed the encoding of the russian .po-file from ISO to windows
CP 1250 and compiled a .mo from this.
This should fix the problems as users reported this to me.
I asked on the list to have two different .po files, one in ISO and one
in Windows CP, but this proposal
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> Angus> When I get to the configure LyX stage I'll see if I can use the
> Angus> installed gettext/libiconv rather than the gettext that comes
> Angus> with the LyX sources.
> Very good. Or maybe building against the included gettext and
>
Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Jean-Marc Lasgouttes ...> writes:
> > Angus> When I get to the configure LyX stage I'll see if I can use the
> > Angus> installed gettext/libiconv rather than the gettext that comes
> > Angus> with the LyX sources.
>
> > Very good. Or maybe
Angus wrote:
Ok, you can grab this iconv-aware version of LyX 1.3.7 here:
http://wiki.lyx.org/uploads/Windows/LyX137/lyx-1.3.7_win32_setup_v3.exe
I've no idea how to go about testing it. Jean-Marc?
--
This is probably not
Hi, folks!
There are two problems with russian language in Lyx 1.3.7 for windows.
First, when LANG environment variable is assigned to ru_RU,
all russian characters in menus are displayed in incorrect encoding.
There are many russian encodings: KOI8-R under Unix, CP1251 under
Windows and
There are two problems with russian language in Lyx 1.3.7 for windows.
First, when LANG environment variable is assigned to ru_RU,
all russian characters in menus are displayed in incorrect encoding.
There are many russian encodings: KOI8-R under Unix, CP1251 under
Windows and CP866 under
Uwe Stöhr [EMAIL PROTECTED] writes:
There are two problems with russian language in Lyx 1.3.7 for windows.
First, when LANG environment variable is assigned to ru_RU,
all russian characters in menus are displayed in incorrect encoding.
There are many russian encodings: KOI8-R
Uwe Stöhr wrote:
It seems like Lyx/Win uses KOI8-R
even when LANG is explicitly assigned to ru_RU.CP1251.
This should be fixed in version 1.0 and 1.1 of this installer:
I use 1.1. It still exists.
Second, when keyboard is switched to russian layout,
Lyx ignores all keys until keyboard is
Hi, folks!
There are two problems with russian language in Lyx 1.3.7 for windows.
First, when LANG environment variable is assigned to ru_RU,
all russian characters in menus are displayed in incorrect encoding.
There are many russian encodings: KOI8-R under Unix, CP1251 under
Windows and
> There are two problems with russian language in Lyx 1.3.7 for windows.
> First, when LANG environment variable is assigned to ru_RU,
> all russian characters in menus are displayed in incorrect encoding.
> There are many russian encodings: KOI8-R under Unix, CP1251 under
> Windows and CP866
Uwe Stöhr <[EMAIL PROTECTED]> writes:
>
> > There are two problems with russian language in Lyx 1.3.7 for windows.
>
> > First, when LANG environment variable is assigned to ru_RU,
> > all russian characters in menus are displayed in incorrect encoding.
> > There are many russian encodings:
Uwe Stöhr wrote:
It seems like Lyx/Win uses KOI8-R
even when LANG is explicitly assigned to "ru_RU.CP1251".
This should be fixed in version 1.0 and 1.1 of this installer:
I use 1.1. It still exists.
Second, when keyboard is switched to russian layout,
Lyx ignores all keys until keyboard is
32 matches
Mail list logo
