Japanese locale modules for Porteus

Here is a place for your projects which are not officially supported by the Porteus Team. For example: your own kernel patched with extra features; desktops not included in the standard ISO like Gnome; base modules that are different than the standard ISO, etc...
neko
DEV Team
DEV Team
Posts: 2109
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Japanese locale modules for Porteus

Post#46 by neko » 27 Aug 2022, 08:26

Updated fcitx-mozc to fcitx5-mozc.

Please refer to the top article of this thread.

Note 1:
fcitx5-mozc package is from one of Archlinux.

Note 2:
There is a bug in fcitx5 package.
Bug fix

Code: Select all

% diff fcitx5-5.0.18-x86_64-2/usr/bin/org.fcitx5-autostart fcitx5-5.0.18-x86_64-2/usr/bin/fcitx5-autostart
5c5
< if [ "$XIM" = "fcitx" ]; then
---
> if [ "$XIM" = "fcitx5" ]; then
9c9
< if [ "$XIM_PROGRAM" = "fcitx" ]; then
---
> if [ "$XIM_PROGRAM" = "fcitx5" ]; then
13c13
< if [ "$GTK_IM_MODULE" = "fcitx" ]; then
---
> if [ "$GTK_IM_MODULE" = "fcitx5" ]; then
17c17
< if [ "$QT_IM_MODULE" = "fcitx" ]; then
---
> if [ "$QT_IM_MODULE" = "fcitx5" ]; then
Thanks.

rych
Warlord
Warlord
Posts: 622
Joined: 04 Jan 2014, 04:27
Distribution: Porteus 5.0 x64 OpenBox
Location: NZ
Contact:

Japanese locale modules for Porteus

Post#47 by rych » 27 Aug 2022, 09:58

neko, a few things:
1. I modified your module slightly: moved /home/guest folder to /root as I run root. Anyway, the main issues are the same:
2.

Code: Select all

