Translation for time zone conversion runner
Natalie Clarius
natalie_clarius at yahoo.de
Fri Feb 10 01:24:01 GMT 2023
Forgot one more translation string:
"<time> <timezone> in <timezone>" is the user help that explains what query they can type to invoke the runner. Here you should simply translate the placeholder words as you would use them in the accompanying explanation as well as the "in" word, and keep the "<" ">" as they are. I see now that the comment I gave in the translation string did not make this clear. Eg the expected German translation of that string is: "<Zeit> <Zeitzone> nach <Zeitzone>".
I hope this clears things up.
Am Donnerstag, 9. Februar 2023 um 23:09:39 MEZ hat Albert Astals Cid <aacid at kde.org> Folgendes geschrieben:
El dijous, 9 de febrer de 2023, a les 18:40:34 (CET), Natalie Clarius va
escriure:
> Dear translators,
> I authored the recently added time zone conversion feature for the date-time
> runner. It was brought to my attention that the way the input is parsed
> poses some problems for translation into various languages. I actually
> intended to make the syntax not too natural-language-y, and we decided to
> go with a format similar to what we already have in the unit conversion
> runner. The discussion can be found here:
> https://invent.kde.org/plasma/kwin/-/merge_requests/2587 But it appears
> that I did not succeed in making it independent enough of peculiarities of
> English syntax after all.
>
> Could you point out which assumptions about the input format are especially
> problematic for translation, and how this could possibly be handled in a
> better way?
Are you expecting all the translators to understand C++ code?
Please explain how the input format works in words non-coders can understand
:)
Best Regards,
Albert
> Cheers,Natalie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-i18n-doc/attachments/20230210/aaf9436c/attachment.htm>
More information about the kde-i18n-doc
mailing list