Posted: Wed 16 Oct 2013, 13:49
I have posted PeasyDisc v2.0. It will require re-MoManager-ing.
READ-ONLY Archive
https://oldforum.puppylinux.com/
Puppus Dogfellow wrote: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.L18L wrote: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.
Puppus Dogfellow wrote:i made a folder of your apps in the utilities section of my repo:
rcrsn51--peasy, etc
thanks again, rcrsn51!
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.rcrsn51 wrote: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.rcrsn51 wrote: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.
Each app has its own collection of NLS files for different language.rcrsn51 wrote: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?
Puppus Dogfellow wrote:a folder for each app plus nls pets (...like how th) results in too many folders...
makes me suggest:vicmz wrote: big programs like LibreOffice which has more translation files
L18L wrote:Each app has its own collection of NLS files for different language.rcrsn51 wrote: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?
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.
Puppus Dogfellow wrote:a folder for each app plus nls pets (...like how th) results in too many folders...makes me suggest:vicmz wrote: big programs like LibreOffice which has more translation files
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:L18L wrote:One TEXTDOMAIN=peasy for all the peasy apps?
- Less files to maintain
- less messages to translate
it can be done.
my console wrote: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
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.Pelo wrote:Version 2.8, why to change ?