i'm back here

[balloon]

When was the last time I came here to help with the Japanese translation?

When I woke up, I noticed that Salix 15.0 was released and that SalixLive 15.0 was also in development.
Salix's Transifex doesn't seem to change much, but I haven't translated Sli (the installer) yet. Will it go in time for SalixLive 15.0 now?
I'm taking action from GitHub.

[balloon]

Because I didn't put the URL in consideration of spam judgment.

https://github.com/djemos/sli/issues/2

My working Salix is already in this state.

[djemos]

Thanks.
ja_JP is OK.
Edit: ja_JP added on SLI.

[miredia]

Because I didn't put the URL in consideration of spam judgment.

I'm so glad the installer was changed out of that incredible mess, to one that looked like Slackware "install-DVD". I'm sorry if it sounded like an insult but that dialog box (of course in English) was just confusing, I couldn't make progress on it. @djemos it included my attempt to install Slackel. I would have picked that one if I couldn't have neither Slackware nor Salix.

[balloon]

By the time I posted this comment, sli's Japanese translation was provided. SalixLive 15.0 could adopt it.
(Sli for Slackel has also been translated)

Slackware and Salix maintain CLI installers because of their use in the CLI. For example a server.
However, desktop distro usage is also increasing, and Salix is a good fit for that, and SalixLive has a more approachable installer. It's a good entry point into the world of Slackware for inexperienced users.

Perhaps when SalixLive 15.0 is released, the ISO won't be updated for a while, so I was able to work in good timing.
(Slackel had the feel of being used before the move to 15.0. It helped too. Of course it will be useful later)

Support for Windows 10 ends in 2025. Someone should enter the Linux world instead. Salix will be the receptacle for that. Surely this forum should be lively at this time of year.
Thanks to the users who loved Linux, Slackware and Salix that they were still maintained.

[djemos]

@balloon
salixlive-xfce 15.0 rc4 with Japanese sli translation is on Sourceforge.
I suggest to use salix-xfce 15.0 for everyday use because updates are not often and it is based on slackware stable.
slackel is based on slackware current where updates done everyday. Japanese sli translation on slackel is also included but it will adopted when a new iso is released which i do not know when it will happen. Installing slackel once there is no need to install it again. Just update the system and have always the latest slackware current.

[balloon]

Thanks for building rc4! i will try it soon.

Japanese users need an input method to input Japanese.
Slackware 15.0 adopted Fcitx instead of SCIM. (for KDE Plasma and Qt5 support)
The tricky part is installing the input method when using current. It seems necessary to build SlackBuild for that.
Regarding the use of Slackel by Japanese users, the degree of difficulty will increase greatly in this regard.

If this is Salix(Live) 15.0+, you can easily install the input method with Gslapt or slapt-get:

Code: Select all

sudo slapt-get -u 
sudo slapt-get --dist-upgrade
sudo slapt-get -i fcitx-kkc fcitx-configtool noto-cjk-fonts-ttf

and create the following ~/.xprofile:

Code: Select all

export GTK_IM_MODULE=fcitx
export QT_IM_MODULE=fcitx
export XMODIFIERS=@im=fcitx

Also, I've already checked Slint 15.0. It has the input method already installed, so just create the above .xprofile.

[balloon]

I booted SalixLive 15.0-rc4 in Japanese:


That's the expected display!

[djemos]

fcitx removed on current.
Replaced by fcitx5, fcitx5-anthy, fcitx5-gtk, fcitx5-kkc, fcitx5-m17n, fcitx5-sayura, fcitx5-table-extra, fcitx5-table-other, fcitx5-unikey, fcitx5-qt

[balloon]

There is information from Japanese users that it is affected by the Unicode conversion of anthy.
So ~/.xprofile is: (for current)

Code: Select all

export GTK_IM_MODULE=fcitx5
export QT_IM_MODULE=fcitx5
export XMODIFIERS=@im=fcitx5

But the problem is package installation. Is there a way to inherit the current dependency? Otherwise, you'll have to install and explore the many packages you need, or bypass it and create a SlackBuild.
(For 15.0 it doesn't matter, see comments above)