[Libreoffice-qa] Existing German translation in Moztrap

[Yifan Jiang]

Hi *,

The repo is here (silently), may be I should make it available for
@tdf searching :)

    https://github.com/yifanjiang/moztrap

The important hacking on this branch is OpenID login implementation.

As for the localization, IMHO, is inevitably considered divided into 2
levels:

    1. the UI level

    The content is relatively "static" in moztrap *code*, usually
    *translated* word by word.

    Yes, with Django framework, it is not that complicated to leverage
    pootle approach to translate the UI of Moztrap, where UI indicates
    any text else except test cases content in Moztrap.

    But, I doubt it is really necessary to implement and MAINTAIN this
    even if the word-by-word translation has been highly automated:

    http://translate.google.com/translate?hl=en&sl=en&tl=de&u=http://manual-test.libreoffice.org/results/runs/

    2. the test case level

    The content is relatively "dynamic" in moztrap *database*, usually
    *localized* sentence by setence or paragraphs by paragraphs. The
    similar way of UI level translation does make sense in the first
    place, however *database* level translation is not that easy as
    what we did in *code* level in a Django framwork. It may be needed
    to deeply reconstruct the moztrap core tables, and hook together
    pootle like translation content with the refined moztrap database.

    In another word, yes, technically it can be more complicated :)

Best wishes,
Yifan

On Thu, Nov 14, 2013 at 09:20:32AM +0100, Thomas Hackert wrote:
> Hello Robinson, *,
> On Donnerstag, 14. November 2013 08:59 Robinson Tryon wrote:
> > On Thu, Nov 14, 2013 at 2:50 AM, Thomas Hackert
> > <thackert at nexgo.de> wrote:
> >>
> >>> At least the first part (localizing the interface) seems like it
> >>> just
> >>> needs someone to go poke at the code for a while  (no, I'm not
> >>> raising my hand right now... :-)
> >>
> >> I cannot help here as well, sorry ... :( If I read the above side
> >> right, it is just some kind of Python hook. But how do I see, if
> >> localization is enabled in our Django installation?
> > 
> > I don't see a TDF fork of moztrap up on Github:
> > https://github.com/search?q=%40tdf++moztrap
> 
> there is no Django fork there as well 
> (https://github.com/search?q=%40tdf++django) ... :(
> 
> > Maybe the repo lives elsewhere?
> 
> Maybe. But I am not one of our admins, so ... ;)
> 
> >> And I found on
> >> 
> https://docs.djangoproject.com/en/1.6/internals/contributing/localizing/,
> >> that the project uses transiflex (https://www.transifex.com/)
> >> itself to translate their software. Does it mean, we have to
> >> switch to transiflex as well?
> > 
> > I think that's just what django uses for their own work. I think
> > that lots of tools support the ".po" file format, so we can stick
> > with whatever system we currently have in place (pootle, IIRC).
> 
> That would be nice :)
> Thomas.
> 

-- 
  Yifan Jiang
  SUSE Desktop, Libreoffice /SUSE
  Contact: yifan - irc.freenode.net/libreoffice
  =============================================  
  http://www.libreoffice.org/
  http://www.documentfoundation.org/