Add bgnpcgn-Afgn-Latn-2007 system

[ronaldtse]

From @manuel489

[ronaldtse]

@manuel489 I've updated the file and fixed some issues. Notice that not all characters can be copied and pasted, we will need to use the unicode numbers directly, sometimes multiple code points for a single character (e.g. n with top bar).

[ronaldtse]

1. Please help fill in the transliteration table.

2. This document also defines the "Yaghoubi" system, which should be encoded as a separate YAML file.

[manuelfuenmayor]

Hi @ronaldtse,
I have pushed my changes. I did both BNG/PCGN and Yaghoubi systems in separated files.

I'd like to make some comments:

1. There are several cases where a Unicode value is repeated.
2. I couldn't find an acronim for "Afghan" in ISO 639-2 code. So, I wrote "afg" according to ISO 3166-2.
3. There were cases where I used four unicode values in a row to depict a Latin character.
4. There were several Unicode values enclosed between parentheses (I didn't use them).

[ronaldtse]

1. There are several cases where a Unicode value is repeated.

Could you explain which these cases are?

2. I couldn't find an acronim for "Afghan" in ISO 639-2 code. So, I wrote "afg" according to ISO 3166-2.

The language code should be prs for Dari (https://iso639-3.sil.org/code/prs). I fixed it in 0265be7.

3. There were cases where I used four unicode values in a row to depict a Latin character.

Each source character should be implemented as a separate rule.

e.g. these:

 # VOWELS  
  'ئه' / 'ه' : 'e' # See notes 1 and 5
  'ئا' / 'ا' : 'a' # See note 1
  'ئي' / 'ي' : 'î' # See notes 1, 6 and 7

Should be implemented as:

 # VOWELS  
  'ئه' : 'e' # See notes 1 and 5
  'ه' : 'e' # See notes 1 and 5
  'ئا' : 'a' # See note 1
  'ا' : 'a' # See note 1
  'ئي' : 'î' # See notes 1, 6 and 7
  'ي' : 'î' # See notes 1, 6 and 7

[manuelfuenmayor]

Could you explain which these cases are?

@ronaldtse, for example:

[manuelfuenmayor]

@ronaldtse, why text paragraphs must be splitted in several lines?

[ronaldtse]

Ah, because it reads better in the editor :-)

[ronaldtse]

Same for these comments to be on separate lines. In addition, comments and code lines should be separate, so that git tracks the actual change in code vs comments, instead of mixing changes for code vs comments.

[AhMohsen46]

superseded by https://github.com/interscript/interscript/pull/441