Quickset Wary-5.1.1-01q the Final Release

[L18L]

Wary-500j05 changed the locale to de_DE.
Just on my system, will upload later.

small change in welcome1stboot
edited: now correctly showing english if no localized picture

Code: Select all

# window_position=\"${WINPOS}\"
menu2="${TEXTDOMAINDIR}/`echo $LANG | cut -d '_' -f1`/pixmaps/menu2.png"
[ ! -f "$menu2" ] && menu2="`dirname $0`/menu2.png"
export WELCOME_DLG="
<window decorated=\"false\">
 <vbox>

and about 33 lines down

Code: Select all

  <hbox>
   <pixmap><input file>${menu2}</input></pixmap>
   <vbox>

enables localized picture (in new folder /usr/share/locale/language/pixmaps)

[don570]

When I tested version 4 wary-500j04.iso
I noticed a strange bug. mtPaint wasn't able to
load SVG format files.

For example try to open a SVG file located in
/root/puppy-reference/vector-images/

mtPaint just gave a warning message that it
couldn't open the file.

According to the mtpaint documentation,
librsvg is needed to open svg files.
_________________________________________________

[don570]

wary-500j04.iso observations:

When I first booted up with a frugal install ,
I tried the option pfix=nox for something different to test.

I chose English at the console but first run app was entirely
in Japanese and desk icons had Japanese labels.
This is not acceptable to an English user.

I chose 'English' with first run app , then there was a black screen
(with no warning) .. It remained for a long time, so I clicked and
the screen came back. Icons now had English labels.
Pupsaveconfig now launched and it was in English. Good!!

__________________________________________________

[L18L]

L18L wrote:

translating xorgwizard msgfmt and testing;
xorgwizard: silently does not anything

solved: was with xvesa
The Dialog was in the error file.
A small message on the screen would have been nicer.

[don570]

I did a vesa test of version4.
I chose English but this time I chose the Japanese keyboard
which is an easy mistake to make for an inexperienced user
because it is the default choice.

The warning screen 'Screen may turn black' was now much
better.

I discovered that the underscore character has now changed position.
The underscore character has become the equal sign.
This makes using pupsaveconfig harder to use.(see photo).

Also pressing the tilde key now brings up the Japanese character
insertion method SCIM.

Making English the default keyboard layout would solve this
problem.

This has convinced me that English users need a special opening screen
that is more user friendly for them.

[sc0ttman]

Making English the default keyboard layout would solve this
problem.

This has convinced me that English users need a special opening screen
that is more user friendly for them.

But this if for Japanese people

I think it's best to let shinobar carry on with a Japanese focused Wary, and later he will surely make his improvements made in this version available to be used in others. I think its enough at the moment to let users find their way into their language from Japanese.

Then once they've done that, they can test and give feedback on how to make localisation better for ALL users, not only English speaking users.

[shinobar]

I think it's best to let shinobar carry on with a Japanese focused Wary, and later he will surely make his improvements made in this version available to be used in others.

Thanks sc0ttman.
There is a chance a Multilingual Wary be released before the Japanese edition...

[L18L]

rodin.s wrote:

Maybe that line is for English-speaking people.

definitely not.
see attached screenshot showing pupsaveconfig in 3 languages.
OK button works, of course and the debug button is not needed in release version.

Why was I posting this issue?
The correction has to be done in script then new .pot file etc...

You can merge your old po file to the new like so:

Code: Select all

msgmerge old.po new.po -o - > newest.po

add the changes, rename po file, msgfmt and test.

Because of this I did yet not upload my translated pupsaveconfig.po.

shinobar wrote:

There is a chance a Multilingual Wary be released before the Japanese edition...

Yes it is, but 'don´t hurry be wary'
pupsaveconfig is the most essential script of any NLS_puppy IMHO (and your first use of gettext if I remember well).

[rodin.s]

Well, it's easy to fix. Need to add one gettext line and change 'Cancel' to 'OK'. I could do it later today. I use poedit and po-file will be updated from new pot-file.

[sc0ttman]

