(old)Puppy Linux Discussion Forum

There are several things that can be done:

1. I'd recommend only translating utilities and wizards that have been addapted to use "getttext". If the text gets translated inside the script maintenance will be a nightmare and will always be out of sync. To translate the wizards and utilities we have to coordinate closelly with Barry so we don't end up translating old versions.

2. Collect all the .mo files for known applications in a common repository. I don't think the forum is the appropriate repository.

Currently there are several repositories available:
- My recommendation would be to use the subversion repository. It is the best way to make sure we are in sync and to coordinate the work from multiple people as it tracks versions, changes, contributors, etc.

I can grant write access to the people that require it. Every body currently has read access.

- Alternativelly we could use any of the ftp sites donated by members.
The one I regularly use is the space donated by GermanPup.
MU, klhrevolutionary and some other people have also offered hosting space.

deleted duplicate post

mtPaint 3.02 has up-to-date Spanish translation, and other translations, while incomplete, also are somewhat improved. If an older version is used in Puppy, I suggest switching to 3.02 - version 3.10 is in alpha stage still. and won't be released very soon.

Maybe others already know this, but Debian and Ubuntu have Spanish translation sections and one thing they do is list possible words as translation candidates/choices. In my opinion, it seems reasonable, wise, and time-efficient to take guidance from the work they have already done, rather than start all over and decide those issues on our own, at least at this point. This would also produce some translation similarities and continuity in Puppy for users who are familiar with another distro.

Another, related, issue is the possible need for an accepted list of terms to be used in all of puppy. A concern is that applications, desktop, wiki, and documentation all refer to items by either 1) the same term, or 2) the two or three terms that may be used. Problems and confusion may be caused if the wiki says "click on home", but the desktop only has an icon that says "inicio", and an aplication calls the button something else. A workaround may be -- where space allows -- to state "click on the 'home or inicio' button".

Producing a list of accepted terms may not be too difficult. Most terms are easy; only a few are difficult or problematic. An alternative option is that Puppy could adopt a list from another distro. What do people think about this?

I vote for 'inicio' ('beginning' or 'starting point'). I have problems with the term (I would prefer 'hogar' = 'home'), but other distros use 'inicio' and at least it's in Spanish. People with limited education (6th grade?), and Non-English speaking 'Grandma Nontechie' will understand 'inicio' better than 'home'.

I think both 'trash' and 'basura' are good because they are short, but they don't hint at the recycling function of the button, therefore they are not very intuitive. 'Papelera de reciclaje' ('paper bin for recycling') is very explanatory but maybe long. Also the RAE seems to prefer 'reciclamiento' instead of 'reciclaje'. That would makes the term longer: 'Papelera de Reciclamiento', but if it's not too long, then it might be the best, because it is the most accurate, precise, and intuitive.

If a shorter option is needed how about just 'reciclar' (recycle) or 'reciclamiento' (recycling)?

rarsa wrote:1. I'd recommend only translating utilities and wizards that have been addapted to use "getttext". If the text gets translated inside the script maintenance will be a nightmare and will always be out of sync. To translate the wizards and utilities we have to coordinate closelly with Barry so we don't end up translating old versions.

Yes, you're right. But I think this will take some time, so meanwhile I'm translating and testing wizards and other scripts. This is what I have working in spanish for Puppy 2.11:

Almost completed the pinboard apps:
-Seamonkey updated to 1.0.5 (html, browse, email and contacts icons)
-Gaim(chat icon)
-Gnumeric(calc icon)
-Abiword(word icon)
-Connect icon(Internet conection wizard)
-Setup icon(WizardWizard-almost all wizards translated)
-Install icon(and all scripts related)
-Trash icon
-PupZip icon (not XArchive)
-Lock icon

Another apps in the live-CD:
-gFTP
-puppyROX (yes, puppyRox not rox2.5)
-Xdialog
-make messages
-gcc messages
-mtpaint 3.01 shows spanish and english menues maybe updating to the next version works correctly?

Extra things:
-Country localization(money, date/time/telephone format, etc) for es_AR, es_BO, es_CL, es_CO, es_CR, es_DO, es_EC, es_ES, es_GT, es_HN, es_MX, es_NI, es_PA, es_PE, es_PR, es_PY, es_SV, es_US, es_UY, es_VE.
-es.lang file for Puppymenu-translator (JWM menu taken from puppy-2.12beta)
-ROX options file, with common key shorcuts (F3->Find; F2->Rename; Ctrl+C->Copy; / -> Enter path/Path bar; Ctrl+N->New window; and much more in spanish)
-Clipart images

