Re: ldm language localization...

On Thu, Jan 29, 2009 at 03:34:52PM -0500, Warren Togami wrote:
> Scenario A
> ==========
> Previous implementation of localized language names in ldm's Language 
> menu worked, except it had the major drawback of needing 8MB iso-codes 
> in both the server and chroot.
> 
> Scenario B
> ==========
> Ryan52 tried an earlier recommendation of ldminfod transmitting only 
> locale codes (like before) and ldm having its own translations in the 
> chroot.  He found this infeasible however due because the multitude of 
> automatically generated .mo files necessary would have been ~3MB due to 
> binary overhead and shear numbers of individual files.
> 
> Scenario C
> ==========
> Ryan52 wrote an alternative idea of transmitting all localized language 
> strings over ldminfod.  This eliminated the need for iso-codes in the 
> chroot.  But we now realize some drawbacks:
> 
> * ldminfod is slower because it needs to read a large number of files.
> * It needs to transmit more (currently 18KB) over ldminfod upon each 
> connection.
> * The current implementation has a python traceback on the nb_NO.UTF-8 
> when redirected (netcat, pipe, etc.)
> 
> Scenario D
> ==========
> Vagrant, Ogra and Warren support another alternative that should again 
> be faster than Scenario C, and also simpler in code.
> 

/me agrees

> * ldminfod should transmit only raw locale codes like in the past.
> * ldm during build reads from iso-codes and compiles a flat text file 
> containing all known raw locale codes and corresponding translations 
> needed by ldm.  This text file should be ~16KB in size.
> * ldm during runtime asks ldminfod and gets a list of locale codes the 
> server desires to display in ldm's Language menu.  Those locale codes 
> are matched to the flat text file to display full localized names.
> 
> Advantages:
> * ldminfod is far simpler and faster.
> * ldm reads only a single small file.
> 
> This text file should live somewhere in /usr/share.
> 
> Anyone see any problem in Scenario D?
> 
> Warren Togami
> [email protected]
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _____________________________________________________________________
> Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
>       https://lists.sourceforge.net/lists/listinfo/ltsp-developer
> For additional LTSP help,   try #ltsp channel on irc.freenode.net

-- 
_________________________
Ryan Niebur
[email protected]

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword

_____________________________________________________________________
Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help,   try #ltsp channel on irc.freenode.net

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkmCSjMACgkQMihv+PacasWE/wCeNa6hlhb2Ur4pYgy9VVcxfDUS
BmYAn3k3sj80up0tmYzFGSDhGBca3BHN
=eaW9
-----END PGP SIGNATURE-----