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
Hi,
2008/4/12, Hans Eriksson <[EMAIL PROTECTED]>:
>
> and can easily be reproduced like I saw in Scid 3.6.23 rc5 where
> the Swedish vowels "ÅÄÖ" ("åäö" lower case) that are placed after a-z in
> the Swedish alphabet IS reproduced as two strange looking characters
> that are not
> displayed corr
Hello all,
If you look at the language support of Windows
in this Microsoft homepage of
"Locale Identifier Constants and Strings" here:
http://msdn2.microsoft.com/en-us/library/ms776260.aspx
you can easily see that Windows by default has VERY
bad support of Unicode,since only some languages
id e
It is great to see Scid continued, specially that it seems there is no other
free alternatives (ChessX seems more or less dead these days, as it is too
big project for me to continue without help).
It seems that thanks to Pascal's work Scid is finding more users and
contributors. My suggestion
-- very often is this how to forgotten !
> * signature line
>
> My own preference should go for that kind of page to wrap the
> documentation
> pages (i.e. for scid-pg's home page), but something like Ruby On Rails
> [ror]
> might be nice too.
>
> == Concluding
ted program, one that I could sell to only one
friend. All the other ones preferred to sell up their souls...
Kindest regards,
Benoit St-Pierre, Montréal, 20080412
== References ==
[ama] http://www.w3.org/Amaya/
[dta] http://www.devon-technologies.com/support/academy/index.ht
pgeorges wrote:
Hi!
> There were still small problems due to differences between Linux and
> Windows. So I handled both cases in a RC5 that I tested on my Linux
> system (mine is utf-8) and Windows XP.
Just for me to understand: How could it be that DOS has
"another" UTF-8 than linux?
Or in
Pascal Georges, sobota, 12 kwietnia 2008:
>What I don't understand is why
>"encoding system utf-8" does not switch windows to unicode.
Working on another project, I found that Windows Unicode support is at least
buggy (or non-working in some cases), at least up to Windows XP. I don't know
about
Windows has UTF fonts, but if you run
tclsh% encoding names
You will get cp*, which is a localized code page (not utf ...).
So when windows gets 2 bytes for a unicode char, it will display it as 2
chars. What I don't understand is why
"encoding system utf-8" does not switch windows to unicode. The