[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libreoffice-l10n] Updated Bengali (bn) Translation.

У сре, 06. 10 2010. у 03:39 -0700, Jamil Ahmed пише:
> Btw, I did not get any "bn.po" file in the repository. Any pointer please?

Hi Jamil,

You can use any other, for example sr.po, edit the header and
remove/overwrite all translations. At the moment there is no POT file
extracted for these .desktop files. Note also the comment posted at the

> http://www.freedesktop.org/wiki/Software/LibreOffice/i18n/translating_3.3
> Translators could ignore build/po/<lang>.po files. They are still used
> by some Linux distributions. They are not used for the official
> LibreOffice build. They are getting obsolete by the desktop
> integration from the LO sources.

On the other hand, you do want to work on the lo-build-bn.po file. Just
1% of the file is translated in this moment.

If upstream OpenOffice.org translation is not at 100%, there are more
strings, but at the moment I do not think we have a process defined how
to handle those.

Kind regards,
Goran Rakic

To unsubscribe, e-mail to l10n+unsubscribe@libreoffice.org
List archives are available at http://www.libreoffice.org/lists/l10n/
All messages you send to this list will be publicly archived and cannot be deleted.

Re: [libreoffice-l10n] Updated Bengali (bn) Translation.Jamil Ahmed <itsjamil@gmail.com>
[libreoffice-l10n] Updated Bengali (bn) Translation.Jamil Ahmed <itsjamil@gmail.com>
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.