That's interesting - I don't recall getting that message when I was compiling scim, and I don't know why. (I might look into it later, but I'm not a programmer, either.)

A common way of dealing with lib files that aren't where you want them, is to make a link instead of copying. It does the same job, and takes up a bit less room in the pup_save file. In fact, I think that in Puppy217 the X11R6 directories are linked to the X11R7 ones (or vice versa - I'm not in Puppy at the moment and can't check).

I think I followed Irihapeti and RR Koothady's instructions one by one. Here's what I did :
(btw I'm using Puppy-3.01 Seamonkey with devx_301.sfs)

- set my locale to fr_FR, and checked the file '/etc/profile' and I found the line 'LANG=fr_FR'.

- copied 'libXaw95.so.7' to '/usr/local/bin' and installed 'libotf.so.0' in '/usr/local/lib'.

- installed the packages m17nlib, m17ndb, and m17n-SCIM RR Koothady offered. There were no dependency errors.

- installed scim-1.4.7-i486.pet, scim-bridge-0.4.15-i486.pet and scim-tables-0.5.8-i486.pet that I succesfully compiled :
1) for scim-1.4.7-i486.pet I did './configure --prefix=/usr'.
2) for scim-bridge-0.4.15-i486.pet I did './configure --prefix=/usr --disable-qt3-immodule --disable-qt4immodule'
3) for scim-tables-0.5.8-i486.pet I did just './configure' (I also tried './configure --prefix=/usr and it compiles well, but still doesn't work.)

then 'make; make install' for all three packages.

afterwards, I replaced '/usr/local/lib/scim-1.0/1.4.0/SetupUI/table-imengine-setup.so' by the one RR Koothady offered again.

Then I edited the following two files as Irihapeti and RR Koothady instructed :

1. a) My experience (I mean past few days) with SCIM installation tells me setting the 'locale' to fr_FR or ta_IN (in my case) is not necessary in the first place.
b) Setting the 'locale' becomes mandatory if you wish to 'display' the User Interface in your own language - that is after you translate ~/.jwmrc and ~/Choices/ROX-Filer/PuppyPin and ?may be other files(I am just exploring this at present...)

2. a) Hence, for the present, the objective is to make a successful 'local language input' using SCIM and not translating the UI.
b) The first precondition for a successful input is to install a unicode font of your language in your system. This is installed at /usr/X11R6/lib/X11/fonts/ttf folder. This action makes the font available universally for all the applications.

3. I have tested SCIM successfully with many puplet versions of 3.01 now (Timxxine, Pupee, Standard 3.01). The steps are fairly clear:

at /etc/gtk-2/immodules
viii) Finally:
Just place the following script at ~/.xinitrc - after the PUPSTATE line:

Quote:

GTK_IM_MODULE=scim
export GTK_IM_MODULE

ix) reboot.
x) No need for pressing "ctrl + space" to invoke SCIM; because with the above scripts in place, SCIM gets invoked whenever a GTK application starts.
xi) When a GTK application starts - SCIM is invoked. or else you can invoke it by typing scim -d in the terminal. It gets launched successfully.
xi) Now install the language tables in the SCIM panel found in the X Tray. To do this: Right click scim keyboard icon found in the tray - SCIM Setup - IM Engine - Generic Table - Table Management - Install ... Install the tables from /usr/local/share/scim/tables/
x) Close. Open the GTK application. SCIM Keyboard popsup a tray from where you can choose the language and table of your choice.
xi) After this - just type in your language.

The Problems with my way:
- I have read in Debian Forums (?Min Hua) that SCIM-Bridge way is more versatile of the two. It is said that SCIM-Bridge is written in C and hence it is capable of handling more apps. For example, my installation is fine with Abiword, Geany, Leafpad, GIMP, Inkscape - BUT not in Open Office. I am not able to use SCIM with Oo.
- However, I have seen in "BOSS Linux" (an Indian Debian Derivative) SCIM compiled with just SCIM-Brige and the Tables, inputting in Oo very well. SCIM-m17n is said to be written in C++ and it is claimed to be the reason for such a constraint.