I think it's best to let shinobar carry on with a Japanese focused Wary, and later he will surely make his improvements made in this version available to be used in others.

Thanks sc0ttman.
There is a chance a Multilingual Wary be released before the Japanese edition...

I see, get a multi-lingual puppy out there, and when all the bugs are fixed, make a perfect Wary just for Japanese people, huh?

[rodin.s]

Let shinobar decide about pupsaveconfig.

Code: Select all

LATER='LEGACY'	# use legacy dialog after
ENGLISH='For English readers'
ENGLISH1="Click '$LATER' button if you cannot read next language. The save-file settings will be asked later. "
ENGLISH3='Your Puppy Linux is running under full install mode. '
ENGLISH5='is already used. '
ENGLISH8='Click next button.'
ENGLISH9="Just click 'Cancel' or close this window."
MINMB=512

I am not sure about gettexting it.

For delayedrun to work I changed the line

Code: Select all

export TEXTDOMAIN=welcome

I also have fixed russian welcome.po.

[L18L]

Having tested the russian welcome1stboot
(text not completely in dialog box, cut off at bottom)
I found a bug of mine, fixed please see:
http://www.murga-linux.com/puppy/viewto ... 3&start=50
@rodin-s you are right, let shinobar decide about pupsaveconfig.
@sc0ttsmann it really does not matter what is first, multi or japanese

[rodin.s]

Russian welcome1stboot looks OK at 1024x768 but not at 800x600. I don't know how to fix this, so leave it as it is.

[L18L]

Not OK at 1280x720 (my widescreen monitor, xvesa)
I also dont know how to fix it.
Maybe return to html ?

[rodin.s]

Tried to increase value in line 11 of welcome1stboot

Code: Select all

WINHEIGHT=535 

Possibly should be increased even more.
Are you testing build in or my yesterday corrected translation?
Can you post a screenshot.

And it's a good idea about replacing picture.

[L18L]

rodin.s wrote

Code: Select all

WINHEIGHT=535

and then I was trying this and that and then:

Code: Select all

#WINHEIGHT=635
#WINWIDTH=690

did it

[rodin.s]

Good. But it's better to use newer russian welcome.po - corrected some mistakes.

[L18L]

Now waiting for j06

edit and here are the corresponding .mo files

[shinobar]

Updated the current collection of the .pot and .po files wary_po_files-20110117.tar.gz here.

Note: you can also translate the help files at /usr/share/doc/help/C or /usr/share/doc/* and place the translations at /usr/share/doc/help/(language_code).

[charlie6]

Bonjour Shinobar !
Best wishes for 2011 !
Just discover this new Wary-500J04 here under Puppy Projects threads (OOOPS!).
Again thanks for your time!

In order to install a wacom tablet (i.e. Bamboo MTE-450 with Stylus, Pad, Touch Ring, and 4 "express keys" - no mouse as the stylus is used as a mouse).

As it was not present in Wary-500J04, I have picked up the wacom kernel module for k.2.6.31.14 from Barry's wary-500 full iso. Also installed the linux-wacom-8.8.10-w5.pet which contains the wacom tools: wacdump, xidump and xsetwacom.

My tablet works on wary-500 full edition. But do not on wary-500J04: the USB-tablet is well present in /proc/bus/input and /proc/bus/usb.

I am questionning about xorg.conf: it looks a bit different as the one in wary-500full: I had to add the complete Section "ServerLayout" (not present) as also the other wacom specific Section "InputDevice" bits. This xorg.conf was "accepted" by Xorg as Xorg did not reset to the default one.

here are xidump's answers: (xidump -l returns the xinput events , i.e. the list of input devices which are currently activated)

Code: Select all

# xidump pad
Unable to find input device 'pad'
# xidump stylus
Unable to find input device 'stylus'
#            
# xidump -l
pointer                        disabled
keyboard                       keyboard
# 

My questions:
- does wary-500full iso's wacom.ko module work here?
- is there somethibg special to do for editing xorg.conf?
- how to fix this?

Many thanks in advance for any answer!
Salutations cordiales, Charlie.