openerp-india team mailing list archive

["Olivier Dony \(OpenERP\)" <929607@xxxxxxxxxxxxxxxxxx>]

Hello,

Thank you for the additional details. I'm sorry to insist on this, but providing sufficient context on *every* bug report is essential. Remember that people on the other side of the internet can't see what you're doing and cannot read your mind ;-)
It only takes 10 more seconds of effort when reporting the bug, but can save several back and forth questions on each bug report for both the reporter and the developers handling bugs - so hours of work every month.
The key information here was that you were looking at the EDI module translations.

As for the reason why the sentence appears "cut" in the translations, this is a limitation of the current way we extract terms to translate in XML document (such as RML reports, web templates, etc.)
Each "text" element in the XML is handled as a separate term to translate, because there is no easy way to automatically know if 2 text elements separated by a single XML node are meant to be translated as one or not.

Therefore the following XML snippet:
  <div>You can open the following <a href="....">link</a> to preview the invoice</div>
will be extracted as 3 different terms to translate:
  - "You can open the following "
  - "link"
  - " to preview the invoice"

This is not always easy to translate, but if you are reviewing translations you will often see them one after the other and be able to make the connection between them (possibly going back to the previous one to correct the translation.
This is also why it is important for translators to look at the "context" provided at the bottom of each translation.
If you look at the german translation interface for the sentence you are referring to, i.e.:
   https://translations.launchpad.net/openobject-addons/trunk/+pots/edi/de/+translate?batch=10&show=all&search=independent
You will notice that the context line at the bottom says:
  Located in /home/odo/repositories/addons/trunk/edi/static/src/xml/edi.xml:54 
You could easily open the corresponding source file on Launchpad next to the translation interface to double check the context of that term, it's as easy as copy-pasting the part of the path starting with the module name "edi/static/src/xml/edi.xml" at the end of the root URL for viewing the project's source code, which is for addons: "http://bazaar.launchpad.net/~openerp/openobject-addons/trunk/files/head:/";
You can also find the file by clicking on "Browse the code" on the branch summary page.

Looking at line 54 mentioned in the context, you will immediately see how that term is part of a longer sentence, and how to properly translate it:
  http://bazaar.launchpad.net/~openerp/openobject-addons/trunk/view/head:/edi/static/src/xml/edi.xml#L54

In the future we might introduce more flexible terms that translators
are able to reorganize the sentence instead of having to work on it in
several fixed parts. But currently that would cause the XML templates to
be much more complicated and hard to read and maintain.

Thanks,

** Changed in: openobject-addons
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/929607

Title:
  edi help text

Status in OpenERP Addons (modules):
  Invalid

Bug description:
  OpenERP's Electronic Data Interchange documents are based on a generic
  and language

  something missing?

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/929607/+subscriptions