Menu

Localization guide

Help
Chrissyx
2010-03-20
2013-04-26
  • Chrissyx

    Chrissyx - 2010-03-20

    In case you want to translate the AuthorSupportTool entirely into another language, I have written a guide how to achieve this. It covers all the files you have to care about and provides some recommendations as well. I assume some basic knowlege about XML.
    Note: Steps 5 and 6.1 might be optional, but I've listed them here for sake of completeness.

    1) The main file is the PO file. I suggest using Poedit, download it here: http://www.poedit.net/
    The most strings contain natural language, but there are also some technical strings. Be careful translating those, otherwise ask here first.
    Get the english PO file here: http://astool.svn.sourceforge.net/viewvc/astool/data/poedit/Messages_en.po
    Save your new translation as Messages_xx.po, where xx is your overall language code.

    2) A small description is required and displayed in the Extension manager.
    http://astool.svn.sourceforge.net/viewvc/astool/src/BesserWissA/description/description_en.txt
    Keep the sentence really short, because space is limited in the manager. Save it as a new text file with the name description_xx.txt, where xx is your overall language code.

    3) The options dialog is not covered by the PO file and needs a seperate translation file.
    http://astool.svn.sourceforge.net/viewvc/astool/src/BesserWissA/dialogs/ASTLeaf_en_US.properties
    You only need to translate the existing strings. Save it as a new file with the name ASTLeaf_xx_XX.properties, where xx is your overall language code and XX the detailed one.

    4) Next part are the AST menu entries.
    http://astool.svn.sourceforge.net/viewvc/astool/src/BesserWissA/registry/data/org/openoffice/Office/Addons.xcu
    Edit this file and add your translation to the current ones. Only consider the <value xml:lang="xx"> tags, where xx is your overall language code. Save it when you're finished.

    5) No translation is required here, only an addition inside the <prop oor:name="Label"> tag.
    http://astool.svn.sourceforge.net/viewvc/astool/src/BesserWissA/registry/data/org/openoffice/Office/OptionsDialog.xcu
    Edit this file by adding a new <value xml:lang="xx-XX"> tag, where xx and XX are the usual language codes. Save it when you're done.

    6) Several changes are needed to be done here:
    http://astool.svn.sourceforge.net/viewvc/astool/src/BesserWissA/src/description.xml
    The easiest way to perform the following steps would be loading up the full AST project into NetBeans with installed OOo API plugin. Rightclick on the project entry, choose Properties and edit them accordingly to your new translation.
    To do it manually without NetBeans GUI:
    6.1) Add a new <name lang="xx"> tag to the <display-name> block, where xx is your overall language code. No translation needed.
    6.2) Add a new <name lang="xx" xlink:href="…"> tag to the <publisher> block, where xx is your overall language code. You have to translate the word "project" of the link description here.
    6.3) Link your text file from step 2 by adding a new <src lang="xx" xlink:href="description/description_xx.txt" /> tag to the <extension-description> block. Replace xx as usual.

    7) If you even want to translate the manual, follow these steps otherwise skip.
    Create a new folder and name it after your overall language code xx. Place in this file:
    http://astool.svn.sourceforge.net/viewvc/astool/src/BesserWissA/help/en/help.tree
    Edit the path inside the topic tag and translate the word "Extension" (part of the node tag).
    Create a new folder inside your current one with the name "ast.BesserWissA"
    Now place inside that newly created folder this file:
    http://astool.svn.sourceforge.net/viewvc/astool/src/BesserWissA/help/en/ast.BesserWissA/ast_page1.xhp
    Work your way through the XHP file translating all the manual entries and language codes. Be careful regarding consistently naming! Your translation should conform to the strings used in the PO file before.

    8) You're done! Commit your new and changed files to the repository OR send them to us instead. Your package should contain:
    New files:
    - Messages_xx.po
    - description_xx.txt
    - ASTLeaf_xx_XX.properties
    - xx/help.tree (optional)
    - xx/ast.BesserWissA/ast_page1.xhp (optional)

    Edit files:
    - Addons.xcu
    - OptionsDialog.xcu (possible optional)
    - description.xml

    We will add your localization to the AST tool and parse the PO file for you.

    Happy translating!
    Chris

     
  • Gibarian

    Gibarian - 2011-02-07

    The links to retrieve de english PO file are not working… Please update them…

     
  • Chrissyx

    Chrissyx - 2011-02-07

    The links are correct, but SourceForge has some ongoing issues with the repositories right now. See here for details:
    https://sourceforge.net/blog/update-on-services/

     
  • Luis Mora

    Luis Mora - 2011-03-07

    Hi, the tool seems like a great idea, but the page ast.informatik.uni-bremen.de / does not work, I can not connect to the server, if you need collaboration for servicing the site and the translation tool to Spanish just let me know.

     
  • Chrissyx

    Chrissyx - 2011-03-07

    Yes, the site is not available, but will hopefully return soon. However, feel free to finish the current incomplete Spanish translation as you like. Don't expect too much support from our side, since the project ended officially in Sep 2010.

     
  • Luis Mora

    Luis Mora - 2011-03-08

    Yes, I could see that the project was conducted as part of a course at the University of Bremen with Prof. Karl-Henz think. If you want I can talk with a friend who is the administrator of a server, to give them space. As the project I think is a good tool for those who use libreoffice and openoffice and still do not use LaTeX, you should not leave, there are parts that still do not understand how to use the SVN service sometimes leads to problems, I think it is my inexperience, however, would be good to create you a user manual in pdf.

     
  • Chrissyx

    Chrissyx - 2011-03-13

    Webspace is not the problem and the site is currently moving to a permanent location at the university. I don't know the details, since I'm not there anymore.

    Help contents are available as a built-in user manual. See here:
    Help -> OpenOffice.org Help -> Tab 'Content': Extensions -> AuthorSupportTool Extension -> AuthorSupportTool
    I've written a section about SVN usage as well.

     
  • B. Vollmer

    B. Vollmer - 2011-03-22

    The project homepage at the university of bremen is now online again.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.