Answers.Body: <p>The specification you have in your link has no practical meaning as the format is not enforced consistently. Steven J. Edwards introduced the format, but he didn't have authority to control how programmers implement PGN.</p>
  
  <p><strong>Most PGN parser would only support the English language.</strong></p>
  
  <p>I've been distributing PGN parsing softwares for years, but I don't think I'll add foreign language support. I assume anyone who is intelligently capable of playing chess would be able to read English piece identifiers. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-10T11:18:12.517Z
Answers.Text: In case anyone wants to parse Dutch or German input, my pgn-extract program (https://www.cs.kent.ac.uk/~djb/pgn-extract) has supported both for most of its life, and there is also an option (-Wsan) that would allow output to an arbitrary set of single-character letters if desired.
Answers.UserDisplayName: kentdjb
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-10T11:37:11.010Z
Answers.Text: @kentdjb Thanks for your excellent work on PGN. Your software is an exception :-)
Answers.UserDisplayName: SmallChess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-12T14:15:03.587Z
Answers.Text: @kentdjb That is very interesting! Thanks!
Answers.UserDisplayName: Myungjin Hyun
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-09T10:42:56.267Z
Answers.LastActivityDate: 2018-03-09T10:48:07.687Z
Answers.LastEditDate: 2018-03-09T10:48:07.687Z
Answers.UserDisplayName: SmallChess
Answers.Body: <p>I read it like this:</p>
  
  <blockquote>
    <p>The standard is to use the English piece names. Of course, we can't stop authors to adapt this standard in their own programs (sometimes, it might make sense). But pretty please, do always stick to the English names for any data that might be shared between multiple programs.</p>
  </blockquote>
  
  <p>For example, if I write a program to automatically scan games from old German chess magazines, it makes no sense to let my program try to parse the standard PGN piece names. I'd use German piece names instead, and this is fine in the environment of my own program. </p>
  
  <p>But as soon as I want to store the PGN files in a database, I must translate them to English piece names or my database browser or whatever other program won't be able to read them.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-09T10:47:51.360Z
Answers.Text: I don't fully understand -- if the program in your example scanned games which used German identifiers, would the PGN it internally stores use the German identifiers or the English ones?
Answers.UserDisplayName: Myungjin Hyun
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-09T10:49:33.263Z
Answers.Text: If it only stores the PGN locally, it may use whatever format it wants. If it stores the PGN in a database that other programs are supposed to access (e.g. SCID & Co.), or if it directly shares data with other programs (e.g. if I include an automated Stockfish analysis for each game) it has to conform to the international standard.
Answers.UserDisplayName: Annatar
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-09T10:54:24.633Z
Answers.Text: As such, the paragraph you quote only states the obvious: "You can tinker with the standard in any way you want, but if your program wants to be understood by other programs, you have to translate to English".
Answers.UserDisplayName: Annatar
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-09T13:49:17.097Z
Answers.Text: So you basically mean that I can make a programme that reads PGN that way, but no mainstream PGN readers does so, right? Thanks for your answer! (+1)
Answers.UserDisplayName: Myungjin Hyun
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-09T14:04:34.200Z
Answers.Text: @HarryWeasley Yes.
Answers.UserDisplayName: Annatar
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-09T10:43:26.640Z
Answers.LastActivityDate: 2018-03-09T10:43:26.640Z
Answers.UserDisplayName: Annatar
Body: <p>I came across this in the PGN standard on <a href="http://www.saremba.de/chessgml/standards/pgn/pgn-complete.htm#c9" rel="nofollow noreferrer">this site</a>, section 17, for alternative piece identifiers (emphasis mine):</p>
  <blockquote>
  <p>English language piece names are used to define the letter set for identifying chesspieces in PGN movetext. However, authors of programs which are used only for local presentation or scanning of chess move data may find it convenient to use piece letter codes common in their locales. This is not a problem <strong>as long as PGN data that resides in archival storage or that is exchanged among programs still uses the SAN (English) piece letter codes: &quot;PNBRQK&quot;.</strong></p>
  </blockquote>
  <p>Followed by a table of symbols for different languages.</p>
  <p>The first part seems to suggest that one can use identifiers from other languages to represent the pieces if one so wishes.</p>
  <p>However, the highlighted part seems to contradict that, saying that, ultimately, the PGN should use the English identifiers and not those of any other language.</p>
  <p>It appears that a mistake in my understanding caused this contradiction, so I'd be glad if someone could please clarify it.</p>
  <h3>My question</h3>
  <p>Can one use symbols from languages other than English for representing pieces in a PGN file?</p>
  <p>Would something like this work (using the piece identifiers in German)?</p>
  <pre><code>[Event &quot;Casual game&quot;]
  [Site &quot;Hogwarts&quot;]
  [Date &quot;2018.03.09&quot;]
  [Round &quot;1&quot;]
  [White &quot;Malfoy, Draco&quot;]
  [Black &quot;Weasley, Ronald&quot;]
  [Result &quot;*&quot;]
  [TimeControl &quot;1/15+1&quot;]
  [FEN &quot; &quot;]
  
  1. e4 e5 2. Sf3 Sc6 3. Lb5 Sf6 4. O-O Sxe4 *
  </code></pre>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-09T13:50:35.990Z
