Difference between revisions of "Transliteration"
David Haslam (talk | contribs) (→Transliteration options: === Ruby markup ===) |
David Haslam (talk | contribs) (→Ruby markup: [http://www.w3.org/TR/ruby/]) |
||
| Line 24: | Line 24: | ||
=== Ruby markup === | === Ruby markup === | ||
| − | A module could be created with the transliterated words coded in OSIS using Ruby markup. This may be especially useful for transliterating those languages which are not yet supported by ICU. | + | A module could be created with the transliterated words coded in OSIS using Ruby markup.[http://www.w3.org/TR/ruby/] This may be especially useful for transliterating those languages which are not yet supported by ICU. |
Revision as of 18:48, 18 October 2010
- New page under construction. Please add content.
Contents
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
- The SWORD Project for Windows (aka BibleCS)
- BPBible – available only if compiled with ICU
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
- Keyboard entry of transliteration words in the search dialogue for the original text
Ruby markup
A module could be created with the transliterated words coded in OSIS using Ruby markup.[1] This may be especially useful for transliterating those languages which are not yet supported by ICU.
