`locale_install.sh` fails to install many locales #3

Closed
opened 1 year ago by xry111 · 3 comments
xry111 commented 1 year ago

Hi Gavin,

In locale_install.sh, it lists all installed locales with locale -a, then tries to match all .msg files in locales with them. If one .msg files matches a installed locale, it will be installed.

Unfortunately, on my LFS development system (with glibc-2.31) locale -a outputs the locale names like zh_CN.utf8, but the corresponding .msg file is zh_CN.UTF-8.msg. Then it just won't be installed.

I can create a symlink zh_CN.utf8.msg to zh_CN.UTF-8.msg to make locale_install.sh install it. But I'm not sure if it's the best way to solve this problem. (This is just an example, there are many other mismatches like en_US.ISO8859-1.msg versus en_US.iso88591, etc.)

Hi Gavin, In `locale_install.sh`, it lists all installed locales with `locale -a`, then tries to match all `.msg` files in `locales` with them. If one `.msg` files matches a installed locale, it will be installed. Unfortunately, on my LFS development system (with glibc-2.31) `locale -a` outputs the locale names like `zh_CN.utf8`, but the corresponding `.msg` file is `zh_CN.UTF-8.msg`. Then it just won't be installed. I can create a symlink `zh_CN.utf8.msg` to `zh_CN.UTF-8.msg` to make `locale_install.sh` install it. But I'm not sure if it's the best way to solve this problem. (This is just an example, there are many other mismatches like `en_US.ISO8859-1.msg` versus `en_US.iso88591`, etc.)
Owner

Symlinks are best, yes. I don't add them until someone asks because I don't know what is needed.

I have added a symlink to zh_CN.utf8. Do you need me to do a release? Also, are there other symlinks you want?

Symlinks are best, yes. I don't add them until someone asks because I don't know what is needed. I have added a symlink to zh_CN.utf8. Do you need me to do a release? Also, are there other symlinks you want?
Poster

It's not critical so I can wait for the next release.

I only use zh_CN.utf8 locale (besides the well-known locales C or en_US.utf8). But as recent glibc version's locale -a only outputs utf8 instead of UTF-8 now, each UTF-8 should be added an utf8 symlink (IMO). For example, es_ES.utf8.msg, ja_JP.utf8.msg, etc.

It's not critical so I can wait for the next release. I only use zh_CN.utf8 locale (besides the well-known locales `C` or `en_US.utf8`). But as recent glibc version's `locale -a` only outputs `utf8` instead of `UTF-8` now, each `UTF-8` should be added an `utf8` symlink (IMO). For example, `es_ES.utf8.msg`, `ja_JP.utf8.msg`, etc.
Owner

Okay, I have added all of the utf8 locales. It was big enough of a change that I decided to release 3.0.2.

I am closing this now; please reopen if there is more I need to do.

Okay, I have added all of the `utf8` locales. It was big enough of a change that I decided to release `3.0.2`. I am closing this now; please reopen if there is more I need to do.
gavin closed this issue 1 year ago
Sign in to join this conversation.
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.