Comments.Text: Could someone let me know why this was downvoted? If there's something to fix, I'd be glad for your suggestions!
Comments.UserDisplayName: Myungjin Hyun
Tags: <pgn>
Title: Can one use alternative identifiers (from languages other than English) for chesspieces in PGN?
ThreadText: # Can one use alternative identifiers (from languages other than English) for chesspieces in PGN?
  
  (Asked by: username_0 on 2018-03-09)
  
  I came across this in the PGN standard on [this site](http://www.saremba.de/chessgml/standards/pgn/pgn-complete.htm#c9), section 17, for alternative piece identifiers (emphasis mine):
  
  > English language piece names are used to define the letter set for identifying chesspieces in PGN movetext. However, authors of programs which are used only for local presentation or scanning of chess move data may find it convenient to use piece letter codes common in their locales. This is not a problem **as long as PGN data that resides in archival storage or that is exchanged among programs still uses the SAN (English) piece letter codes: "PNBRQK".**
  
  Followed by a table of symbols for different languages.
  
  The first part seems to suggest that one can use identifiers from other languages to represent the pieces if one so wishes.
  
  However, the highlighted part seems to contradict that, saying that, ultimately, the PGN should use the English identifiers and not those of any other language.
  
  It appears that a mistake in my understanding caused this contradiction, so I'd be glad if someone could please clarify it.
  
  ### My question
  
  Can one use symbols from languages other than English for representing pieces in a PGN file?
  
  Would something like this work (using the piece identifiers in German)?
  
  ```
  [Event "Casual game"]
  [Site "Hogwarts"]
  [Date "2018.03.09"]
  [Round "1"]
  [White "Malfoy, Draco"]
  [Black "Weasley, Ronald"]
  [Result "*"]
  [TimeControl "1/15+1"]
  [FEN " "]
  
  1. e4 e5 2. Sf3 Sc6 3. Lb5 Sf6 4. O-O Sxe4 *
  
  ```
  
  **Tags:** pgn
  
  > **Comments:**
  > **username_0**: Could someone let me know why this was downvoted? If there's something to fix, I'd be glad for your suggestions!  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_3 on 2018-03-09. Score: 4 | Accepted answer
  
  I read it like this:
  
  > The standard is to use the English piece names. Of course, we can't stop authors to adapt this standard in their own programs (sometimes, it might make sense). But pretty please, do always stick to the English names for any data that might be shared between multiple programs.
  
  For example, if I write a program to automatically scan games from old German chess magazines, it makes no sense to let my program try to parse the standard PGN piece names. I'd use German piece names instead, and this is fine in the environment of my own program.
  
  But as soon as I want to store the PGN files in a database, I must translate them to English piece names or my database browser or whatever other program won't be able to read them.
  
  > **Comments:**
  > **username_0**: I don't fully understand -- if the program in your example scanned games which used German identifiers, would the PGN it internally stores use the German identifiers or the English ones?  
  > **username_3**: If it only stores the PGN locally, it may use whatever format it wants. If it stores the PGN in a database that other programs are supposed to access (e.g. SCID & Co.), or if it directly shares data with other programs (e.g. if I include an automated Stockfish analysis for each game) it has to conform to the international standard.  
  > **username_3**: As such, the paragraph you quote only states the obvious: "You can tinker with the standard in any way you want, but if your program wants to be understood by other programs, you have to translate to English".  
  > **username_0**: So you basically mean that I can make a programme that reads PGN that way, but no mainstream PGN readers does so, right? Thanks for your answer! (+1)  
  > **username_3**: @HarryWeasley Yes.  
  
  ---
  
  ### Answer by username_1 on 2018-03-09. Score: 4
  
  The specification you have in your link has no practical meaning as the format is not enforced consistently. Steven J. Edwards introduced the format, but he didn't have authority to control how programmers implement PGN.
  
  **Most PGN parser would only support the English language.**
  
  I've been distributing PGN parsing softwares for years, but I don't think I'll add foreign language support. I assume anyone who is intelligently capable of playing chess would be able to read English piece identifiers.
  
  > **Comments:**
  > **username_2**: In case anyone wants to parse Dutch or German input, my pgn-extract program (https://www.cs.kent.ac.uk/~djb/pgn-extract) has supported both for most of its life, and there is also an option (-Wsan) that would allow output to an arbitrary set of single-character letters if desired.  
  > **username_1**: @username_2 Thanks for your excellent work on PGN. Your software is an exception :-)  
  > **username_0**: @username_2 That is very interesting! Thanks!  
  
  ---
  
  