#32 allow for non-english piece initials in the PGN text

[Anonymous]

Originally created by: paolocas...@gmail.com
Originally owned by: paolocas...@gmail.com

A six char string needs to be defined, such as "KQRBNP" for English.
Then the array PieceCode needs to be assigned the new value; PieceCode[0] =
"K" and so on.

Please check there no implication for the FEN PGN tag (for the initial
board setup), with FEN and pgn4web.js always using English initials.

[Anonymous]

Originally posted by: paolocas...@gmail.com

1. avoid guessing the language, in some cases there are ambiguities (1. h4 h5 2. Rh3
Finnish or English?)
2. avoid "translating" the PGN in another language (how to deal with
variations/comments?)

Some input language combinations:

Language     PGN piece string
========     ================
Catalan      RDTAC P
Czech        KDVSJ P
Danish       KDTLS B
Dutch        KDTLP P
English      KQRBN P
Finnish      KDTLR S
French       RDTFC P
German       KDTLS B
Hindi        RVHOG P
Hungarian    KVBFH P
Icelandic    KDHBR P
Indonesian   RMBGK P
Italian      RDTAC P
Korean       KQRBN P
Norwegian    KDTLS B
Polish       KHWGS P
Portuguese   RDTBC P
Romanian     RDTNC P
Slovakian    KDVSJ P
Spanish      RDTAC P
Swedish      KDTLS B

[Anonymous]

Originally posted by: Danijel....@gmail.com

Croatian KDTLS P!

[Anonymous]

Originally posted by: paolocas...@gmail.com

After adding support for figurine notation (see issue 39
https://code.google.com/p/pgn4web/issues/detail?id=39), adding support for different
piece initials in different languages is not necessary anymore. Use your chess
software to generate PGN files with English initials and then use figurine fonts for
the moves.

Might go back to this later, but I will probably never add the multi-language option.

Status: WontFix

[Anonymous]

Originally posted by: paolocas...@gmail.com

Further thoughts... I might implement the option to set the input language (or to
guess it, with preference to english in case of ambiguity); then the language
translation would apply only when reading the moves leaving the display untouched.
It might be possible to doit changing only function ParseMove() in pgn4web.js.
Since moves display is not translated, the comment/variation issue does not apply.

Status: Accepted

[Anonymous]

Originally posted by: paolocas...@gmail.com

Dutch is actually KDTLP O

[Anonymous]

Originally posted by: paolocas...@gmail.com

If multiple languages were accepted for display, keep in mind that figurine notation
works only with English (and German and Dutch) initials. So, if multiple languages
were accepted, either the documentation should warn not to use figurine notation with
non supported languages, or a flag should be assigned when selecting the language to
translate into English for display (however this would mess up the cut&paste and this
would also show the other language initials if the browser does not support figurine
fonts).

[Anonymous]

Originally posted by: paolocas...@gmail.com

Further thought: the NAG translation is currently in English; if multiple languages
were supported, should also NAG translations be included?

[Anonymous]

Originally posted by: pa...@casaschi.net

(No comment was entered for this change.)

Labels: Category-Core

[Anonymous]

Originally posted by: pa...@casaschi.net

(No comment was entered for this change.)

Summary: allow for non-english piece initials in the PGN text

[Anonymous]

Originally posted by: pa...@casaschi.net

Decided not to support non-english piece initials in the PGN text, rather encouraging the use of english initials in conjunction with figurine font and chess informant symbols font for the game notation in language independent format.

Status: WontFix

[Anonymous]

Originally posted by: Danijel....@gmail.com

OK, fair enough.