[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [virt-tools-list] [libosinfo v3] install-scripts: Translate lang format when needed

On Fri, Nov 16, 2012 at 4:14 PM, Christophe Fergeau <cfergeau redhat com> wrote:
> On Thu, Nov 15, 2012 at 10:22:30PM +0200, Zeeshan Ali (Khattak) wrote:
>> On Thu, Nov 15, 2012 at 7:18 PM, Fabiano FidĂȘncio <fabiano fidencio org> wrote:
>> > Add this translation in the windows template file because the script
>> > must have the language set using non-linux standard format.
>> > Windows will use, for instance, en-US instead of en_US or en_US.utf8.
>> This log and the doc comment below could be improved:
>> * There is no 'unix standard' or 'non-linux standard'.
>> * You want to point to what you are calling the standard:
>> https://www.ietf.org/rfc/rfc4646.txt
>> * The above log still makes it sound like windows is the one thats not
>> following the standard. You want to point out that although Linux is
>> not following the standard, why we are expected the string in Linux
>> format.
>> * We should probably specify more explitictly that '.utf8' part is
>> accepted but optional.
> Fwiw, Linux locale names (POSIX?) are roughly described here
> https://www.gnu.org/savannah-checkouts/gnu/gettext/manual/html_node/Locale-Names.html
> At least the language code and country code are the same as in rfc4646.

While I knew they are the same, now there is a document to prove that
they are. Thanks for digging this out. We should refer to this in the
docs/log as well.


Zeeshan Ali (Khattak)
FSF member#5124

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]