That's good I did not introduce a regression, but given the difficulties
between Linux-ASCII, Linux-UTF-8 and windows , I will leave this bug
resolution to people able to validate the solution, that is are able to read
the relevant languages.
But I think it should not be too complex and that some c
Pascal Georges, poniedziałek, 14 kwietnia 2008:
>Was Polish support working in Scid 3.6.1 ? If yes, this is me that broke
>something and the solution should be easy to find.
No. In fact, since my Linux uses UTF-8, I have to manually convert language
files to UTF-8.
--
Michal Rudolf
2008/4/13, Michal Rudolf <[EMAIL PROTECTED]>:
>
> pgeorges, niedziela, 13 kwietnia 2008:
>
> >I reverted code to ASCII given Windows problems. Could you help fix
> >these broken translations ?
> >I personaly can only cope with english and french.
>
> No idea how I can do it. Linux and Windows use
pgeorges, niedziela, 13 kwietnia 2008:
>I reverted code to ASCII given Windows problems. Could you help fix
>these broken translations ?
>I personaly can only cope with english and french.
No idea how I can do it. Linux and Windows use different charsets and these
days many (most?) Linux installa
Michal Rudolf a écrit :
> pgeorges, niedziela, 13 kwietnia 2008:
>
>
>>> Current version doesn't work for Polish (and probably for other non-Latin1
>>> encodings) in following situations:
>>> * Linux with UTF-8 encoding (which is becoming more and more popular). I
>>> have to manually convert f
pgeorges, niedziela, 13 kwietnia 2008:
>> Current version doesn't work for Polish (and probably for other non-Latin1
>> encodings) in following situations:
>> * Linux with UTF-8 encoding (which is becoming more and more popular). I
>> have to manually convert files to UTF-8
>> * Windows (without
Michal Rudolf a écrit :
> Alexander Wagner, niedziela, 13 kwietnia 2008:
>
>>> So my conclusion so far is to go back to ASCII mode : any
>>> objection in the room ?
>>>
>> No. Never had.
>> As far as I can see it solves the problems for Windows
>> (except switching lang without restart)
Alexander Wagner, niedziela, 13 kwietnia 2008:
> > So my conclusion so far is to go back to ASCII mode : any
> > objection in the room ?
>No. Never had.
>As far as I can see it solves the problems for Windows
>(except switching lang without restart) and as all other
>charsets are subsets of UTF-8
Pascal Georges wrote:
Hi!
> Well, all this does not answer the main question now :
> should I go back to ASCII ? Is current implementation
> broken (my tests show it works) ?
Well it works for me on Linux in either way, actually. I
never tried Windows, though.
> I am not an expert at all in
Well, all this does not answer the main question now : should I go back to
ASCII ? Is current implementation broken (my tests show it works) ?
I am not an expert at all in char encoding problems, and here I am a bit
puzzled about the path to choose. I got an advice from a french Tcl guru (a
person
Pascal Georges wrote:
Hi!
> - On Windows, if french is selected then swedish, the later may be
> displayed incorrectly and need a restart of Scid (this is logical for me
> given current code that converts tokens once for all);
>
> - On Linux, with an UTF-8 system, everything is OK;
Yepp.
Hi,
Tell me if I don't sum up correctly :
- On Windows, if french is selected then swedish, the later may be displayed
incorrectly and need a restart of Scid (this is logical for me given current
code that converts tokens once for all);
- On Linux, with an UTF-8 system, everything is OK;
- On Lin
Hello all,
After checking with older versions of Scid (Scid 3.6.18,Scid 3.6.14,,, etc.)
I saw that it was needed to use "Language for non-Unicode programs"
and a reboot OR use Applocale to select the wanted Scid language
without reboot,so obviously if the *.lng Scid languages are saved
as UTF-8 (w
13 matches
Mail list logo
