...when packagers do crazy crap like including the user config in root rather than modifying the global one in /etc)

I am sooooooo guilty of that! vlc-gtk, browser-installer, toggle-rox-desktop, feh, conky, elinks, desksetup - I wondered where to put their config files and always ended up in /root

its not really anything for you to worry about if you are packaging for only Puppy, just if you are making portable packages for use in other distros

normally there is a system default in /etc
the way it works is "program" looks in default location for user config
if it exists, then it is used
if parameters are changed, it copies to home with the change (if the program can modify its defaults)

for example jwm will look for /etc/system.jwmrc if it doesn't exist in $HOME but since jwm doesn't have a builtin tool to modify its own config file, it is not copied

rox on the other hand can modify options and will look in /etc/xdg/rox.sourceforge.net/
(actually its $XDG_CONFIG_DIRS/rox.sourceforge.net/*/*)
before saving changes to
$HOME/.config/rox.sourceforge.net/*/*_________________Web Programming - Pet Packaging 100 & 101

@wuwei
most of the translations are using gettext system.
.pot file --> .po file --> .mo file
.pot to .po, you can use a text editor, but I usually use poedit.
Take it easy. You can easily catch the how to.
poedit-1.4.2-3-i686.pet or poedit-1.4.2-4.sfs from http://shino.pos.to/party/bridge.cgi?puppy/wary/opt/

@wuwei
most of the translations are using gettext system.
.pot file --> .po file --> .mo file
.pot to .po, you can use a text editor, but I usually use poedit.
Take it easy. You can easily catch the how to.
poedit-1.4.2-3-i686.pet or poedit-1.4.2-4.sfs from http://shino.pos.to/party/bridge.cgi?puppy/wary/opt/

The .pot files can be found at /usr/share/doc/nls in akita linux.

Call me stupid shinobar,
but I'd rather not fiddle with all these steps, just to get to a text.
I gladly offer some translation work, but would appreciate a Geany readable textfile to start from, if it is not too much asked.

'd rather not fiddle with all these steps, just to get to a text.
I gladly offer some translation work, but would appreciate a Geany readable textfile to start from, if it is not too much asked.

For example, look up the file /usr/share/doc/nls/jwmconfig.pot by geany.
The .pot file is a template and .po is for a specific language.

Copy jwmconfig.pot to jwmconfig_de.po.
You can edit the .po file by geany, but remark you must use UTF-8 encoding.
Keep the english at each line of msgid.
Write the german at each line of msgstr.

EXAMPLE:
msgid "Shortcut Details"
msgstr "Shortcut Einzelheiten"

Post the .po file here then another guy can convert .po to .mo.
(poedit does it automatically.)_________________Downloads for Puppy Linux http://shino.pos.to/linux/downloads.htmlLast edited by shinobar on Fri 23 Sep 2011, 11:25; edited 2 times in total

Sc0ttman, I believe @Shinobar had solved this in his WARY versions. He may be able to offer something helpful.

Hope this helps._________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum