user13565: I came across this in the PGN standard on this site, 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 *


user825: 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. 

user13433: 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.

13565: <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>
 825: <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>
 13433: <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>
