MoManager scoops up more translations

I posted about MoManager being able to build a bigger langpack:

I also posted about non-English Hunspell dictionaries:

I have further refined this support in MoManager. The relevant files, that translators may download if they wish, are /usr/sbin/momanager and /usr/share/doc/langpack-template/, see Woof commit:

Posted on 16 Mar 2012, 8:25


Posted on 17 Mar 2012, 7:14 by fyujj
br-abnt2 keyboard
Not related to the topic but to i18n.
I'm using Wary 5.2.2 recently and, as usual, it sets up the Brazilian keyboard wrong. Since you're preparing the next version you may want to look at it.
I remember to have chosen the br-abnt2 keyboard in the first run but it set up xorg.conf with

"XkbModel" "pc102"
"XkbLayout" "br"

and the correct is

"XkbModel" "abnt2"
"XkbLayout" "br"

BTW, the traditional 'mouse/keyboard wizard > advanced xorg keyboard configuration' tool seems to be broken.

The best localization tool I ever used in Puppy was that one made by a community member from Japan. Pity for some reason the guys who made the Lupus didn't like it for some reason and so it never made to the main Puppy.

Posted on 17 Mar 2012, 7:50 by BarryK
Re Brazil keyboard
Could you please explain something for me. The keyboard layout utility in Puppy offers all of these:


Do you know the difference between each of these?
Which one do you use?
Which one do the majority of users in Brazil choose?

Posted on 17 Mar 2012, 7:55 by vicmz
RE: br-abnt2 keyboard
Racy is a clone of Wary (the only difference: Wary is for older computers and Racy is for newer computers), and I am using it right now (Racy with keyboard set to br-abnt2, it works fine. Don't worry, surely it's going to be fixed in the next version.

By the way, although I'm doing the Spanish translations first, I'm also doing some Portuguese translations on the go. It'd be great if you could help, or tell anyone who wishes to help or has .po files of existing translations. I only have the desktop, JWM, ROX-Filer and a couple of applications in Portuguese, but with a little help it can be more, and the best part, the resulting language pack will be included in Woof so that all new versions of Puppy can have a Portuguese langpack, and even a Portuguese Puppy can be made!

Posted on 17 Mar 2012, 8:29 by kAlug
RE: Brazil keyboard
I believe most keyboards here in Brazil are br-abnt2.

Posted on 18 Mar 2012, 2:42 by fyujj
Hi, the standard desktop keyboard in Brazil is br-abnt2.
The other ones you (Barry) mentioned are probably very old ones, from the time people used mostly us-international (maybe in the 90's).
I don't know about laptops as I have never had any.

Puppy used to have trouble with the br keyboard layout back when it didn't use xorg to set it as the map it used was wrong but I then helped to find the right map (some versions, though, reverted the error and some got it right).
But setting through xorg.conf always worked fine. This time it probably didn't because the xorg tool seems to be broken (when clicking to set the layout it pops up some text file and it also says it can't set the layout etc.).
Anyway, setting xorg.conf as I said works properly. The way it was (pc102,br) probably sets to an old key map which has the signs out-of-place, more like a US keymap.
vic, I did a lot of localisation to Portuguese for upstream stuff but stopped after having to almost fight just so translations wouldn't be destroyed (a 'big' distribution and their 'translation' teams..) etc. So I settled with en-GB ;-)
Good that you got ROX in pt-br, I translated it and could never make Puppy use it (probably some version mismatch or something else).

Posted on 18 Mar 2012, 2:57 by fyujj
BTW, there's a Pupplet from Brazil at
It used to be active at least not long ago. I suspect the guy who made it has translated some Puppy specific stuff.

Posted on 18 Mar 2012, 3:28 by BarryK
Testing br-abnt2
I am running Wary

I ran QuickSetup, chose br-abnt2 keyboard layout, and then looked in ;etc;X11;xorg.confă

Section "InputDevice"

Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "abnt2"
Option "XkbLayout" "br" #xkeymap0

The guy that you mention is shinobar, and I have his script ;usr;sbin;keymap-set, which modifies xorg.conf -- correctly.

Some characters are wrong in this post, that is because I am currently running with the br-abnt2 layout on my us layout keyboard.

Posted on 18 Mar 2012, 3:46 by BarryK
Re br-abnt2
Ok, I have changed back to us keyboard layout

I think that I see what the problem is. QuickSetup, via shinobar's keymap-set script, modifies xorg.conf correctly.

But, that is for Racy, where we boot straight to X and do not run the XorgWizard. So, xorg.conf already exists when QuickSetup is run.

Wary, however, runs the text-mode keyboard layout script (which is actually 'quicksetup') and then runs 'xorgwizard' to create 'xorg.conf'. So, 'xorg.conf' is created afterward.

A workaround for the problem is to run QuickSetup, choose br-abnt2 (actually, you might have to choose 'us' then 'br-abnt2' otherwise the script might think there is no change so do nothing). This will set 'xorg.conf' correctly.

Anyway, I will look at script 'xorgwizard', see if I can fix this.

Posted on 18 Mar 2012, 4:41 by BarryK
Brazil layout fix
Fixed, I think:

Posted on 18 Mar 2012, 6:52 by fyujj
Thank you, Barry.
Recapitulating: I've installed the nvidia driver so maybe that or me just looking at things ran xorgwizard and caused xorg to misconfigure. I noticed it when trying to access my email which has signs in its password.
When the next version of Wary is available then I give it a run to see if it's all ok in this front.

Posted on 18 Mar 2012, 12:06 by vicmz
Hunspell, menu entries
I got the latest updates for MoManager. I made a langpack using the 'find all' function (and without modifying the langpack template generated in root), and tested with no pupsave. ROX translations made it into the langpack, as I could see ROX-Filer in Spanish. I noticed that the hunspell folder had only the .dic files, the .aff files of the spellchecking dictionaries were missing, however the next time the 'almost done' dialog let me include anything that was missing or I simply wanted to include there such as Pburn, Pprocess and Pschedule locales and AbiWord strings (which are placed in /usr/share/abiword-2.8/strings), so that was no problem. Now as far as menu entries, some existing translations that are built-in in the live-CD appear instead of the new translations, this is important because it means I can't correct translation bugs. For example, the Bcrypt entry has an existing translation "Encriptado de Aplicaciones", but the proper term for encryption in Spanish is "cifrado" and Bcrypt doesn't encrypt "aplicaciones"(=applications), it encrypts files, so it should say "cifrado de archivos". Anyway, the most important is I could build a bigger langpack and include more translations without using any tools other than MoManager. Although there's still much to translate, I have plenty of Racy in Spanish!