Difference between revisions of "Transliteration"
From CrossWire Bible Society
David Haslam (talk | contribs) (→Front-ends that support Transliteration: added diatheke, made each frontend a wikilink or link) |
David Haslam (talk | contribs) m (→Front-ends that support Transliteration: edited 2 wikilinks) |
||
Line 9: | Line 9: | ||
=== Front-ends that support Transliteration === | === Front-ends that support Transliteration === | ||
− | * [[Frontends:Diatheke]] | + | * [[Frontends:Diatheke|Diatheke]] |
− | * [[Frontends:Xiphos]] | + | * [[Frontends:Xiphos|Xiphos]] |
* [[Frontends:BibleCS|The SWORD Project for Windows]] (''aka'' BibleCS) | * [[Frontends:BibleCS|The SWORD Project for Windows]] (''aka'' BibleCS) | ||
* [http://bpbible.com/ BPBible] – available only if compiled with ICU | * [http://bpbible.com/ BPBible] – available only if compiled with ICU |
Revision as of 07:37, 14 May 2020
- 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
- Diatheke
- Xiphos
- The SWORD Project for Windows (aka BibleCS)
- BPBible – available only if compiled with ICU