hoping next version of Puppy Linux may include default inputting framework like Ubuntu or distro.

[kclau2020]

Hello,
I have been using Puppy Linux from 2009 and always found that it is a solid, stable and work out of box distro. I really like it very much. During the years, I notice that Puppy Linux still without an inputting framework installed by default such as Ubuntu, Mint or other distro. User from Japan, Chinese or other Asia countries need to type their language is difficult to find solution until some volunteers to provide a pet for installing, thanks for icake! However, I would like to suggest puppy user should have a choice to select their own inputting method such as cangjie, quick, pinyan or etc. by default in next Puppy. I think this changes may help make puppy linux more popular and usable and is really useful for a PC layman like me. Thank you very much!

[thinkpadfreak]

Hello.

I am a Japanese, who make Japanese language packs and Japanized versions of puppies (ISO files).

I myself feel that I would be happier if I could use some input method out of the box. However ...

If we add some input method and a font to display our language, ISO will become larger in size by 20 ~ 30MB. The size of recent puppies is originally 300 ~ 400MB. European and American people do not need any input method. Thinking that puppy linux copies the main sfs (+ zdrv sfs, etc) to RAM, a larger size of ISO might be a handicap.

Isn't there a localization project in your language? Ubuntu provides a large variety of software packages to help localize its products. And if there are language packs in your language, it might be possible to make a localized ISO.

Above is only my personal opinion.

[rockedge]

Hello thinkpadfreak,

I wonder if @MochiMoppel has some information on Japanese language integration.

[kclau2020]

Thanks for reply!
I don't need to localise Puppy Linux to my native language. I would rather use any English OS without problems. But I most concern on the input method such as ibus, scim etc. My experience to install such input method is rather easy in Puppy Linux. But even you can install one of them, it always don't at all. That's the problem I concern.

[thinkpadfreak]

My experience to install such input method is rather easy in Puppy Linux. But even you can install one of them, it always don't work at all.

It seems to me that the reasons why input methods don't work are:
(1) Some dependencies are not satisfied. (You need to add some packages.)
(2) The configuration is not complete. (In order to start an input method, you need to add some lines to /root/.xinitrc, for example.)

I often refer to archwiki. Unlike other distributions, the settings for Puppy are often written in /root/.xinitrc.

[kclau2020]

Hi thinkpadfreak:
Thanks for your suggestion: "It seems to me that the reasons why input methods don't work are:
(1) Some dependencies are not satisfied. (You need to add some packages.):
(2) The configuration is not complete. (In order to start an input method, you need to add some lines to /root/.xinitrc, for example.)
I often refer to archwiki. Unlike other distributions, the settings for Puppy are often written in /root/.xinitrc."

@(1) I install all the scim required files from Petget package manager.

@(2) I edit the file of /root/.xinitrc in fossapup64 like this:
export XIM="SCIM"
export XIM_ARGS="-d"
export XIM_PROGRAM="SCIM"
export GTK_XIM_MODULES="SCIM"
export QT_XIM_MODULES="SCIM"
export LC_CTYPE="zh_CN.utf8"
if (grep "[1-2]" /usr/share/.fixmenus_indicator) then
fixmenus
fi
export XMODIFIERS=@im=SCIM
killall scim; scim &
It doesn't work.

Then I try to download icake's language pet to install in fossapup64, not work also.

I tried all this but is still no luck. That's why I suggest as the heading said.
In short, Puppy Linux is still the best one I love and use it in my daily work.

[thinkpadfreak]

@(2) I edit the file of /root/.xinitrc in fossapup64 like this:

Hello.

I use fcitx for fossapup64, because scim is not compatible with qt5 applications. Xim is not compatible with qt5, either.
But scim is still valid for gtk applications.

I added these to /root/.xinitrc:

Code: Select all

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

In case of scim, I would add these:

Code: Select all

 export XMODIFIERS='@im=SCIM'
 export GTK_IM_MODULE="scim"
 export QT_IM_MODULE="scim" # <- This line is invalid for the reason I wrote above.
 scim -d

I have made a Japanese language pack for fossapup64, which adds fcitx and the necessary settings. I have not tested it with other languages than Japanese, though.

