Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


Hi Petr,

(forwarding for info to l10n@libo)

thanks for the update - all correct, but one addition:

We might be able to provide a pootle server for 3.3 as well. But all
people who are fine with directly pulling po-files and sending these
to the mailing list, should go on as suggested.

André


Von: Petr Mladek <pmladek@suse.cz>
An: libreoffice@lists.freedesktop.org

first, we are really happy to hear that so many people would want to
help with translating LibreOffice.

We will use a temporary process for 3.3 and something better for the
next releases.


Proposed process for LibreOffice-3.3:

      + we are going to regularly merge ooo330-mX, so we will get
          translation for most strings from OOo-3.3 sources


      + the libreoffice-specific strings are listed in
          libreoffice/build/po/lo-build.pot, see
http://cgit.freedesktop.org/libreoffice/build/tree/po/lo-build.pot

          Some of the strings are already translated in the 
          libreoffice/build/po/lo-build-<lang>.po files, see
http://cgit.freedesktop.org/libreoffice/build/tree/po

          Please, help us to have 100% translated strings in the
          lo-<lang>.po files

        You might send your changes to this mailing list and someone
          with a commit access will push them to the git.

          Of course, you might also ask for commit access. Though, I
          am not sure if it is worth for this temporary process.

          Note that you might ignore libreoffice/build/po/<lang>.po
          files. They are used for desktop integration by some Linux
          distributions. They are not important for LibreOffice.
          They will most likely get removed soon.


      + if you want to fix a string that is not in lo-build.pot,
          you might create a reduced .sdf file and we will put it
          as a hotfix into libreoffice/build/src/sdf

          It is a bit inconvenient but it is only for LO-3.3 release.

          Let us know if you have troubles to create the sdf file. We
          will try to help you with it. Personally, I would try to base
          it on the existing .sdf file in the l10n source module, see
http://cgit.freedesktop.org/libreoffice/l10n/tree/l10n/source
          
          
Plans for the future:

      + we would like to setup a pootle server and allow to translate
          all LibreOffice strings at the same place a convenient way
      + the strings will be extracted from the pootle server and
          used for the regular test builds


Schedule for LibreOffice-3.3:

      + libreoffice/build/po/lo-build.pot and lo-build-<lanf>.po
          have been just updated, so they follow the current state
          => please, start with contributing

      + string freeze will be at the end of October; I expect only
          very few new strings; nobody should add any huge feature at
          this stage

        + final release date is a bit unclear; My estimation is December
          but I am not the one who would decide ;-)


Any hints how to improve the processes are welcome.

André, please fix me if any information above is wrong or if you suggest
any improvement. You are much bigger expert here. I just try to solve
the technical problems... :-)


Best Regards,
Petr

_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

-- 
GRATIS! Movie-FLAT mit über 300 Videos. 
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.