Consider the file Encoding.cpp. There is a table named arabic_table and four methods all related to the arabic language defined in this file. The table contains different shapes of each character in unicode. The methods are as follows: 1. is_arabic_special(character) -> returns whether the given character joins to the letters on its left 2. isComposeChar_arabic(character) -> returns whether the character is an arabic compose character 3. is_arabic(character) -> returns whether the character is an arabic character 4. transformChar(character, shape) -> returns the requested shape of an arabic letter --------------------------------- I would like to add Farsi support based on ARABI package to LyX. Starting with Encoding.cpp file, one way is to provide a farsi_table similar to arabic_table. But since most of the characters are similar it seems reasonable to just extend the existing arabic_table to contain the farsi characters too. This way it is necessary to update some of the mentioned methods of arabic too. But the problem is that the table becomes a table with nearly [200][4] items such that many of its internal items are empty (that belong to other arabic-like languages). The good thing is that this way adding other arabic-like languages to LyX becomes easier later. Anybody has any other idea?
--------------------------------- Don't pick lemons. See all the new 2007 cars at Yahoo! Autos.
