up | previous | next | firstname.lastname@example.org
When you choose the modify character translation tables operation from the main menu, LifeLines displays the character translation menu:
Which character mapping do you want to edit? e Editor to Internal mapping m Internal to Editor mapping i GEDCOM to Internal mapping x Internal to GEDCOM mapping d Internal to Display mapping r Internal to Report mapping q Return to main men
LifeLines has little built-in knowledge of character codes. If you use 7-bit ASCII characters you will not encounter problems. However, many European and other languages require additional characters, and there are many 8-bit and other schemes for encoding those characters. LifeLines knows about none of them. However, LifeLines provides a few character translation features you can use to help manage character translation.
LifeLines provides facilities for mapping between characters whenever a data record changes form. LifeLines supports four forms:
When converting text from one form to another LifeLines normally does not convert characters codes. You may, however, override this default behavior by creating translation tables for LifeLines to use when converting between forms. There are six translation tables you may define. The following lists the six tables and describes when they are applied:
After you select a translation table you are placed in your screen editor to edit the table. Translation tables are made up of lines that look like:
where a tab separates the two patterns. Each pattern is an arbitrary sequence of verbatim ASCII characters and escape sequences. Translation occurs by finding all occurrences that match left patterns and replacing them with the corresponding right patterns.
There are four escape mechanisms used in patterns:
#nnn nnn is a decimal character value $hh hh is a hexadecimal character value \# represents the # character \$ represents the $ character \\ represents the \ character
The character translation feature is not fully tested, and not all translations are currentlyimplemented.
up | previous | next | email@example.com/1/00