Context specific translations?

[Erik Huelsmann]

Hi,

Sorry, yes, wrong list!

Thanks for the pointers! Ik use them while mailing the right list.

Regards,

Erik

On Mar 5, 2018 22:22, "Daniel Herring" <dherring at tentpost.com> wrote:

Hi Erik,

Did this get sent to the wrong list?

Anyway, I would recommend mimicking Qt's approach to translation.  If
possible, re-use their file formats.  Then you can use their toolchain for
maintaining translations.

http://doc.qt.io/qt-5/linguist-overview.html

- Daniel



On Mon, 5 Mar 2018, Erik Huelsmann wrote:

Hi,
>
> In our translation catelog, we have the word "To". There are multiple uses
> for this word, which is marked for translation for all uses.
>
> One use is the case of a date range ("From ... To ...."). Another use is
> the case of an address ("To: <address on the next line(s)>".
>
> When translating these to Dutch, these use cases have very different
> translations (Date range: "Tot"; address: "Aan").
>
> It seems we need some context specific translations. However, our
> translation library (which isn't gettext), doesn't cater for them.
>
> Any ideas as to how to approach this problem?
>
> How will we know which domains we need to distinguish?
>
>
>
> --
> Bye,
> Erik.
>
> http://efficito.com -- Hosted accounting and ERP.
> Robust and Flexible. No vendor lock-in.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/clo-devel/attachments/20180305/b7cb8470/attachment.html>