root@porteus:~# fcitx5-configtool 
You're currently running Fcitx with GUI, but fcitx5-config-qt couldn't be found. Now it will open config directory.
3. Ctrl+Space doesn't work, it's because they really want to use fcitx in the ENV exports and not fcitx5. It wasn't a bug but a feature :)
4. GLib mismatch is still there so Gtk apps won't work anyway. beny's last message shows he could somehow get /usr/lib64/gtk-3.0/3.0.0/immodules/im-fcitx5.so to load. I suggest we wait for beny to share his method of fixing the GLib issue (I guess it's a bit ugly).

Here is the full output with your module (which doesn't work):

Code: Select all

root@porteus:~# fcitx5-diagnose 
# System Info:
1.  `uname -a`:

        Linux porteus.example.net 5.18.8-porteus #1 SMP PREEMPT_DYNAMIC Sat Jul 2 10:05:31 MSK 2022 x86_64 Intel(R) Core(TM) i5-9500 CPU @ 3.00GHz GenuineIntel GNU/Linux

2.  `lsb_release`:

    `lsb_release` not found.

3.  `/etc/lsb-release`:

    `/etc/lsb-release` not found.

4.  `/etc/os-release`:

        NAME=Porteus
        VERSION="5"
        ID=slackware
        VERSION_ID=5.0
        PRETTY_NAME="Porteus 5.0"
        ANSI_COLOR="0;34"
        CPE_NAME="cpe:/o:porteus:porteus_linux:5"
        HOME_URL="http://www.porteus.org/"
        SUPPORT_URL="http://forum.porteus.org/"
        BUG_REPORT_URL="http://forum.porteus.org/"

5.  Desktop Environment:

    Cannot determine desktop environment.

6.  XDG SESSION TYPE:

        XDG_SESSION_TYPE='x11'

7.  Bash Version:

        BASH_VERSION='5.1.16(1)-release'

# Environment:
1.  DISPLAY:

        DISPLAY=':0'


        WAYLAND_DISPLAY=''

2.  Keyboard Layout:

    1.  `setxkbmap`:

            xkb_keymap {
            	xkb_keycodes  { include "evdev+aliases(qwerty)"	};
            	xkb_types     { include "complete"	};
            	xkb_compat    { include "complete+ledscroll(group_lock)"	};
            	xkb_symbols   { include "pc+us+ru(phonetic_YAZHERTY):2+inet(evdev)+group(alt_shift_toggle)+terminate(ctrl_alt_bksp)"	};
            	xkb_geometry  { include "pc(pc105)"	};
            };

    2.  `xprop`:

            _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us,ru", ",phonetic_YAZHERTY", ",grp:alt_shift_toggle,grp_led:scroll,terminate:ctrl_alt_bksp"

3.  Locale:

    1.  All locales:

            C
            C.utf8
            POSIX
            en_US
            en_US.utf8

    2.  Current locale:

            LANG=en_US.UTF-8
            LC_CTYPE="en_US.UTF-8"
            LC_NUMERIC="en_US.UTF-8"
            LC_TIME="en_US.UTF-8"
            LC_COLLATE=C
            LC_MONETARY="en_US.UTF-8"
            LC_MESSAGES="en_US.UTF-8"
            LC_PAPER="en_US.UTF-8"
            LC_NAME="en_US.UTF-8"
            LC_ADDRESS="en_US.UTF-8"
            LC_TELEPHONE="en_US.UTF-8"
            LC_MEASUREMENT="en_US.UTF-8"
            LC_IDENTIFICATION="en_US.UTF-8"
            LC_ALL=

4.  Directories:

    1.  Home:

            /root

    2.  `${XDG_CONFIG_HOME}`:

        Environment variable `XDG_CONFIG_HOME` is not set.

        Current value of `XDG_CONFIG_HOME` is `~/.config` (`/root/.config`).

    3.  Fcitx5 Settings Directory:

        Current fcitx5 settings directory is `~/.config/fcitx5` (`/root/.config/fcitx5`).

5.  Current user:

    The script is run as root (0).

    1.  `sudo` Environment Variables:

        SUDO_COMMAND is not set.

        SUDO_USER is not set.

        SUDO_UID is not set.

        SUDO_GID is not set.

    2.  Running as root:

        **You are probably logging in as `root` or using `sudo` to run this script. This either means you have security problems or the result of this script may not be accurate. See [Why is it bad to run as root](https://www.google.com/search?q=Why+is+it+bad+to+run+as+root) or [sudo environment variables](https://www.google.com/search?q=sudo+environment+variables) for more information.**

# Fcitx State:
1.  executable:

    Found fcitx5 at `/usr/bin/fcitx5`.

2.  version:

    Fcitx version: `5.0.18`

3.  process:

    Found 1 fcitx5 process:

         1991 fcitx5

4.  `fcitx5-remote`:

    `fcitx5-remote` works properly.

5.  DBus interface:

    Using `dbus-send` to check dbus.

    Owner of DBus name `org.fcitx.Fcitx5` is `:1.27`.

    PID of DBus name `org.fcitx.Fcitx5` owner is `1991`.

    Debug information from dbus:

           Group [x11::0] has 1 InputContext(s)
          IC [4cd55ab46e8c49458233dd11a34eadf7] program: frontend:xim cap:4000000000 focus:0
        Input Context without group

# Fcitx Configure UI:
1.  Config Tool Wrapper:

    Found fcitx5-configtool at `/usr/bin/fcitx5-configtool`.

2.  Config GUI for qt:

    **Config GUI for qt not found.**

3.  Config GUI for kde:

    **`kcmshell5` not found.**

    **Cannot find a GUI config tool, please install one of `kcm-fcitx5`, or `fcitx5-config-qt`.**

# Frontends setup:
## Xim:
1.  `${XMODIFIERS}`:

    **Environment variable XMODIFIERS is "@im=fcitx5" instead of "@im=fcitx". Please check if you have exported it incorrectly in any of your init files.**

    **Please set environment variable XMODIFIERS to "@im=fcitx" using the tool your distribution provides or add `export XMODIFIERS=@im=fcitx` to your `~/.xprofile`. See [Input Method Related Environment Variables: XMODIFIERS](http://fcitx-im.org/wiki/Input_method_related_environment_variables#XMODIFIERS).**

    Xim Server Name from Environment variable is fcitx5.

2.  XIM_SERVERS on root window:

    Xim server name is the same with that set in the environment variable.

## Qt:
1.  qt4 - `${QT4_IM_MODULE}`:

    **Environment variable QT_IM_MODULE is "fcitx5" instead of "fcitx". Please check if you have exported it incorrectly in any of your init files.**
    **You may have trouble using fcitx in qt4 programs.**

    **Please set environment variable QT_IM_MODULE to "fcitx" using the tool your distribution provides or add `export QT_IM_MODULE=fcitx` to your `~/.xprofile`. See [Input Method Related Environment Variables: QT_IM_MODULE](http://fcitx-im.org/wiki/Input_method_related_environment_variables#QT_IM_MODULE).**

2.  qt5 - `${QT_IM_MODULE}`:

    **Environment variable QT_IM_MODULE is "fcitx5" instead of "fcitx". Please check if you have exported it incorrectly in any of your init files.**
    **You may have trouble using fcitx in qt5 programs.**

    **Please set environment variable QT_IM_MODULE to "fcitx" using the tool your distribution provides or add `export QT_IM_MODULE=fcitx` to your `~/.xprofile`. See [Input Method Related Environment Variables: QT_IM_MODULE](http://fcitx-im.org/wiki/Input_method_related_environment_variables#QT_IM_MODULE).**

3.  Qt IM module files:

    Found fcitx5 im module for qt5: `/usr/lib64/qt5/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so`.
    Found fcitx5 qt5 module: `/usr/lib64/fcitx5/qt5/libfcitx-quickphrase-editor5.so`.
    **Cannot find fcitx5 input method module for Qt4.**

## Gtk:
1.  gtk - `${GTK_IM_MODULE}`:

    **Environment variable GTK_IM_MODULE is "fcitx5" instead of "fcitx". Please check if you have exported it incorrectly in any of your init files.**
    **You may have trouble using fcitx in gtk programs.**

    **Please set environment variable GTK_IM_MODULE to "fcitx" using the tool your distribution provides or add `export GTK_IM_MODULE=fcitx` to your `~/.xprofile`. See [Input Method Related Environment Variables: GTK_IM_MODULE](http://fcitx-im.org/wiki/Input_method_related_environment_variables#GTK_IM_MODULE).**

2.  `gtk-query-immodules`:

    1.  gtk 2:

        **Cannot find `gtk-query-immodules` for gtk 2**

        **Cannot find fcitx5 im module for gtk 2.**

    2.  gtk 3:
Cannot load module /usr/lib64/gtk-3.0/3.0.0/immodules/im-fcitx5.so: GModule (/usr/lib64/gtk-3.0/3.0.0/immodules/im-fcitx5.so) initialization check failed: GLib version too old (micro mismatch)
/usr/lib64/gtk-3.0/3.0.0/immodules/im-fcitx5.so does not export GTK+ IM module API: GModule (/usr/lib64/gtk-3.0/3.0.0/immodules/im-fcitx5.so) initialization check failed: GLib version too old (micro mismatch)

        Found `gtk-query-immodules` for unknown gtk version at `/usr/bin/gtk-query-immodules-3.0`.

        **Failed to find fcitx5 in the output of `/usr/bin/gtk-query-immodules-3.0`**

        **Cannot find `gtk-query-immodules` for gtk 3**

        **Cannot find fcitx5 im module for gtk 3.**

3.  Gtk IM module cache:

    1.  gtk 2:

        Found immodules cache for gtk `2.24.33` at `/usr/lib64/gtk-2.0/2.10.0/immodules.cache`.
        Version Line:

            # Created by /usr/bin/gtk-query-immodules-2.0-64 from gtk+-2.24.33

        **Failed to find fcitx5 in immodule cache at `/usr/lib64/gtk-2.0/2.10.0/immodules.cache`**

        **Cannot find fcitx5 im module for gtk 2 in cache.**

    2.  gtk 3:

        Found immodules cache for gtk `3.24.33` at `/usr/lib64/gtk-3.0/3.0.0/immodules.cache`.
        Version Line:

            # Created by /usr/bin/gtk-query-immodules-3.0-64 from gtk+-3.24.33

        **Failed to find fcitx5 in immodule cache at `/usr/lib64/gtk-3.0/3.0.0/immodules.cache`**

        **Cannot find fcitx5 im module for gtk 3 in cache.**

    3.  gtk 4:

        **Cannot find immodules cache for gtk 4**

        **Cannot find fcitx5 im module for gtk 4 in cache.**

4.  Gtk IM module files:

    1.  gtk 2:

        All found Gtk 2 immodule files exist.

    2.  gtk 3:

        All found Gtk 3 immodule files exist.

    3.  gtk 4:

        All found Gtk 4 immodule files exist.

# Configuration:
## Fcitx Addons:
1.  Addon Config Dir:

    Found fcitx5 addon config directory: `/usr/share/fcitx5/addon`.

2.  Addon List:

    1.  Found 20 enabled addons:

            Classic User Interface 5.0.18
            Clipboard 5.0.18
            DBus 5.0.18
            DBus Frontend 5.0.18
            Emoji 5.0.18
            Fcitx4 Frontend 5.0.18
            IBus Frontend 5.0.18
            Input method selector 5.0.18
            Keyboard 5.0.18
            KDE Input Method Panel 5.0.18
            Mozc 
            Status Notifier 5.0.18
            Notification 5.0.18
            Quick Phrase 5.0.18
            Spell 5.0.18
            Unicode 5.0.18
            Wayland 5.0.18
            Wayland Input method frontend 5.0.18
            XCB 5.0.18
            X Input Method Frontend 5.0.18

    2.  Found 0 disabled addons:

3.  Addon Libraries:

    All libraries for all addons are found.

4.  User Interface:

    Found 2 enabled user interface addons:

        Classic User Interface
        KDE Input Method Panel

## Input Methods:
1.  `/root/.config/fcitx5/profile`:

    `/root/.config/fcitx5/profile` not found.

# Log:
1.  `date`:

        Sat Aug 27 21:36:45 NZST 2022

2.  `/root/.config/fcitx5/crash.log`:

    `/root/.config/fcitx5/crash.log` not found.


root@porteus:~# 

beny
Full of knowledge
Full of knowledge
Posts: 2086
Joined: 02 Jan 2011, 11:33
Location: italy

Japanese locale modules for Porteus

Post#48 by beny » 27 Aug 2022, 12:07

hi rich i have make a porteus 5 stock without packages not useful at fcitx5 i have to upgrade the xcb deps that have grow a bit and the other are:

/mnt/sdh1/porteus/modules/gexiv2-0.14.0-x86_64-3.xzm
/mnt/sdh1/porteus/modules/glib2-2.72.3-x86_64-2.xzm
/mnt/sdh1/porteus/modules/glib-1.2.10-x86_64-9.xzm
/mnt/sdh1/porteus/modules/gtk+2-2.24.33-x86_64-3.xzm
/mnt/sdh1/porteus/modules/gtk+3-3.24.34-x86_64-1.xzm
/mnt/sdh1/porteus/modules/kiten-21.12.1-x86_64-1.xzm
/mnt/sdh1/porteus/modules/libffi-3.4.2-x86_64-2.xzm
/mnt/sdh1/porteus/modules/qt5-5.15.3_20211130_014c375b-x86_64-
/mnt/sdh1/porteus/modules/babl-0.1.88-x86_64-1.xzm
/mnt/sdh1/porteus/modules/gegl-0.4.34-x86_64-2.xzm
with fcitx4-config-qt you can choose mozc and control-space give you the switch to en to hiragana,btw i am a poor guy that not know if this work as expected i hope that work if you or other do not trust this you can do a directory that you can use where you have to work with fcitx5-mozc and you can remove from modules when you need a clean system.
Last edited by beny on 27 Aug 2022, 12:17, edited 1 time in total.

beny
Full of knowledge
Full of knowledge
Posts: 2086
Joined: 02 Jan 2011, 11:33
Location: italy

Japanese locale modules for Porteus

Post#49 by beny » 27 Aug 2022, 12:17

this is the link with the xcb deps upgraded:
https://www.mediafire.com/folder/m0mg5hfssyd44/xcb%26co
ok wait for report,,,

neko
DEV Team
DEV Team
Posts: 2109
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Japanese locale modules for Porteus

Post#50 by neko » 27 Aug 2022, 12:19

@rych

This is the fcitx5-mozc patch for root user.

rootpatch.xzm (4 K)
deleted
md5sum: e10d04a99c8d19454aab7be6d6ee7497 rootpatch.xzm

Porteus 5.0, cheatcode "login=root" is not available.
How do you login root ?


Thanks.

rych
Warlord
Warlord
Posts: 622
Joined: 04 Jan 2014, 04:27
Distribution: Porteus 5.0 x64 OpenBox
Location: NZ
Contact:

Japanese locale modules for Porteus

Post#51 by rych » 27 Aug 2022, 12:53

beny wrote:
27 Aug 2022, 12:07
fcitx5-config-qt you can choose mozc and control-space give you the switch to en to hiragana
yes, that's what we want. Which modules should I install for that, could you give me a full list with download links?

beny
Full of knowledge
Full of knowledge
Posts: 2086
Joined: 02 Jan 2011, 11:33
Location: italy

Japanese locale modules for Porteus

Post#52 by beny » 27 Aug 2022, 15:03

hi this is the link for the whole fcitx5,you have downloaded only the xcb deps when i have removed,ok the other file are on the tread is easy to download and make the packages
https://www.mediafire.com/folder/9fm3rvwc51ivq/fcitx5

rych
Warlord
Warlord
Posts: 622
Joined: 04 Jan 2014, 04:27
Distribution: Porteus 5.0 x64 OpenBox
Location: NZ
Contact:

Japanese locale modules for Porteus

Post#53 by rych » 28 Aug 2022, 08:11

neko, thanks for the patch, although I had done it manually already, anyway it's the least of our problems: your fcitx5-mozc doesn't work for bigger reasons. I'll start assembling a bundle from beny's pieces and notes.

By the time I downloaded Porteus 5.0 OpenBox iso cheatcode "login=root" had already been fixed apparently as per Porteus-v5.0x86_64_bugs reports (Post by ncmprhnsbl #88515)

neko
DEV Team
DEV Team
Posts: 2109
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Japanese locale modules for Porteus

Post#54 by neko » 29 Aug 2022, 14:00

=== Porteus v5.0 Japanese version ===
Update to PorteusV5.0-MULT_ja-22.08.29

Please refer to the top article of this thread.


Kernel 5.19.5 with AUFS patch
initrd-22.08.05.xz
32bit/64bit = 001-core-22.07.24.xzm / 001-core-22.07.23.xzm
32bit/64bit = 002-xorg-22.07.24.xzm / 002-xorg-22.07.23.xzm
004-chromium-104.0.5112.101-i586-1alien.xzm / 004-chromium-104.0.5112.101-x86_64-1alien.xzm
08-fcitx5-mozc-22.08.27-i586.xzm / 08-fcitx5-mozc-22.08.27-x86_64.xzm

Note: fcitx5-mozc
If a login-user is the "root", fcitx5-mozc is not available.


Thanks.

neko
DEV Team
DEV Team
Posts: 2109
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Japanese locale modules for Porteus

Post#55 by neko » 30 Aug 2022, 13:55

=== Porteus v5.0 Japanese version ===
Update to PorteusV5.0-MULT_ja-22.09.05

Please refer to the top article of this thread.


Kernel 6.0-rc4 with AUFS patch
initrd-22.08.05.xz
32bit/64bit = 001-core-22.07.24.xzm / 001-core-22.07.23.xzm
32bit/64bit = 002-xorg-22.07.24.xzm / 002-xorg-22.07.23.xzm
32bit/64bit = 004-chromium-105.0.5195.52-i586-1alien.xzm / 004-chromium-105.0.5195.52-x86_64-1alien.xzm
32bit/64bit = 08-fcitx5-mozc-22.08.27-i586.xzm / 08-fcitx5-mozc-22.08.27-x86_64.xzm

Note: fcitx5-mozc
If a login-user is the "root", fcitx5-mozc is not available.


Thanks.

neko
DEV Team
DEV Team
Posts: 2109
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Japanese locale modules for Porteus

Post#56 by neko » 19 Sep 2022, 13:51

=== Porteus v5.0 Japanese version ===
Update to PorteusV5.0-MULT_ja-22.09.19

Please refer to the top article of this thread.

1. Kernel : 6.0-rc6 with AUFS patch

2. "cryptsetup" of "000-kernel.xzm@/sbin" is version 2.3.5 (NEW)

3. Include Tools (spm 22.09.18-2, mkKernel 22.09.19-1) same as APoteus


Tkanks.

neko
DEV Team
DEV Team
Posts: 2109
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Japanese locale modules for Porteus

Post#57 by neko » 12 Oct 2022, 14:49

=== Porteus v5.0 Japanese version ===
Update to PorteusV5.0-MULT_ja-22.10.12

Please refer to the top article of this thread.

1. Kernel : 6.0.1 with AUFS patch

2. chromium : 106.0.5249.91-1alien

3. Include Tools (spm 22.10.10-1, mkKernel 22.10.09-1) same as APoteus


Tkanks.

bour59
Samurai
Samurai
Posts: 181
Joined: 29 Dec 2010, 08:10
Distribution: porteus v5.0-xfce K5.19.7
Location: France

Japanese locale modules for Porteus

Post#58 by bour59 » 14 Oct 2022, 13:11

hello, in PorteusV5.0-MULT_ja-22.10.12-x86_64.iso (747 M), post#1
I can find a tool to "Create a live USB" which use <table.
but
by ncmprhnsbl » 28 Sep 2022, 12:54

bour59 wrote: ?
28 Sep 2022, 09:49
Can't display a file in Porteus5.0-xfce but ok in APorteus

this is because Porteus5.0 gtkdialog is built with/for gtk+3 (and APorteus is still using gtk+2 version)
"table" was deprecated in gkt+2 and then removed in gtk+3
but
you can use "tree" in the same way:
so the tool is unusable in Porteus v5.0 but is ok in APorteus due to the version of gtk
same problem with <combobox> deprecated
use instead <comboboxtext> or <comboboxentry>

neko
DEV Team
DEV Team
Posts: 2109
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Japanese locale modules for Porteus

Post#59 by neko » 16 Oct 2022, 07:03

@bour59
Thank you for pointing out the problem.

I also considered remodeling to apply 005-spm-22.10.10-noarch-1.xzm to Porteus.
However, I decided to work around this problem by activating 005-spm-22.10.10-noarch-1.xzm
when using only valid features of 005-spm-22.10.10-noarch-1.xzm.

In other words, 005-spm-22.10.10-noarch-1.xzm is accommodated in ISO/porteus/optional,
and load=xfce;005-spm (example for XFCE) is added to cheatcode only when using it.
And this rearrangement will be modified in the next update.

Note: "valid features of 005-spm-22.10.10-noarch-1.xzm" example
GUI menu System ---> "Get Addon Packages"
You can get the most recent version WEB browser.


Thanks.

neko
DEV Team
DEV Team
Posts: 2109
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Japanese locale modules for Porteus

Post#60 by neko » 10 Nov 2022, 09:08

=== Porteus v5.0 Japanese version ===
Update to PorteusV5.0-MULT_ja-22.11.10

Please refer to the top article of this thread.

1. Kernel : 6.1-rc4 with AUFS patch

2. chromium : 107.0.5304.87-1alien

3. Include Tools (spm <option>, mkKernel, hardinfo) same as APoteus


Tkanks.

Post Reply