Peasy-apps Localized

[rcrsn51]

I have posted PeasyDisc v2.0. It will require re-MoManager-ing.

[L18L]

re-MoManager-ed

[Bert]

PeasyDisk 2.3 in Dutch.

[robwoj44]

Polish translation for peasywifi-3.0

[rcrsn51]

Thank you. I hope that v2.3 will be final for a while.

[xanad]

Italian translations:

peasyglue
peasypdf
peasyport
peasyprint
peasyscale
peasyscan

all in *.mo and *.po

[rcrsn51]

Grazie!

[xanad]

Ciao rcrsn51,
new adds in italian language

yassm
legacy_grub_2013

[Puppus Dogfellow]

i made a folder of your apps in the utilities section of my repo:

rcrsn51--peasy, etc


thanks again, rcrsn51!

[L18L]

As this section is Localization Project it is a pity that there are no localizations (*-NLS.pet) found in that repo.
Please correct me if I am wrong.

i made a folder of your apps in the utilities section of my repo:

rcrsn51--peasy, etc


thanks again, rcrsn51!

[Puppus Dogfellow]

As this section is Localization Project it is a pity that there are no localizations (*-NLS.pet) found in that repo.
Please correct me if I am wrong.

i made a folder of your apps in the utilities section of my repo:

rcrsn51--peasy, etc


thanks again, rcrsn51!

there are many .NLS pets in the repo, although none in that particular folder, and far fewer than i remember adding, to be honest--i usually include them if i see them, except perhaps when i'm downloading to install something personally and am rushing about. as an attempt to reduce the overwhelming pathos of the situation, i placed a text document in the folder directing translators to this thread. further, i see no particular shame in offering the apps in one place for any to either use, translate, or use and translate. this thread is the most convenient way i knew of to locate rcrsn's programs--just seemed to make sense to link the folder here as it covers more than any individual app's thread does.

that said, and to further alleviate the the pain and suffering this has all caused, i would gladly host the nls pets that go to the apps in the folder if you like. are the gz files in this thread actually nls pets? if so, why aren't they pets?

i can't help out with any actual translations, but hosting stuff is no problem.

[L18L]

Puppus Dogfellow,

no shame pain and suffering intended
I was just hoping to get all peasy-NLS.PETs translations in one location.

My regards

[rcrsn51]

I don't know the best way to handle this. Should each app have its own collection of NLS files for different languages? Or should each language have a collection of NLS files for the different apps?

Since many community members have generously translated Peasy-apps, I am unwilling to second-guess how they have organized it.

[Puppus Dogfellow]

I don't know the best way to handle this. Should each app have its own collection of NLS files for different languages? Or should each language have a collection of NLS files for the different apps?

Since many community members have generously translated Peasy-apps, I am unwilling to second-guess how they have organized it.

links could be arranged here and easily copied back to text pages in the repo in multiple ways, but i'd have two items in the folder for each app, the app itself and a folder of language packs or nls.pets, sort of how the libreoffice language packs (thanks to vicmz) inthis folder are setup.

a folder for each app plus nls pets (like how the geany 1.25 folder--courtesy of corvus--is set up) results in too many folders and (gasp) possibly an unnecessary click.

anyway, not set in stone.

[vicmz]

I don't know the best way to handle this. Should each app have its own collection of NLS files for different languages? Or should each language have a collection of NLS files for the different apps?

Since many community members have generously translated Peasy-apps, I am unwilling to second-guess how they have organized it.

Usually each app has its own NLS.pet with translations in a few languages. A pet for each language is not really practical, except for big programs like LibreOffice which has more translation files, not just a simple .mo for each language so in this case making individual 1~3 MB pets makes more sense.

Puppy language packs usually include translations for the version included in a Puppy .iso file. NLS pets are meant to have the latest translations for the latest versions.

[L18L]

Should each app have its own collection of NLS files for different languages? Or should each language have a collection of NLS files for the different apps?

Each app has its own collection of NLS files for different language.
In Puppy this is app-NLS.pet

Each language has a collection of NLS files for the different apps.
In Puppy this is langpack_
The developer of apps should not have to care about language packs I think.

a folder for each app plus nls pets (...like how th) results in too many folders...

big programs like LibreOffice which has more translation files

makes me suggest:
One TEXTDOMAIN=peasy for all the peasy apps?
- Less files to maintain
- less messages to translate
it can be done.

[Puppus Dogfellow]

Should each app have its own collection of NLS files for different languages? Or should each language have a collection of NLS files for the different apps?

Each app has its own collection of NLS files for different language.
In Puppy this is app-NLS.pet

Each language has a collection of NLS files for the different apps.
In Puppy this is langpack_
The developer of apps should not have to care about language packs I think.

a folder for each app plus nls pets (...like how th) results in too many folders...

big programs like LibreOffice which has more translation files

makes me suggest:
One TEXTDOMAIN=peasy for all the peasy apps?
- Less files to maintain
- less messages to translate
it can be done.

i could update nls pets just as easily as the apps themselves. if it's just apps and nls pets, everything could just all go in the same folder. i don't know how the languages roll in or the frequency with which they get updated, but any language pack that's not part of an nls pet (the actual mechanics of making these pets aside) can go into a Pending-Inclusion folder (or something similar). they'd be auto-alphabetized by app-lang (or something similar) in a repeating pattern--should be easy enough for the user to sift through regardless how big or behind the folder got.

keeping it app.pet plus nls.pet only in the folder would be easiest for me, or at least easiest to keep up to date (based merely on infrequency of uploads waiting around for me to realize they're there), but however those actually working on it want it is fine with me (caveat about potentially marooned pets still applicable, but the issue is certainly now more on my radar).


so roughly how much of puppy is still untranslated after the user chooses language at startup?

[L18L]

One TEXTDOMAIN=peasy for all the peasy apps?
- Less files to maintain
- less messages to translate
it can be done.

It has be done now:
You might use TEXTDOMAIN=peasy for all apps named peasy*.
No translator has to do additional work
as attached script merges the existing translations into one .mo file.

Note, number of messages is decreased from 370 to 318.

Merge existing GNU/gettext translations
oldTEXTDOMAINs=peasy*
newTEXTDOMAIN=peasy

lang=de
142 de/LC_MESSAGES/peasydisc.mo
32 de/LC_MESSAGES/peasyglue.mo
77 de/LC_MESSAGES/peasypdf.mo
24 de/LC_MESSAGES/peasyport.mo
42 de/LC_MESSAGES/peasyprint.mo
18 de/LC_MESSAGES/peasyscale.mo
35 de/LC_MESSAGES/peasyscan.mo
370 LC_MESSAGES/peasy*.mo in lang=de
msgcat -o /tmp/peasy_.po /tmp/peasydisc.po /tmp/peasyglue.po /tmp/peasypdf.po /tmp/peasyport.po /tmp/peasyprint.po /tmp/peasyscale.po /tmp/peasyscan.po
318 LC_MESSAGES/peasy.mo in lang=de

lang=en
0 LC_MESSAGES/peasy*.mo in lang=en

lang=fi
0 LC_MESSAGES/peasy*.mo in lang=fi

done

[Pelo]

PeasyWifi now a standard at Pelo's home.
When an application runs without any bug, information has to be posted in the topic ! Done.
Version 2.8, why to change ?

[rcrsn51]

Version 2.8, why to change ?

If V2.8 does everything you need, there is no need to change. PWF is just a front-end for some standard command-line tools. They don't change.

Most of the updates to PWF since v2.8 are for special situations that you might never see.