1. Mailing Lists
  2. Germany
  3. Re: [14966] Translation and GoBD issues

Germany mailing list archives

germany@odoo-community.org

Browse archives

Re: AW: [14966] Translation and GoBD issues

Avatar

Re: [14966] Translation and GoBD issues

by
OpenBig, Thorsten Vocks
- 16/02/2017 12:17:38
Hello Frederik, 

at first sorry for the late reply. Before transifex times (since V9) only a few people was involved to finish most translation terms (+90%) in a time frame between 4-8 weeks before the official release. We could avoid different "flavours" of translations and it was easier to agree consistent terms.

The drawback was the high workload for only a few people.  By moving to transifex (since V9) it was required for Odoo SA to open the door to everyone, as translations was not any more a natural part of the process to release a completed new version. 

Therefore the translation process changed since V9:

* many new translators collaborate only few translation terms  more or less "on demand" (f.e. for presentations or for early project roll-outs).

* translation work even for countries with obviously many Odoo customers like germany is not anymore part of the official release planning.

* the translation process is flatered between many voluntary people

* (as a result) reviewing is more difficult and more time intense due to different "flavours" and non-consistent terms. Example: some very engaged translators with a specific flavor from switzerland or austria.

* no updated glossary, no guideline about the "how to" exists. 

* large team with many unexperienced translators are working to close translation gaps even 1 year after the official release date

* overall translation workload is higher, due to introduction of very long terms (qweb reports, email templates, contextual help terms, configuration wizards ...)

* voluntary translators with significant workloads and responsibility didn't get funds or equivalent promotion neither from Odoo SA nor from successfull resellers or any other kind of "crowd" funds. Customers simply expect a completly translated version.

* overall it seems that Odoo SA regards translations as not important enough and further more they think it is very easy and a task for everyone. 


Proposal to improve translations:

* re-integration into release planning (=no release publishing before finishing the translations).

* funding of some main translators and reviewers (in a pre-defined period before the official release date), f.e. by defining a certain rate of Odoo SaaS / OE earnings from the country to finance the translation work.  

* possibility to report translation issues in a end-user friendly way.

* introduction of a responsible maintenance team to fix translation issues.

* invitation to voluntary translators to collaborate by offering the possibility to translate directly in Odoo ("translator mode" to record all translations for a predefined language and to be able to export that list of changes to the personal google spreadsheet of a translator, re-import of re-edited spreadsheet data would be fine for a iterative process and to share intermediate work between several translators). Finally another next and optional step of public collaboration would be to share the google spreadsheet with a community bot who is responsible to transform all new or modified translations from the google spreadsheets into automated proper pull requests for github. 

By default the bot should create a pull request either against the Odoo OCB branch on github, or against Odoo community edition, if Odoo SA agrees to finance the system. In best case it should be possible for a collaborating translator to configure alternative targets. The targeted repo(s) should be selectable or configurable before starting the recording. 

The collaborator should be notified by email after the bot finished his work. The bot should provide him a .po or whatever file he could reuse on other Odoo systems or database to immidiately update incomplete translations on his database. Furthermore the email should include the link to the pull request or minimum to the targeted repo as a service.

I guess this could be a typical case for a ETL process. There are 
some mature Open Source tools to do that and some guys from 
Odoo community already use these tools.


For sure a commercial bot offer, can refinance development and maintenance of bots where people want to target closed source repos or their own private repos.



Thorsten Vocks

openBIG.org
Dipl. Kaufmann (FH)
Porscheweg 4-6
49661 Cloppenburg

Phone: +49 4471 8409000
Fax: +49 4471 84090009
Mail: thorsten.vocks@openbig.org

              

2017-01-25 15:22 GMT+01:00 Frederik Kramer <frederik.kramer@initos.com>:
Dear German Odoo Community, 

first of all i wish all of you a happy and succesful 2017. Quite some
time ago i mentioned that we at initOS are currently working on some
projects towards GoBD compliance not limited to but including Odoo. If
somebody has a similar effort ongoing or would like to join, just let
me know.

Doing some project on Odoo 10 some of our PMs and developers again
outlined the rather incomplete and partly poor translation of Odoo.
What about a joint community effort in that regard. Is somebody aware
of the current status of official tools to do the translation task ?

@Thorsten: I would be eager to get especially your opinion about the
state of the German Odoo community efforts and potential ways to
improve here and there.

Looking forward to receive your feedback

Cheers Frederik
-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155

_______________________________________________
Mailing-List: http://odoo-community.org/groups/germany-18
Post to: mailto:germany@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


Reference