[Project-ideas] [Anubad] [GSoC]: Editor for DTD Translations

[shreyankg at gmail.com]

On Sun, Mar 25, 2012 at 6:01 PM, Sankarshan Mukhopadhyay
<sankarshan.mukhopadhyay at gmail.com> wrote:
[..]
>> I've been going through the working of Gtranslator and I think I've
>> understood the way it works.
>>
>> So, the basic layout of a .po file is as follows:-
>>
>>     white-space
>>     #  translator-comments
>>     #. extracted-comments
>>     #: reference...
>>     #, flag...
>>     #| msgid previous-untranslated-string
>>     msgid "untranslated-string"
>>     msgstr "translated-string"
>>
>> Now, what Gtranslator does is that it extracts the untranslated-string
>> from within the double quotes in msgid and displays it as the Original
>> Text. The interface provides a text area wherein the Translated Text
>> can be input. This input text is then stored within double quotes in
>> the .po file as msgstr.
>>
>> The basic layout of DTD files that need translation is as follows:-
>>
>>    <!--License Block-->
>>    <!-- General -->
>>    <!ENTITY element_name "msgstr">
>>    <!-- LOCALIZATION NOTE-->
>>    <!ENTITY element_name "msgstr">
>>    <!--Entity Specific Comments-->
>>    <!ENTITY element_name "msgstr">
>>
>> The application extension that would enable the translation of DTD
>> files should ideally be able to fetch the msgstr from the entity tags,
>> store it in a temporarily in memory and display it as the Original
>> Text Area of the User Interface. Similar to the existing system the
>> Translated String can be input in the Translated Text area. This input
>> string can then be used to replace the existing msgstr within the
>> double quotes.
>>
>> The proposed system would thus require very little or no modifications
>> to the existing basic User Interface.
>>
>> However, the main difference between the PO and DTD translation files
>> is the fact that the PO file contains record of the Original Text
>> whereas the DTD file contains only the Translated Text. This however
>> can be overcome by a small change in the way the extension would store
>> the translated text. Instead of replacing the msgstr in the original
>> entity itself, the extension can be customized to comment out the
>> original entity declaration and replace the msgstr in a copy of the
>> entity declaration as follows:-
>>
>>    <!--<!ENTITY element_name "Untranslated msgstr">-->
>>    <!ENTITY element_name "Translated msgstr">
>>
>> This is my basic proposal for the Translation Editor Extension for
>> Gtranslator. The main reason behind my intention to create this
>> extension for Gtranslator is that I personally am more proficient in
>> Gtranslator than Lokalize. However, once I successfully complete the
>> extension I would also like to work on Lokalize, if not during GSoC,
>> then after GSoC.
>>
Your research is good, and so is you plan.

Except for that fact that gtranslator is not that popular anymore, nor
is it maintained. It would be great to see this as a feature to a more
popular application, and I would put my money on lokalize.

-- 
Peace and Love,
Shreyank Gupta
Blog: http://allsortsofshrink.blogspot.com