Re: Encoding-named locale files in po_document

[Rafael Fontenelle]

Hi Gavin

On Sat, Oct 28, 2023 at 2:52 PM Gavin Smith <gavinsmith0123@gmail.com> wrote:
>
>
> Yes, I agree completely.  Thanks for looking into it and for explaining
> the benefits of removing these files.
>

I see those files were removed. Thanks for the fast reply and for solving this.

>
> The Norwegian translation file is dated 2001-01-01 (a suspicious-looking
> date, actually).
>
> It has a tiny number of working translations: for some variations of
> "Contents", "Index", and the twelve months of the year.
>
> I'm almost tempted to delete the file, but I will transfer it to
> state a UTF-8 encoding as you suggest.
>
> In some other translation files, Norwegian is nb rather than no (for
> "Bokmål"), but apparently no is still fine.  I found this page:
>
> https://icu.unicode.org/design/norwegian-locales-changes-in-v39
>
>   In CLDR 39 and ICU 69, the locale code “no” (Norwegian) is no
>   longer an alias (for CLDR and ICU purposes) and becomes the parent
>   locale for locales "nb" (Norwegian Bokmål) and "nn" (Norwegian
>   Nynorsk). The latter two locales retain their regional locales:
>   “nb_NO”, “nb_SJ”, “nn_NO”. The locale code “no” is no
>   longer deprecated.

The thing with the "no" locale is that Translation Project does *not*
have a translation team for the "no" locale, but it has teams for "nb"
(Norwegian Bokmål) and "nn" (Norwegian Nynorsk)[1]. So it seems to be
of no use for the translators from those teams.

I'm familiar with that locale to be confident enough to tell if you
can delete it or not, so I emailed the Norwegian translation from
Translation Project about this file. Hopefully they will come forward
to provide more expert opinion on how to solve this.

[1] https://translationproject.org/team/index.html

Regards,
Rafael