[gui-dev] Language names in message bundles

Discussion:

Philippe Verdy

2005-02-13 17:40:56 UTC

I don't know the difference between these two resources defined in
messagesbundles for language names:

(example in the French resource file)

LOCALE_ENGLISH_LANGUAGE_NAME=French
LOCALE_NSIS_NAME=French

Shouldn't it be LOCALE_NSIS_NAME=Français
like for LOCALE_LANGUAGE_NAME=Français

Or is there effectively the need to use a recognized language name only
in English and in a specific form for the NSIS installer, which may
sometimes be different from the detailed English name we use on our web
site? Or is that because NSIS will automatically locate a resource
named "LOCALE_NSIS_NAME"? Or because NSIS limits the length of the
language name?

In summary, why the new LOCALE_NSIS_NAME resource had to be defined?

Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails !
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/

Sam Berlin

2005-02-13 17:52:32 UTC

Permalink

Take a look at the Traditional Chinese bundle or the Portuguese (Brasilian)
bundle to see an example of why they're different ( at
http://www.limewire.org/fisheye/viewrep/~raw,r=MAIN/limecvs/lib/messagebundl
es/MessagesBundle_zh_TW.UTF-8.txt &
http://www.limewire.org/fisheye/viewrep/~raw,r=MAIN/limecvs/lib/messagebundl
es/MessagesBundle_pt_BR.properties ). In order to build the Windows (NSIS)
installer with a list of viable languages, we need the languages in the
codes that NSIS understands. For Traditional Chinese, this name is
'TradChinese', but on our website we want to show it was 'Chinese
(Traditional)'. For the most part, these names will be the same -- but they
won't always be.

If you look also at this changeset ( at
http://limewire.org/fisheye/changelog/limecvs/lib/messagebundles/com/limegro
up/gnutella/i18n?cs=MAIN:sberlin:20050110230546 ), it adds support to the
messagebundle's CountPercent class so that using the 'nsis' name will print
out the names of release-quality languages in codes that NSIS understands,
so we can provide a list while building that installer.

Thanks,
Sam

-----Original Message-----
Sent: Sunday, February 13, 2005 12:41 PM
Subject: [gui-dev] Language names in message bundles
I don't know the difference between these two resources defined in
(example in the French resource file)
LOCALE_ENGLISH_LANGUAGE_NAME=French
LOCALE_NSIS_NAME=French
Shouldn't it be LOCALE_NSIS_NAME=Français
like for LOCALE_LANGUAGE_NAME=Français
Or is there effectively the need to use a recognized language name only
in English and in a specific form for the NSIS installer, which may
sometimes be different from the detailed English name we use on our web
site? Or is that because NSIS will automatically locate a resource
named "LOCALE_NSIS_NAME"? Or because NSIS limits the length of the
language name?
In summary, why the new LOCALE_NSIS_NAME resource had to be defined?
Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails !
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/
_______________________________________________
gui-dev mailing list
http://www.limewire.org/mailman/listinfo/gui-dev

Greg Bildson

2005-02-14 18:28:00 UTC

Permalink

Some of these emails may benefit by using this or an equivalent:
http://tinyurl.com/

Thanks
-greg

-----Original Message-----
Sent: Sunday, February 13, 2005 12:53 PM
Subject: RE: [gui-dev] Language names in message bundles
Take a look at the Traditional Chinese bundle or the Portuguese (Brasilian)
bundle to see an example of why they're different ( at
http://www.limewire.org/fisheye/viewrep/~raw,r=MAIN/limecvs/lib/me
ssagebundl
es/MessagesBundle_zh_TW.UTF-8.txt &
http://www.limewire.org/fisheye/viewrep/~raw,r=MAIN/limecvs/lib/me
ssagebundl
es/MessagesBundle_pt_BR.properties ). In order to build the
Windows (NSIS)
installer with a list of viable languages, we need the languages in the
codes that NSIS understands. For Traditional Chinese, this name is
'TradChinese', but on our website we want to show it was 'Chinese
(Traditional)'. For the most part, these names will be the same -- but they
won't always be.
If you look also at this changeset ( at
http://limewire.org/fisheye/changelog/limecvs/lib/messagebundles/c
om/limegro
up/gnutella/i18n?cs=MAIN:sberlin:20050110230546 ), it adds support to the
messagebundle's CountPercent class so that using the 'nsis' name will print
out the names of release-quality languages in codes that NSIS understands,
so we can provide a list while building that installer.
Thanks,
Sam

_______________________________________________
gui-dev mailing list
http://www.limewire.org/mailman/listinfo/gui-dev

Sam Berlin

2005-02-14 18:23:49 UTC

Permalink

But then we wouldn't get Google points. :)

Thanks,
Sam

Post by Greg Bildson
http://tinyurl.com/
Thanks
-greg

