Difference between revisions of "Transliteration"
From CrossWire Bible Society
(moving to talk) |
David Haslam (talk | contribs) (→International Components for Unicode (ICU): writing systems) |
||
| Line 5: | Line 5: | ||
Some SWORD front-end applications use libsword ICU to provide a [http://en.wikipedia.org/wiki/Transliteration transliteration] feature. For example, in [[Frontends:Xiphos|Xiphos]], when you right-click in a non-Latin script module, you can see this in action. | Some SWORD front-end applications use libsword ICU to provide a [http://en.wikipedia.org/wiki/Transliteration transliteration] feature. For example, in [[Frontends:Xiphos|Xiphos]], when you right-click in a non-Latin script module, you can see this in action. | ||
| − | The nice thing about ICU is that we can add data to it. Chris has done this for several | + | The nice thing about ICU is that we can add data to it. Chris has done this for several writing systems. The tools are well developed already—it's simply a matter of adding data. |
=== Front-ends that support Transliteration === | === Front-ends that support Transliteration === | ||
Revision as of 17:07, 16 February 2012
- New page under construction. Please add content.
International Components for Unicode (ICU)
Some SWORD front-end applications use libsword ICU to provide a transliteration feature. For example, in Xiphos, when you right-click in a non-Latin script module, you can see this in action.
The nice thing about ICU is that we can add data to it. Chris has done this for several writing systems. The tools are well developed already—it's simply a matter of adding data.
Front-ends that support Transliteration
- Xiphos
- The SWORD Project for Windows (aka BibleCS)
- BPBible – available only if compiled with ICU