Now I'm having some problems, the sfs doesn't update seamonkey, scripts(pupget, input-wizard, etc), what can I do? dotpups only? sfs+dotpups?

Actual size of es_langpack_211.sfs 17 MB / unpacked size 49 MB / unpacked without seamonkey 6~7 MB.

CatmanDru wrote: Maybe others already know this, but Debian and Ubuntu have Spanish translation sections and one thing they do is list possible words as translation candidates/choices. In my opinion, it seems reasonable, wise, and time-efficient to take guidance from the work they have already done, rather than start all over and decide those issues on our own, at least at this point. This would also produce some translation similarities and continuity in Puppy for users who are familiar with another distro.

Yes, there are many translation teams and some Debian and derivades langpacks. Seems easy take .mo files from that packages, but puppy is constantly updated, making a bit difficult complete the list from the beginning(I've already downloaded 2 spanish distros: Guadalinex and Archlinux, and I only have few .mo files matching with the software included in Puppy , so now I'm looking for sources)

sintot wrote:Hi:
I have also the mo files for geany, gqview, gftp , gslapt, slapt-get, LinNeighborHood, sweep and xfe.

I have downloaded mtpaint, but it's not working, the same as inkscapelite (but I rememeber inkscape did work)

wow, I can upload them here and you can include it in your sfs

Please upload your files here ftp://ftp.servage.net/Localization-proj ... C_MESSAGES you can use gFTP to do that.
If asks for user name and password type "puppy" for user and "linux" for password.

Webspace donated by Germanpup - up/down url: ftp://puppy:linux@ftp.servage.net/Local ... C_MESSAGES

About standard spanish names for desktop icons KDE has these:

(snapshot from my currently puppy 109CE + spanish KDE)

Some problems related to accentuation:

With accents

Without


Temporal solution: do not use accentuation

More screenshots:


1. Seamonkey 1.0.5 and JWMmenu
2. Spanish Rox showing keyboard shortcuts and pinboard
3. Abiword, Gnumeric, Gaim, Leafpad and X Server Chooser Wizard

try saving the script using utf-8 encoding

i had to put this line in my dotpup script to get it to display utf-8 characters:

export OUTPUT_CHARSET="utf-8"

Please upload your files here ftp://ftp.servage.net/Localization-proj ... C_MESSAGES you can use gFTP to do that.
If asks for user name and password type "puppy" for user and "linux" for password.

Webspace donated by Germanpup - up/down url: ftp://puppy:linux@ftp.servage.net/Local ... C_MESSAGES

I've tried to upload files to that direction, but it's not working with gftp nor firefox (but it works in opera...). I'm behind a router. Does it matter?

wow wrote:-mtpaint 3.01 shows spanish and english menues maybe updating to the next version works correctly?

Yes, this was one of things I fixed in the 3.02 release.

sintot wrote: I've tried to upload files to that direction, but it's not working with gftp nor firefox (but it works in opera...). I'm behind a router. Does it matter?

Router? maybe, but if you have Winslows you can upload using MS Internet Explorer without problem

GuestToo wrote:try saving the script using utf-8 encoding

i had to put this line in my dotpup script to get it to display utf-8 characters:

export OUTPUT_CHARSET="utf-8"

Some script uses mixed messages, e.g. chooselocale script, that use xmessage and Xdialog:
Character coding: ISO-8859-1

Character coding: UTF-8

Character coding: UTF-8 and gxmessages instead of xmessages


Thanks GuestToo, gxmessage is the solution. So I'll have to edit all others scripts and test if they work correctly.

I've downloaded the beta2 of puppy-2.12, and I will upload what I have till now for the 2.11 version after modifying definitively the scripts, it is still very preliminary so don't expect too much of this.

Ok, it's ready for testing. But I need to integrate the JWM Menu Translation Utility(written by MU) during the dotpup installation(without run the whole script) and try to translate the Rox Pinboard instead of overwrite it. If I have success you only will need to install the DotPup and restart X . Maybe tomorrow...