-----Original Message-----
Sent: Sunday, February 13, 2005 12:53 PM
Subject: RE: [gui-dev] Language names in message bundles
Take a look at the Traditional Chinese bundle or the Portuguese (Brasilian)
bundle to see an example of why they're different ( at
http://www.limewire.org/fisheye/viewrep/~raw,r=MAIN/limecvs/lib/me
ssagebundl
es/MessagesBundle_zh_TW.UTF-8.txt &
http://www.limewire.org/fisheye/viewrep/~raw,r=MAIN/limecvs/lib/me
ssagebundl
es/MessagesBundle_pt_BR.properties ). In order to build the
Windows (NSIS)
installer with a list of viable languages, we need the languages in the
codes that NSIS understands. For Traditional Chinese, this name is
'TradChinese', but on our website we want to show it was 'Chinese
(Traditional)'. For the most part, these names will be the same -- but they
won't always be.
If you look also at this changeset ( at
http://limewire.org/fisheye/changelog/limecvs/lib/messagebundles/c
om/limegro
up/gnutella/i18n?cs=MAIN:sberlin:20050110230546 ), it adds support to the
messagebundle's CountPercent class so that using the 'nsis' name will print
out the names of release-quality languages in codes that NSIS
understands,
so we can provide a list while building that installer.
Thanks,
Sam

-----Original Message-----
Sent: Sunday, February 13, 2005 12:41 PM
Subject: [gui-dev] Language names in message bundles
I don't know the difference between these two resources defined in
(example in the French resource file)
LOCALE_ENGLISH_LANGUAGE_NAME=French
LOCALE_NSIS_NAME=French
Shouldn't it be LOCALE_NSIS_NAME=Français
like for LOCALE_LANGUAGE_NAME=Français
Or is there effectively the need to use a recognized language name only
in English and in a specific form for the NSIS installer, which may
sometimes be different from the detailed English name we use on our web
site? Or is that because NSIS will automatically locate a resource
named "LOCALE_NSIS_NAME"? Or because NSIS limits the length of the
language name?
In summary, why the new LOCALE_NSIS_NAME resource had to be defined?
Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour
vos
mails !
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/
_______________________________________________
gui-dev mailing list
http://www.limewire.org/mailman/listinfo/gui-dev

_______________________________________________
gui-dev mailing list
http://www.limewire.org/mailman/listinfo/gui-dev

Greg Bildson

2005-02-14 18:36:22 UTC

Permalink

Okay, lets start our own on org. :-)

Thanks
-greg

-----Original Message-----
Sent: Monday, February 14, 2005 1:24 PM
Subject: Re: [gui-dev] Language names in message bundles
But then we wouldn't get Google points. :)
Thanks,
Sam

Post by Greg Bildson
http://tinyurl.com/
Thanks
-greg

-----Original Message-----
Sent: Sunday, February 13, 2005 12:53 PM
Subject: RE: [gui-dev] Language names in message bundles
Take a look at the Traditional Chinese bundle or the Portuguese (Brasilian)
bundle to see an example of why they're different ( at
http://www.limewire.org/fisheye/viewrep/~raw,r=MAIN/limecvs/lib/me
ssagebundl
es/MessagesBundle_zh_TW.UTF-8.txt &
http://www.limewire.org/fisheye/viewrep/~raw,r=MAIN/limecvs/lib/me
ssagebundl
es/MessagesBundle_pt_BR.properties ). In order to build the
Windows (NSIS)
installer with a list of viable languages, we need the languages in the
codes that NSIS understands. For Traditional Chinese, this name is
'TradChinese', but on our website we want to show it was 'Chinese
(Traditional)'. For the most part, these names will be the same -- but they
won't always be.
If you look also at this changeset ( at
http://limewire.org/fisheye/changelog/limecvs/lib/messagebundles/c
om/limegro
up/gnutella/i18n?cs=MAIN:sberlin:20050110230546 ), it adds support to the
messagebundle's CountPercent class so that using the 'nsis' name will print
out the names of release-quality languages in codes that NSIS
understands,
so we can provide a list while building that installer.
Thanks,
Sam

-----Original Message-----
Sent: Sunday, February 13, 2005 12:41 PM
Subject: [gui-dev] Language names in message bundles
I don't know the difference between these two resources defined in
(example in the French resource file)
LOCALE_ENGLISH_LANGUAGE_NAME=French
LOCALE_NSIS_NAME=French
Shouldn't it be LOCALE_NSIS_NAME=Français
like for LOCALE_LANGUAGE_NAME=Français
Or is there effectively the need to use a recognized language name only
in English and in a specific form for the NSIS installer, which may
sometimes be different from the detailed English name we use on our web
site? Or is that because NSIS will automatically locate a resource
named "LOCALE_NSIS_NAME"? Or because NSIS limits the length of the
language name?
In summary, why the new LOCALE_NSIS_NAME resource had to be defined?
Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour
vos
mails !
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/
_______________________________________________
gui-dev mailing list
http://www.limewire.org/mailman/listinfo/gui-dev

_______________________________________________
gui-dev mailing list
http://www.limewire.org/mailman/listinfo/gui-dev