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


Hi,
one thing which I miss in the current system is the possibility to
translate plurals correctly. gettext supports that - maybe that it would
be necessary to change something in code, but I think its is worth that.
Pls, think about this
best
Milos

On 2017-06-05 13:44, Sophie wrote:
Hi all,

Le 04/06/2017 à 22:38, Cor Nouws a écrit :
m.balabanov@gmail.com wrote on 04-06-17 21:23:
Yes, Bulgarian is also one of those inflected languages that require different translations to 
the same English phrase depending on the context. If we lose msgctxt, we must have another way 
to separate different instances of the same English
If I read Caoláns post well, it would not be a problem to preserve
msgtxt in the new situation.
Thanks to all for your feedback. We are well aware of the need of
context, as Cor said, msgtxt could be preserved. Also before going live
with it, there will be several tests run to make sure the situation is
ok for us and doesn't imply more work on our side.

Cheers
Sophie


-- 
email & jabber: sramek.milos@gmail.com


-- 
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

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.