- From: r12a via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Nov 2019 10:22:18 +0000
- To: public-i18n-archive@w3.org
The group discussed this in https://github.com/w3c/alreq/issues/16 and concluded that we would use the LOC transcription for Arabic, and the UNGEN transcription for Persian. However, I can readily believe that we need to tidy up some of the transcriptions in the document. The arabic and persian character apps are equipped with converters, and we used to use those to improve consistency and accuracy. For arabic, go to https://r12a.github.io/pickers/arabic/ and select Transcribe to LOC from the pull down next to Character Markup, top right. For Persian, go to https://r12a.github.io/pickers/persian/ and select Persian to UN from the same pulldown. The tool needs the text being converted (in the large box) to be vowelled for best results (esp. in arabic). (Btw, note that we maintain a distinction between 'transliteration' and 'transcription'. The former is a 1-to-1, roundtripable correspondence between arabic and latin script letters, and the latter is often closer to the phonetics but typically doesn't allow reversible conversions. Both the LOC and UNGEN schemes are used as 'transcriptions'. ) SIL and Noto provide Latin fonts that cover all the non-ASCII characters. with ease. I suggest that we include one of those as a .woff font in the stylesheet and map it to `class="trans"` and `class="lettername"`, which we should use for all transcription text. -- GitHub Notification of comment by r12a Please view or discuss this issue at https://github.com/w3c/alreq/issues/204#issuecomment-555939081 using your GitHub account
Received on Wednesday, 20 November 2019 10:22:20 UTC