(old)Puppy Linux Discussion Forum

Yes, rc.sysinit with t12s is working. But one phrase "next boot will be faster" from rc.update also should to be translated.
Gettexted rc.sysinit started to work for me after I added line:

L18L,
I like your little i18n test program!

I have put the two fonts that you have provided into the initrd in Woof.

After bootup:
One problem: running in the console, I start 'mp' and the border lines do not display properly.

...I wonder if there is a fix for this?

Barry,

console is urxvt or CONTROL-ALT-F2 ?

I have played with both of them,
did not see immediately the border line problem

file named äöü
see picture in X
äöü is blinking
same file named aou does not blink

in console (sorry no photograph available)
file name in title bar is displayed inproperly (equiv. to blinking?)

I can input äöü but it displaed not immediately correctly.

Maybe Barry means border lines in menu when you press Ctrl-A. Maybe you could try two console fonts from my unicode pet ter-u16n.psf.gz and cyr-sun16.psfu.gz. Do not install the pet. Just unpack it and get fonts. In both of them border lines are back and both of them work for Russian and English. Not sure about other languages.

After rodin.s´ hint I have repeated test in console

From my view there is nothing bad to report about border lines
No ! ctrl-a menu: left border is corrupt

Just cosmetic

But
- no öü
- no §
neither in mp nor in command line!

My conclusion:
The "new" consolefont is good just for displaying
but not for input.

Do Puppians really use console for things other than ASCII

I took pictures of menu of mp with normal and new consolefonts.

Yes, I meant when running mp from commandline, no X running.

rodin.s, thanks, I'll check out your alternative console fonts.

Well, I have implemented internationalization of the initrd in Woof, and built Racy 5.2.2.6 to test it:

http://bkhome.org/blog/?viewDetailed=02691

Note though, I used L18L's original technique of simple sed expressions. The implementation is extremely simple, you can see the 'init' script online:

http://bkhome.org/fossil/woof2.cgi/arti ... 8fd83a47d6

The /locale/de/init translation file in the initrd is not online as it gets generated by 3builddistro in Woof, from this file:

http://bkhome.org/fossil/woof2.cgi/arti ... 709a624016
...note, the comments in the [general] section are slightly wrong, the translation actually happens at every boot, and all other SSS domains are now using the same simple sed expressions technique.

A language-choice menu is not required in the initrd, as Woof now is able to edit the initrd.gz and insert file /PUPPYLANG -- except for case of booting off CD -- in that case, you are stuck with the English messages at early-bootup, but as soon as execution gets to rc.sysinit then translation will kick in.

Note also, keyboard layout gets set to match the language, unless set by pkeys boot param or file /PUPPYKEYMAP in initrd -- important in situation where have to enter a password for encrypted save-file.

whenever I have had issues with ncurses based interfaces, it was either:
a. the app needed ncursesw (unlikely if it works in X)
b. the incorrect terminfo was being exported and used ... I would guess that you need /usr/share/terminfo/l/linux and export TERM=linux in the initrd and init script respectively

technosaurus wrote:whenever I have had issues with ncurses based interfaces, it was either:
a. the app needed ncursesw (unlikely if it works in X)
b. the incorrect terminfo was being exported and used ... I would guess that you need /usr/share/terminfo/l/linux and export TERM=linux in the initrd and init script respectively

Before putting it into init one can try.
I have tried: and the left borderline of menu was displayed
This was in racy 5.2.2.6

äöü
- is correct on command line
- not in mp editing

Is there a ncursesw.pet ?
Not found in PPM

_____________________________

edited
same issue with some borderlines in xorgwizard

BarryK wrote:...Note though, I used L18L's original technique of simple sed expressions. The implementation is extremely simple, you can see the 'init' script online:

And slightly faster without g.
But password should become
s%"Password: "%"Paßwort: "%g
because translation has to happen more than once.
(And tell the translator to NOT remove g)

Compliment, you have also solved the problem of
done
using
"done"

L18L wrote:

BarryK wrote:...Note though, I used L18L's original technique of simple sed expressions. The implementation is extremely simple, you can see the 'init' script online:

And slightly faster without g.
But password should become
s%"Password: "%"Paßwort: "%g
because translation has to happen more than once.
(And tell the translator to NOT remove g)

Compliment, you have also solved the problem of
done
using
"done"

I think that the "g" only applies to the same line. That is, will translate multiple occurrences of "Password: " on the same line. If "Password: " is on different lines, then "g" is not required.

BarryK wrote:...
I think that the "g" only applies to the same line. That is, will translate multiple occurrences of "Password: " on the same line. If "Password: " is on different lines, then "g" is not required.

I was wrong
You have thought right
I have proved it