Difference between revisions of "Transliteration"
From CrossWire Bible Society
David Haslam (talk | contribs) (→Ruby markup: [http://www.w3.org/TR/ruby/]) |
(→Transliteration options: moving to talk page, since it looks like discussion, rather than information) |
||
| Line 14: | Line 14: | ||
[[Category:Transliteration]] | [[Category:Transliteration]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=== Ruby markup === | === Ruby markup === | ||
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. | 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 02:41, 19 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
- The SWORD Project for Windows (aka BibleCS)
- BPBible – available only if compiled with ICU
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.
