nsis-devel

[NSIS-devel] 2nd argument to LANGFILE macro

[Wizou <sou...@wi...>]

There are discrepancies among the language files regarding the meaning 
of the 2nd argument to the LANGFILE macro.
It seems that sometimes it is the name of the language in english, 
sometimes it's the localized name.

If I'm right, the idea behind the 2nd argument is that it should be a 
name that can be displayed correctly on every system (for ANSI installers)
Which means the 2nd argument can only be a localized version if it 
contains plain ASCII (0..127) characters, right ?
For example, "Français" was sadly changed to "French" because of that. 
(see also bug tracker ID 2979786)
Then, why is "Español" not changed to "Spanish" ?

In fact, I think we should try to keep them localized at maximum rather 
than English, using "close" characters from the ASCII range if possible 
(and if the language purists allow it)
For example, we could have "Francais" and "Espanol"
(as a french guy, I wouldn't be offended by the missing cedil, and I 
would appreciate to see the name of the language localized)


On a related note, I will add a 3rd argument to the macro which is the 
exact localized version of the language, and will use it only instead of 
2nd argument when building Unicode installers.

Re: [NSIS-devel] 2nd argument to LANGFILE macro

[Amir S. <ki...@gm...>]

Sounds good to me.

On Jul 8, 2010 6:49 PM, "Wizou" <sou...@wi...> wrote:
> There are discrepancies among the language files regarding the meaning
> of the 2nd argument to the LANGFILE macro.
> It seems that sometimes it is the name of the language in english,
> sometimes it's the localized name.
>
> If I'm right, the idea behind the 2nd argument is that it should be a
> name that can be displayed correctly on every system (for ANSI installers)
> Which means the 2nd argument can only be a localized version if it
> contains plain ASCII (0..127) characters, right ?
> For example, "Français" was sadly changed to "French" because of that.
> (see also bug tracker ID 2979786)
> Then, why is "Español" not changed to "Spanish" ?
>
> In fact, I think we should try to keep them localized at maximum rather
> than English, using "close" characters from the ASCII range if possible
> (and if the language purists allow it)
> For example, we could have "Francais" and "Espanol"
> (as a french guy, I wouldn't be offended by the missing cedil, and I
> would appreciate to see the name of the language localized)
>
>
> On a related note, I will add a 3rd argument to the macro which is the
> exact localized version of the language, and will use it only instead of
> 2nd argument when building Unicode installers.
>
>
>
------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Nsis-devel mailing list
> Nsi...@li...
> https://lists.sourceforge.net/lists/listinfo/nsis-devel

Re: [NSIS-devel] 2nd argument to LANGFILE macro

[Wizou <sou...@wi...>]

mmmh on second thought, we can be even more clever than that

if MUI_LANGDLL_ALLLANGUAGES is not specified, we are sure that only 
languages using the same codepage will be displayed, in this case we can 
use the full localized name instead of the ASCII name.


Amir Szekely a écrit :
>
> Sounds good to me.
>
> On Jul 8, 2010 6:49 PM, "Wizou" <sou...@wi... 
> <mailto:sou...@wi...>> wrote:
> > There are discrepancies among the language files regarding the meaning
> > of the 2nd argument to the LANGFILE macro.
> > It seems that sometimes it is the name of the language in english,
> > sometimes it's the localized name.
> >
> > If I'm right, the idea behind the 2nd argument is that it should be a
> > name that can be displayed correctly on every system (for ANSI 
> installers)
> > Which means the 2nd argument can only be a localized version if it
> > contains plain ASCII (0..127) characters, right ?
> > For example, "Français" was sadly changed to "French" because of that.
> > (see also bug tracker ID 2979786)
> > Then, why is "Español" not changed to "Spanish" ?
> >
> > In fact, I think we should try to keep them localized at maximum rather
> > than English, using "close" characters from the ASCII range if possible
> > (and if the language purists allow it)
> > For example, we could have "Francais" and "Espanol"
> > (as a french guy, I wouldn't be offended by the missing cedil, and I
> > would appreciate to see the name of the language localized)
> >
> >
> > On a related note, I will add a 3rd argument to the macro which is the
> > exact localized version of the language, and will use it only 
> instead of
> > 2nd argument when building Unicode installers.
> >
> >
> > 
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Sprint
> > What will you do first with EVO, the first 4G phone?
> > Visit sprint.com/first <http://sprint.com/first> -- 
> http://p.sf.net/sfu/sprint-com-first
> > _______________________________________________
> > Nsis-devel mailing list
> > Nsi...@li... 
> <mailto:Nsi...@li...>
> > https://lists.sourceforge.net/lists/listinfo/nsis-devel
>