This is an old revision of the document!
Editing transliteration should be a simple affair. After all, it only use a few alphabetic signs. Alas, it isn't. In the MdC, a simple, ASCII-based standard was used. But this standard requires special fonts, where “a” are not “a” but “ayin”. This lead to many problem when texts where exchanged. Passing from Mac to PC was a real problem, and publishers were very unhappy. Hundreds of hours of unnecessary work was spent converting files - or re-typing them.
Normally, Unicode should solve all those problems1). So, currently, JSesh proposes choices to the user. Your personal choice will depend on what you want to do with your texts. It's quite likely that unicode is needed for most publications, for instance.
You can choose the way transliteration will be dealt with from the Preference menu.
You can select a font with a MdC-compatible encoding. In this case, JSesh does not deal with capital letters. You can choose your own font, if you have one, or use the default JSesh transliteration font. A version of this font is embedded in the software, but you can install it on your system (to use with a word processor, for instance). A copy of this font is available in the font folder of JSesh installation.
You should open the “Preferences” menu (on the Mac, it's in the “JSesh” menu; elsewhere, it's under the “Edit Menu”). Go to the “Font Preferences” Tab, and click the “use old transliteration font” button.
That's it. For your own Word (or OpenOffice…) documents, you can find the font in the JSesh application folder (in the “font” folder).
If you have a font compatible with the MdC (that is, the “a” represents an ayn, the “A” represents an aleph, etc…), you can use it too.
Simply select your font (using “Choose font” in front of the Transliteration font), and then, in the advanced options, select “MdC (non Unicode) Transliteration font”.