[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-i18n-doc
Subject: Re: Purpose of LC_SCRIPTS
From: Adrian Chaves <adrian () chaves ! io>
Date: 2017-07-31 12:17:20
Message-ID: 79e16c9ce2efb33e0f87a1ac5ea47f6a () chaves ! io
[Download RAW message or body]
KDE's internationalization and localization framework supports scripting
in translations. I've never used it but I know it is there and I can
think of a few use cases (e.g. using or not an aposthrophe for a
variable based on whether or not the variable value matches or not a
regular expression). And having it as a separate variable is probably
useful to test translation scripts without breaking the translation that
you are currently using.
For more information, see:
*
https://techbase.kde.org/Localization/Concepts/Transcript#Translation_Scripting.3F
(how it is used by translators)
*
https://api.kde.org/frameworks/ki18n/html/prg_guide.html#handle_install
(installation of scripts)
On 2017-07-31 11:48, Luca Beltrame wrote:
> Hello,
>
> recently some translations have started using LC_SCRIPTS, and this caused some
> (transient; solved now) problems with openSUSE packaging. We wanted to make
> the language detection used to grab .mo files also aware of these, and asked
> people in the distribution about it.
>
> We got the following question in the downstream report:
>
> http://bugzilla.suse.com/show_bug.cgi?id=1048851#c1
>
> IOW, what is the purpose of LC_SCRIPTS? So I can tell the person involved.
[Attachment #3 (unknown)]
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body \
style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'> <p>KDE's internationalization \
and localization framework supports scripting in translations. I’ve never used it but I \
know it is there and I can think of a few use cases (e.g. using or not an aposthrophe for a \
variable based on whether or not the variable value matches or not a regular expression). And \
having it as a separate variable is probably useful to test translation scripts without \
breaking the translation that you are currently using.</p> <p>For more information, see:</p>
<ul>
<li><a href="https://techbase.kde.org/Localization/Concepts/Transcript#Translation_Scripting.3F" \
>https://techbase.kde.org/Localization/Concepts/Transcript#Translation_Scripting.3F</a> (how it \
> is used by translators)</li>
<li><a href="https://api.kde.org/frameworks/ki18n/html/prg_guide.html#handle_install">https://api.kde.org/frameworks/ki18n/html/prg_guide.html#handle_install</a> \
(installation of scripts)</li> </ul>
<p>On 2017-07-31 11:48, Luca Beltrame wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: \
0"><!-- html ignored --><!-- head ignored --><!-- meta ignored --> <div class="pre" \
style="margin: 0; padding: 0; font-family: monospace">Hello,<br /> <br /> recently some \
translations have started using LC_SCRIPTS, and this caused some <br /> (transient; solved now) \
problems with openSUSE packaging. We wanted to make <br /> the language detection used to grab \
.mo files also aware of these, and asked <br /> people in the distribution about it. <br /> <br \
/> We got the following question in the downstream report:<br /> <br /> <a \
href="http://bugzilla.suse.com/show_bug.cgi?id=1048851#c1">http://bugzilla.suse.com/show_bug.cgi?id=1048851#c1</a><br \
/> <br /> IOW, what is the purpose of LC_SCRIPTS? So I can tell the person involved.</div> \
</blockquote> <p><br /></p>
</body></html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic