Importing the Japanese Shift-JIS encoding to the kernel's locale
Hi, i have kinda found a method a couple years ago to import the Japanese Shift-JIS encoding from Fedora/CentOS/RHEL/OpenSuse to any other distribution and i keep forgetting to maintain the sideloading method when the kernel update broke it. A lot of Japanese content for Windows, who are able to run into Wine, required Japanese Shift-JIS locale used mostly back in the days. Sadly, only the distros above have it in their file and nobody noticed for years. This is also a major reason why Japanese speaker never used Linux too much due to Linux never supporting Shift-JIS by default and one of the reason MacOS and Windows got a monopole there (Yeah, MacOS support it from FreeBSD). My main issue's idk what's the license of the locale itself. The license of the package from the Fedora repo state the following for that package "LGPLv2+ and LGPLv2+ with exceptions and GPLv2+ and GPLv2+ with exceptions and BSD and Inner-Net and ISC and Public Domain and GFDL" which made me feel like it might had come from FreeBSD and might be BSD license... I am very unsure about it. Essentially, the reply from 2018 from this bugzilla mailing list was what i found to make it work. https://bugzilla.redhat.com/show_bug.cgi?id=136290 It would required to have a up to date fedora build and rip it from that location... Which's very inconveniant. Hence why i was hoping to have it supported by default by the kernel. It's kinda my first time to the kernel mailing list, hence why i am posting in the newbie section to not annoy anybody in the more official channel. IDK either how i can contribute the patch. I really hope this local can be included by default upstream so it get supported for the Japanese user to have their classic game supported in Wine so Linux could spare them from Windows 10's current issue. -Regard, HerbalNekoTea
On Sat, 24 Apr 2021 01:36:13 -0400, HerbalNekoTea said:
Hi, i have kinda found a method a couple years ago to import the Japanese Shift-JIS encoding from Fedora/CentOS/RHEL/OpenSuse to any other distribution and i keep forgetting to maintain the sideloading method when the kernel update broke it.
Essentially, the reply from 2018 from this bugzilla mailing list was what i found to make it work.�https://bugzilla.redhat.com/show_bug.cgi?id=136290
It would required to have a up to date fedora build and rip it from that location... Which's very inconveniant. Hence why i was hoping to have it supported by default by the kernel.
Locales are very much a userspace thing, the kernel doesn't care or know about it. If you're using the line-mode virtual consoles rather than Gnome terminal or xterm or other GUI terminal program, you'll need an appropriate font, but again, that's more userspace than kernel. If you read the last comment that you're pointing at in that bugzilla, it flat out tells you how to fix your issue *in userspace*. This is not a kernel problem.
Is there anyway to have something easily done about it upstream ? Would the license be an issue if there's any about it ? Where should i contact to try to see if they can include it upstream ? Thank you. Regards -HerbalNekoTea On Sat, Apr 24, 2021 at 1:51 AM Valdis Klētnieks <valdis.kletnieks@vt.edu> wrote:
On Sat, 24 Apr 2021 01:36:13 -0400, HerbalNekoTea said:
Hi, i have kinda found a method a couple years ago to import the Japanese Shift-JIS encoding from Fedora/CentOS/RHEL/OpenSuse to any other distribution and i keep forgetting to maintain the sideloading method when the kernel update broke it.
Essentially, the reply from 2018 from this bugzilla mailing list was what i found to make it work. https://bugzilla.redhat.com/show_bug.cgi?id=136290
It would required to have a up to date fedora build and rip it from that location... Which's very inconveniant. Hence why i was hoping to have it supported by default by the kernel.
Locales are very much a userspace thing, the kernel doesn't care or know about it. If you're using the line-mode virtual consoles rather than Gnome terminal or xterm or other GUI terminal program, you'll need an appropriate font, but again, that's more userspace than kernel.
If you read the last comment that you're pointing at in that bugzilla, it flat out tells you how to fix your issue *in userspace*.
This is not a kernel problem.
Hi all! On 24/04/2021 07:55, HerbalNekoTea wrote:
Is there anyway to have something easily done about it upstream ? Would the license be an issue if there's any about it ? Where should i contact to try to see if they can include it upstream ? Thank you. Regards
Since that is a userspace issue (as Vladis already wrote), talk to your distribution. And top-posting is evil.
On Sat, Apr 24, 2021 at 1:51 AM Valdis Klētnieks <valdis.kletnieks@vt.edu <mailto:valdis.kletnieks@vt.edu>> wrote: [...]> This is not a kernel problem. Seconded.
MfG, Bernd -- Bernd Petrovitsch Email : bernd@petrovitsch.priv.at There is NO CLOUD, just other people's computers. - FSFE LUGA : http://www.luga.at
participants (3)
-
Bernd Petrovitsch -
HerbalNekoTea -
Valdis Klētnieks