------------------

So, please follow my way first step by step. Boost your confidence first by practically inputting French or any of your desired language.

Then take Irihapeti's path. Make Oo succumb to Puppy.

Then share with me the SCIM-Bridge Dot Pet you have compiled (as I have failed in this) with me and tell me how I should proceed to tackle Oo.

The whole idea of using scim-bridge is so that you don't have to be tied to a particular localisation to use its language. That's the problem with the chinese-input pet. I've found that changing locale to something non-English changes the default fonts used for things such as the code boxes on this forum, and the result is sometimes almost unreadable.

I've attached a version of the scim-bridge dotpet file, from which I have removed the scripts (don't know why I didn't think of this before )
The purpose of the scripts is to make the necessary alterations to .xinitrc and gtk.immodules. I'm new to this sort of thing and still unsure if I really know what I'm doing.

As for my other question about using macrons for Māori, I found that the mouse/keyboard wizard lets me set up a second keyboard map and also a key combination so that I can switch easily between the two. If anyone wants further details, let me know - it's one of those things that's fairly simple, but not immediately obvious.

Quote:

Kī mai ki ahau: he aha te mea nui o tēnei ao? Māku e kī atu: he tangata, he tangata, he tangata.
(=If you were to ask me, what is the greatest thing in the world, I should reply, it is people, people, people.)

I've seen references elsewhere to a problem with using dead key combinations with scim, but that's something I've not had to use (yet).

- This showed the following message: "/usr/bin/scim-bridge has these missing lib files: libscim-1.0.so.8"
- However, I could find that file residing in: /usr/local/lib
- Hence I thought, they should be linked: I did the following in the terminal: ln /usr/bin/scim-bridge /usr/local/lib/libscim-1.0.so.8 [I do not know how to symlink and was anxious to rush forward for the time being and hence without reading tried this... is it ok? Do you symlink this way between 2 files?]

6) Finally:
Just place the following script at ~/.xinitrc - after the PUPSTATE line:

Quote:

GTK_IM_MODULE=scim-bridge
export GTK_IM_MODULE

7) Reboot

a) SCIM "DOES NOT" get invoked when a GTK app is started as it happens in the m17n install method.
b) However, it can be launched from the Terminal by scim -d
c) This is of no use because even after launching, you can not invoke it "within the" applications.

RRK:
I run Puppy 2.17, as I think I've mentioned, and the file system layout may well be different from 3.01. It might be possible to rearrange the files inside the .pet package, or to add a symlink, by following instructions here:
http://www.puppylinux.com/development/createpet.htm
and then repackage the .pet. As I don't have a copy of 3.01, I can't test/do it myself.

As for symlinking. I just tend to use the GUI option: right click on file->link->absolute link. I guess I'm a bit lazy.

Scim-bridge definitely works with OpenOffice in Ubuntu. I don't have OO for Puppy yet, but I hope to get it shortly when my son downloads it over a much faster connection than I have. Then I can do some more testing.

At least, we have different ways of getting to the end result, which gives users options to try.

First, install the SCIM package compiled with './configure' and not './configure --prefix=/usr'
(you already know that you have to link some files in '/usr/X11R7' and '/usr/lib' to do this.)

Then, to comiple scim-bridge, run a rxvt window, and execute the following lines when you are in its folder :
1) # export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH
2) # export LD_LIBRARY_PATH="/usr/local/lib:$LD_LIBRARY_PATH (not sure if this is needed)
3) # ./configure --disable-qt3-immodule --disable-qt4immodule (don't add --prefix=/usr.)

This build of scim-bridge doesn't give any dependency errors when I install it.

And you install scim-tables finally.

I don't have Open Office, so can't check it for now. assuming that my pet files are built correctly, they could work with Puppy 3.01... or not.

If you would let us know what version of Puppy you are running, I can then tell you if the files I have would be useful to you. It appears that what works on Puppy 3.01 won't work on Puppy 2.17 and vice versa.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum