Difference between revisions of "Transliteration"
From CrossWire Bible Society
(→Front-ends that support Transliteration: STEP doesn't use ICU or Sword's standard transliteration facilities and is thus severely less capable relative to other front ends) |
(→International Components for Unicode (ICU)) |
||
| Line 6: | Line 6: | ||
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. | 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 16:38, 26 August 2013
- 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
