Difference between revisions of "Transliteration"
From CrossWire Bible Society
David Haslam (talk | contribs) (→International Components for Unicode (ICU): === Front-ends that support Transliteration ===) |
David Haslam (talk | contribs) (→Front-ends that support Transliteration: === Transliteration options ===) |
||
| Line 12: | Line 12: | ||
[[Category:Transliteration]] | [[Category:Transliteration]] | ||
| + | |||
| + | === Transliteration options === | ||
| + | |||
| + | Whereas Xiphos offers transliteration as a module option, giving an alternative view of the module, other ideas might be explored by front-end developers. Here are some ideas that might be considered: | ||
| + | |||
| + | * Interlinear display option, with the original text and transliterated text on alternate lines | ||
| + | * Index the transliteration to provide search feature support | ||
Revision as of 18:29, 18 October 2010
- 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 scripts. The tools are well developed already—it's simply a matter of adding data.
Front-ends that support Transliteration
- Xiphos
Transliteration options
Whereas Xiphos offers transliteration as a module option, giving an alternative view of the module, other ideas might be explored by front-end developers. Here are some ideas that might be considered:
- Interlinear display option, with the original text and transliterated text on alternate lines
- Index the transliteration to provide search feature support
