Hi,
I understand that it's easy to differentiate a translation with or without
any parameter but I think that we should do all we can to ease the work of
translators. Imagine a beginner translator that want to help us by creating
or enhancing a translation. If he had to respect some really boring rules
and think for each translation if he needs to protect the quotes or not, he
risks to be quickly bored and to simply abandon the translation. Moreover
I'm sure that we don't want to spend time in fixing bugs in translation and
a rule like this will probably be sooner or later be a source of bugs.
Sure. We shouldn't ask translators to work around what seems a bug in SC
(ok in MessageFormat but from a translator's point of view, it's still a
bug in SC). Moreover, it wouldn't be future-proof (imagine we drop
MessageFormat for something less weird).
And if the api doesn't allow us to filter the quotes, why don't simply parse
the String and automatically protect the quotes in it? If we do it
efficiently the translator would not have to care about protecting or not
the quotes in the String.
What do you all think ?
I vote for pain-free translating.
Sidenote: Did the guys at Sun ever think that one could use a single
quote in a class designed *for translations*? There is a bug marked as
fixed [0] related to this, but I fear the only thing that was fixed was
the documentation now explaining the bug.
[0] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4293229
Cheers,
···
On Sat, Nov 29, 2008 at 05:37:04PM -0500, Benoit Pradelle wrote:
--
Sébastien Mazy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net