Hello Andars,
Thankyou very much for giving me guideline about merging. I have merged
again. Here the new links for both UI and help. Please check.
[0]
http://dhaka.ankur.org.bd/tmp/ankur/l10n/libreoffice.org/l10n_3.3/new-libo3.3_bn_UI_po.tar.bz2
[1]
http://dhaka.ankur.org.bd/tmp/ankur/l10n/libreoffice.org/l10n_3.3/new-libo3.3_bn_help_po.tar.bz2
I have also corrected the error at sc/source/ui/src.po:2602:
thanks
On Sun, Mar 6, 2011 at 2:07 PM, Andras Timar <timar74@gmail.com> wrote:
2011/3/6 israt jahan <isratjahan.ry@gmail.com>:
Sorry for providing wrong files. Now i am sending you latest files
([0],[1])
where the pot creation date is 2011-02-06. Please upload them at pootle.
[0]
http://dhaka.ankur.org.bd/tmp/ankur/l10n/libreoffice.org/l10n_3.3/libo3.3_bn_UI_po.tar.bz2
[1]
http://dhaka.ankur.org.bd/tmp/ankur/l10n/libreoffice.org/l10n_3.3/libo3.3_bn_help_po.tar.bz2
You forgot to merge your lo-build-bn.po, therefore you have many
untranslated string here that are translated there. It is not a big
issue now, but later on can cause confusion. It is better to merge it
now. See http://wiki.documentfoundation.org/Mergingl10n
There is fatal errors in the following file:
sc/source/ui/src.po:2602: end-of-line within string
Please correct this, too.
Thanks,
Andras
--
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/l10n/
*** All posts to this list are publicly archived for eternity ***
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.