On Wed, Feb 25, 2004 at 12:11:30AM -0500, Alexander R. Pruss wrote: > I'm thinking of adding a couple more transliteration tables to the search > (e.g., drop Latin2 accents, Cyrillic->ASCII, etc.; these are really handy > for users who don't want to pay for a localization to read some texts in a > foreign language--or else for languages where there might not be any > localization (e.g., ancient Greek).) I'm wondering how best to do it. >
If written as a generic function, it could be used for displaying text if you happen not to have the font you need - the texts will be at least a bit readable. > The simplest way is just to hard-code a couple more in. Don't forget, that is you want enough generality, you have to allow 1->N scheme (e.g. one input char can be transliterated as a string of more characters). Ideally, it should be even M->N (e.g. in one rather popular russian transliteration, U+0435 CYRILLIC SMALL LETTER IE should be "je" or "ye" at the beginning of word and after vowels other than U+0438 CYRILLIC SMALL LETTER I, "ie" after some consonants, and "e" everywhere else - guess where "soviet" comes from? :-)), but I guess that is already too much for plucker, and simple 1->N would be sufficient. -- ----------------------------------------------------------- | Radovan Garab�k http://melkor.dnp.fmph.uniba.sk/~garabik/ | | __..--^^^--..__ garabik @ melkor.dnp.fmph.uniba.sk | ----------------------------------------------------------- Antivirus alert: file .signature infected by signature virus. Hi! I'm a signature virus! Copy me into your signature file to help me spread! _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
