2011/2/16 Jean-Charles Malahieude <[email protected]>: > Le 16/02/2011 13:19, Francisco Vila disait : >> >> 2011/2/16 Francisco Vila<[email protected]>: >> BTW does >> >> LANG=whatever date -u >> >> work for you? for whatever = fr, de etc? >> > > [jcharles@localhost ~]$ LANG=de_DE.utf8 date -u > Mi 16. Feb 18:52:37 UTC 2011 > [jcharles@localhost ~]$ LANG=de date -u > Wed Feb 16 18:53:21 UTC 2011 > [jcharles@localhost ~]$ LANG=de_DE.utf8 date -u > Mi 16. Feb 18:53:24 UTC 2011 > [jcharles@localhost ~]$ LANG=es_ES.utf8 date -u > mié feb 16 18:53:39 UTC 2011 > [jcharles@localhost ~]$ date -u > mer. févr. 16 18:54:02 UTC 2011 > [jcharles@localhost ~]$ LANG=fr date -u > Wed Feb 16 18:54:14 UTC 2011 > [jcharles@localhost ~]$ LANG=fr_FR.utf8 date -u > mer. févr. 16 18:54:25 UTC 2011 > [jcharles@localhost ~]$ > > > Found after having > env | grep LANG
Thank you. Therefore, the code that pretends to build a localized date string at the translation status page, is wrong (or useless), and it looks a bit more complicated to infer the value of LANG from the lang code we use in the build. I could 'manually' add the code and values but not sure if it worths the effort. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
