Well, those flamewars fortunately are more or less over,
at least I haven't seen them for quite a lot of time.
So - there is no reason to recover them.
And let us stop on it.
-
This SF.net email is sponsored by: Microsoft
D
Technically SCID is not presently being developed, but two forks, ChessDB and
SCID-pg, are under active development.
I made the mistake of stepping into this cow pie of an argument when I posted a
positive review of ChessDB at my web site. I had no idea of all the
controversy, and people starte
Okay, thank you. I did not realize that there were later versions than the
ones by the original author at Sourceforge. When I googled SCID, I came up
with that "official" site, and assumed that was it. Your message was enough
of a hint that I found this site, http://prolinux.free.fr/scid/, whic
Marc Plum a écrit :
> First, let me acknowledge that this question is probably fully covered
> in the mailing list archives. However, when I try to search there on
> the Sourceforge site, I get a message that I don’t have sufficient
> privileges. I also don’t see a version history on the SCID So
> I’m curious as to what the differences are between version 3.5.x and
> 3.6.1 of SCID. Is it mostly bugfixes, or are there significant
> functional enhancements?
Well I do not know. But there are a LOT of important enhancements
between scid 3.6.1 (which is also ancient) and scid 3.6.18 (th
First, let me acknowledge that this question is probably fully covered in
the mailing list archives. However, when I try to search there on the
Sourceforge site, I get a message that I don¹t have sufficient privileges.
I also don¹t see a version history on the SCID Sourceforge page. So I¹ll
just
Marcin Kasperski a écrit :
>> I am not sure Scid uses UTF-8 : if I enter white player as "ùà" for
>> example, it will be exported in PGN as 2 chars (not 4).
>>
>
> I suspect locale can be of some importance here. Try
>export LANG='fr_FR.UTF-8'
> or sth similar...
>
>
>>> It even seems t
Marcin Kasperski a écrit :
PGN is "Portable Game Notation", a standard designed for the
representation of chess game data using ASCII text files.
>>> Well, this is false for long, long years. Plenty of games annotated in
>>> German, French, Russian, Polish, Hungarian,
>
>> > PGN is "Portable Game Notation", a standard designed for the
>> > representation of chess game data using ASCII text files.
>>
>> Well, this is false for long, long years. Plenty of games annotated in
>> German, French, Russian, Polish, Hungarian,
>
> I can put a comment in french, in Asc
> I am not sure Scid uses UTF-8 : if I enter white player as "ùà" for
> example, it will be exported in PGN as 2 chars (not 4).
I suspect locale can be of some importance here. Try
export LANG='fr_FR.UTF-8'
or sth similar...
>> It even seems that utf-8 encoded pgn file is properly imported vi
[EMAIL PROTECTED], wtorek, 2 października 2007:
>I am not sure Scid uses UTF-8 : if I enter white player as "ùà" for example,
> it will be exported in PGN as 2 chars (not 4). Tcl natively uses UTF16, and
> I did not see any place in Scid where it encodes explicitely in UTF8 (but I
> am far from ha
Selon Marcin Kasperski <[EMAIL PROTECTED]>:
>
> > As far as I know Scid always uses UTF-8 encoding for PGN files. It
> > is a bit broken on export, but that's probably Tcl fault, not
> > Scid's.
I am not sure Scid uses UTF-8 : if I enter white player as "ùà" for example, it
will be exported in PG
Selon Marcin Kasperski <[EMAIL PROTECTED]>:
>
> > PGN is "Portable Game Notation", a standard designed for the
> > representation of chess game data using ASCII text files.
>
> Well, this is false for long, long years. Plenty of games annotated in
> German, French, Russian, Polish, Hungarian,
> PGN is "Portable Game Notation", a standard designed for the
> representation of chess game data using ASCII text files.
Well, this is false for long, long years. Plenty of games annotated in
German, French, Russian, Polish, Hungarian,
> As far as I know Scid always uses UTF-8 encoding for PGN files. It
> is a bit broken on export, but that's probably Tcl fault, not
> Scid's.
Wow. Nice.
It even seems that utf-8 encoded pgn file is properly imported via
pgnscid and exported back via scidpgn.
The only thing which does not work
15 matches
Mail list logo