Fossapup64 thread in the Puppy Linux Japanese Forum
http://www.sakurapup.browserloadofcooln ... 490#p27138

[kclau2020]

My problem had been solved as I follow the following link from puppy linux forum.
viewtopic.php?t=88&p=3828&i=1

After I installed this pet "fcitx64_4.2.9-zh-en-bionic-18.0.5.pet" and I can type chinese characters in fossapup64 and it runs without issues.
However, as the above link indicates that installing chinese inputting method such as scim, fcitx or ibus is quite time wasting and frustrated.
In short, many thanks to all of you with great appreciation!

[sc0ttman]

Maybe we should think about creating a generic `langpack-input-methods` package, which contains fcitx, scim, and maybe some other stuff.

If we can build a package that works on lots of different versions of Puppy, it could live in the common32 and common64 repos.

If we need to build a specific version of the package for each Puppy we create, then maybe Woof-CE should build this package, just like it does with the other "langpack" PET packages...

I've created an "issue" for this at the woof-CE Github repo: https://github.com/puppylinux-woof-CE/w ... ssues/1893

[mikeslr]

Hi all,

Feeling reckless today, I'll venture to rush in to a discussion about which I know nothing.
The thread currently immediately below this one is about taersh's modification of initrd.gz in order that Puppies can make use of more "alphabet" SFSes. "alphabet" SFSes when present automatically are copied into RAM on bootup.
[Current Puppies make use of zdrv.sfs (which contain drivers & sometimes firmware); fdrv.sfs (which contains firmware); and can make use of adrv.sfs and ydrv.sfs. Puppy Devs sometimes include an adrv.sfs in an ISO, or otherwise make it available. Such adrv.sfs contains applications the Dev believes some users may want, but other users may consider not essential for his/her needs.
Users can create their own adrv.sfs and ydrv.sfs. A component of nic007's nicOS-utility-Suite can convert a SaveFile or SaveFolder into either an adrv or a ydrv thereby enabling its user to operating from READ-ONLY file-systems.
An "alphabet".sfs can contain anything: an application, an application suite; a random assortment of applications THE user always installs].
Currently, there are only two 'user-definable' 'alphabet.sfses': adrv.sfs and ydrv.sfs. Taersh's modification would add 6 more.
While I think 'regular' sfses are generally superior --unloadable when not needed; easily replaceable by upgrades-- I think an alphabet SFS would be a convenient mechanism for distributing an input system. . It is a system you either need, or don't. If you don't need it, you can either not download it; or if part of an ISO remove it.
And, like any SFS, anyone can create it. From experience in converting a SaveFile to an adrv.sfs, I know that 'alphabet' SFSes can also handle the concerns expressed by thinkpadfreak: (1) include any dependency and "(2) The configuration is not complete. (In order to start an input method, you need to add some lines to /root/.xinitrc, for example.)". Such lines can be built-in.
Perhaps many Puppy variants can use the same build. From my experience using the same application in SFS format among Xenialpup64, Bionicpup64 and Fossapup64, a 'language-input' sfs may not have to be built for each Puppy; or could easily be rebuilt with a few newer libraries. Similarly, some applications built for debian/ubuntus puppies can be used with slacko-puppies if a few required dependencies, packaged as a pet, were installed.

[thinkpadfreak]

I think an alphabet SFS would be a convenient mechanism for distributing an input system.

Yes, indeed.
Shinobar took a similar approach. His lang_pack_ja-2.1.sfs is famous among puppy users in Japan.
It is compatible with tahr, xenial, slacko 6.3.2 and other puppies developed in about the same period.

However, lang_pack_ja-2.1.sfs has become less compatible with recent puppies because of changes in specifications. Since the sfs is for 32bit systems, it does not work with 64bit puppies.

In fact, there was a developer who thought of using adrv sfs in order to japanize puppies.
But an extra sfs such as lang_pack_ja-2.1.sfs sometimes has an avantage over adrv sfs, because the newer files included in the main sfs are prior to the older files included in the extra sfs.

When I make a language pack (.pet), I often refer to lang_pack_ja-2.1.sfs. If a single language pack is applicable to multiple puppies, it will be convenient.