Hello,

How do you translate utilities and Wizards, and could you tell were are the corresponding files to translate in the filesystem. Do you use some tools to perform this work or do you directly translate the files in a text editor?
I have already made this work under Windows, but I don't know how to do it under Linux.
--
A+
gw

Hello,

Problem solved. I have found the scripts in /usr/sbin and have no difficulties to edit them in Leafpad.

A+
--
gw

gw wrote:Problem solved. I have found the scripts in /usr/sbin and have no difficulties to edit them in Leafpad.

Sorry for no answer, I'd a busy weekend.

I've finally uploaded the .sfs and a small .pup for this spanish patch for puppy-2.11, more info: http://208.109.22.214/puppy/viewtopic.php?t=12901

could you tell me what can i do?

iwigo wrote:could you tell me what can i do?

What can you do?

rarsa wrote:There are several things that can be done:

1. I'd recommend only translating utilities and wizards that have been addapted to use "getttext". If the text gets translated inside the script maintenance will be a nightmare and will always be out of sync. To translate the wizards and utilities we have to coordinate closelly with Barry so we don't end up translating old versions.

2. Collect all the .mo files for known applications in a common repository. I don't think the forum is the appropriate repository.

Currently there are several repositories available:
- My recommendation would be to use the subversion repository. It is the best way to make sure we are in sync and to coordinate the work from multiple people as it tracks versions, changes, contributors, etc.

I can grant write access to the people that require it. Every body currently has read access.

- Alternativelly we could use any of the ftp sites donated by members.
The one I regularly use is the space donated by GermanPup.
MU, klhrevolutionary and some other people have also offered hosting space.

About files, tools or whatever you can upload/download files here:
http://www.murga-linux.com/puppy/viewtopic.php?t=12629

Maybe help with the spanish section of the Wiki.

Join the Puppy Linux Documentation Project (PLDP)
http://www.murga-linux.com/puppy/viewtopic.php?t=3456

Or test my "little"(16 MB) experiment and post comments and suggestions:

English intructions: http://www.murga-linux.com/puppy/viewtopic.php?t=12901

Spanish instructions:

1. Hacer una copia de respaldo de pup_save.3fs. 1a 1b 1c
2. Copia el sfs "UnofficialLangPack-es_211.sfs"(16 MB) en la misma carpeta que el archivo pup_save.3fs. Para puppy 2.12 renombra el .sfs a <algo>_212.sfs
3. Arranca con Puppy instala el dotpup "Unofficial-langpack-es-211.pup"(907 KB)/"Unofficial-langpack-es-212.pup"(913 KB), espera unos segundos hasta que aparezca la ventana chooselocale, elige tu país ypresiona OK para reiniciar X.

Paso 1(crear la copia de respaldo) es opcional pero recomendable.
Este paquete solo funciona si tienes un archivo pup_save, no sirve si arrancas puppy en modo ram o si es la primera vez que inicias puppy. Eso es todo

Descargar:
Mirror1: FileFront.com
Mirror2: servage.net

La lista completa de los cambios hechos por este paquete está en los archivos "Unofficial-langpack-es-211.txt"/"Unofficial-langpack-es-212.txt"(disponibles en los sitios de descarga). Como una breve descripción puedo decir la exploración con ROX-filer/puppyROX es como en MS Windows (doble click para abrir, simple click para seleccionar, F3 para buscar, F2 para renombrar, etc), además debo aclarar que no es algo al 100% pero ayuda un poco

no ai nada para puppy 2.10? podria traducir algun programa, algun asistente o algo asi? gracias

De hecho, este parche funciona en versiones anteriores :S y además actualiza algunas cosas(incluye nuevas versiones para programas como Seamonkey, mtPaint, mp, etc. ), lo probé con mi puppy 1.09CE y funciona haciendo algunos cambios. asi que debería funcionar para la 2.10 también. Solo cambia el nombre del UnofficialLangPack_211.sfs por <nombre>_210.sfs e instala el dotpup.

Algo más, ya tengo listo el parche para la versión 2.12 de puppy(gtkdiff, ayuda mucho) solo tengo que probar que todo esté en orden y subirlo en las próximas horas.

y en que carpeta esta el pup_save.3fs? es que no lo encuentro ni bien ni mal
gracias por todo