Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 01 Aug 2014, 18:46
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Fatdog64-630rc1 (16 Oct 2013) [CLOSED]
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 11 of 13 [195 Posts]   Goto page: Previous 1, 2, 3, ..., 9, 10, 11, 12, 13 Next
Author Message
don570


Joined: 10 Mar 2010
Posts: 3221
Location: Ontario

PostPosted: Thu 28 Nov 2013, 18:29    Post subject:  

Here's the latest bulldog finder that I've modified for fatdog
(because fatdog uses SendTo rather than OpenWith folder)


It searches for files using a right click menu
bulldog-finder_NLS-3.6.pet
Description  optional foreign locales
pet

 Download 
Filename  bulldog-finder_NLS-3.6.pet 
Filesize  5.04 KB 
Downloaded  113 Time(s) 
bulldog-finder-fatdog-3.5.pet
Description  find files with right click
pet

 Download 
Filename  bulldog-finder-fatdog-3.5.pet 
Filesize  8.36 KB 
Downloaded  116 Time(s) 
Back to top
View user's profile Send private message 
L18L

Joined: 19 Jun 2010
Posts: 2505
Location: Burghaslach, Germany somewhere also known as "Hosla"

PostPosted: Fri 29 Nov 2013, 08:51    Post subject: Re: Fatdog64-630rc1
Subject description: zarfy
 

L18L wrote:
jamesbond wrote:
Where can I get the latest standalone momanager? I'm thinking to get it in to Fatdog's devx so it's easier for everyone who wishes to translate.

see link for momanager 5 post up that from today 11:08
The link to momanager is here: http://www.murga-linux.com/puppy/viewtopic.php?t=89343&start=143

This is the version which I am using at the moment to test my internationalisations.
No langpackFatdog_de.pet made for now.

Momanager has to be changed (by me) to use another name for langpack (langpackFD or langpackFatdog or ....)
...and make sure that files of eventually loaded base langpack are not included..


Translators can use it now just to make translations of course....
Back to top
View user's profile Send private message 
L18L

Joined: 19 Jun 2010
Posts: 2505
Location: Burghaslach, Germany somewhere also known as "Hosla"

PostPosted: Fri 29 Nov 2013, 09:02    Post subject: Fatdog64-630rc1  

jamesbond

Please check this
Extract of fatdog64.pot sorted by message and my comment
to make it easier for translators


#: hwclockconf.sh:33
msgid “Cancelled"
msgstr “”

#: fatdog-set-hostname.sh:28
msgid “Cancelled!"
msgstr “”

One or the other only
---------------



#: fatdog-set-hostname.sh:28
#, sh-format
msgid “Nothing is changed, hostname stays as $HOSTNAME"
msgstr “”

#: fatdog-login-manager.sh:111
#, sh-format
msgid “Nothing is changed. The login mode stays as $MODE_TEXT"
msgstr “”

#: hwclockconf.sh:33
msgid “Nothing was changed."
msgstr “”


use 3rd msg (decide: is or was) to split msg1 and msg2
---------------------------------


#: fatdog-service-manager.xml.sh:78
msgid “Start at Boot"
msgstr “”

#: fatdog-service-manager.sh:212
msgid “Start at boot:"
msgstr “”

boot or Boot
--------------------------------

#: fatdog-login-manager.sh:103
msgid “Warning"
msgstr “”

#: fatdog-set-hostname.sh:15
msgid “Warning!"
msgstr “”

Warning or Warning!
-----------------------



#: fatdog-disk-usage.sh:99
msgid “Working"
msgstr “”

#: fatdog-service-manager.xml.sh:314
msgid “Working ..."
msgstr “”

#: fatdog-package-manager.sh.1.sh:515 fatdog-package-manager.sh.2.sh:520
#: fatdog-package-manager.sh:524
msgid “Working, please wait ..."
msgstr “”

#: fatdog-drive-mounter.sh:131
msgid “Working..."
msgstr “”

-----
use only 1 variant of “Working”
Back to top
View user's profile Send private message 
L18L

Joined: 19 Jun 2010
Posts: 2505
Location: Burghaslach, Germany somewhere also known as "Hosla"

PostPosted: Fri 29 Nov 2013, 13:43    Post subject: Fatdog64-630rc1
Subject description: control-panel-desktop
 

Skripts of fatdog-control-panel-desktop internationalized
see README for details



Sound and Network should follow sooner or later to make control panel complete.


edit
Thanks for downloading (7 times)
deleted now
because everything for control panel is
in http://www.murga-linux.com/puppy/viewtopic.php?t=89343&start=164 now

Last edited by L18L on Thu 05 Dec 2013, 12:24; edited 1 time in total
Back to top
View user's profile Send private message 
Scotchialoo

Joined: 25 Oct 2013
Posts: 54
Location: Poland

PostPosted: Sat 30 Nov 2013, 08:08    Post subject:
Subject description: Glibc - doesn't be respond a One week ago...
 

Even then doesn't be respond about a glibc -> http://www.murga-linux.com/puppy/viewtopic.php?p=739634#739634
And I will be waitng about a resolve to glibc...

UPDATE [3/12/2013]:

I looking at a /opt/glibc-2.18/ld.so.conf broke and After a /opt/glibc-2.18/ld.so.conf

Now I Working with a GCC Snapshot... (Because I can't even building with a 4.6.2 - I want to compile with a Newest packages...)
libslang-c.png
 Description   libslang.so.2 and libnewt.so.0.52 is not a Symbolic link.
[SECOND METHOD,after ld.so.conf]
 Filesize   58.37 KB
 Viewed   535 Time(s)

libslang-c.png

ld.so-c.png
 Description   Without ld.so.conf for /opt/glibc-2.18
 Filesize   63.92 KB
 Viewed   550 Time(s)

ld.so-c.png


Last edited by Scotchialoo on Tue 03 Dec 2013, 12:48; edited 2 times in total
Back to top
View user's profile Send private message Visit poster's website 
jamesbond

Joined: 26 Feb 2007
Posts: 2059
Location: The Blue Marble

PostPosted: Tue 03 Dec 2013, 12:22    Post subject:  

L18L,
Sorry for the slow response, got busy with other things and got distracted with this: http://murga-linux.com/puppy/viewtopic.php?p=740952#740952 Very Happy
I'm going to get back to it ... please bear with me Smile Btw let's name the pot as "fatdog.pot" instead of "fatdog64.pot", so one day we can use it for FatdogArm too...

don570,
Thanks for the pets, I'll upload them to the contributor's repo.

Scotchialoo,
For your earlier questions about chromium waterfall, sorry but I haven't got the chance to try it. As I suggested before, you can use the google-chrome sfs that kirk built - it runs nicely in 630r1 without the need to upgrade glibc. I may get around to test it but please don't hold your breath Laughing

For this question, I really don't understand what you're trying to say or do. I don't want to discourage you (experiment is a good thing) but as I have told you trying to update or build an app with a new glibc is *no trivial business*. Just because other distros make it look easy by providing a drop-in replacement for glibc, it doesn't mean you can easily do one yourself. You may also ask other knowledgeable people - like Ibidem, technosaurus, amigo - they are the experts when it comes to compiler intrinsics.

And as I have told you before, if all you need is a new glibc, you don't need to use a new version of new gcc. You can if you want, but then let's don't mix multiple problems together when one isn't solved yet - we'll get lost pretty quickly.

For whatever it is worth, the "errors" in your screenshots are just warnings; both are not fatal and can be ignored.

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 2059
Location: The Blue Marble

PostPosted: Tue 03 Dec 2013, 12:36    Post subject:  

L18L, your momanager pet contains fixmenus. Fatdog uses a totally different fixmenus from Puppy (it is in fact the jwm_menu_create from technosaurus). Do you need that fixmenus in the momanager's operation? If yes then we'll in a jam. If not, I'll just drop it and insert the rest (the momanager and langpack-template) to devx.

cheers!

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13
Back to top
View user's profile Send private message 
Scotchialoo

Joined: 25 Oct 2013
Posts: 54
Location: Poland

PostPosted: Tue 03 Dec 2013, 12:47    Post subject:  

jamesbond wrote:

I have told you trying to update or build an app with a new glibc is *no trivial business*. Just because other distros make it look easy by providing a drop-in replacement for glibc, it doesn't mean you can easily do one yourself. You may also ask other knowledgeable people - like Ibidem, technosaurus, amigo - they are the experts when it comes to compiler intrinsics.


Only That's trouble is that's not compatible a "Forward" :/ (Backward is a for example: glibc 2.12)
http://stackoverflow.com/questions/11107263/how-compatible-are-different-versions-of-glibc

"I have told you trying to update or build an app with a new glibc"
Or that's be what...? That's I will be downloaded a Source? If it's that's yes... When I will be migrate to another OS with a newest glibc... or I will be wait a another Distro with glibc 2.17... Or I will be try with a glibc... [Binary command - Portable from /opt will be works.]
Back to top
View user's profile Send private message Visit poster's website 
jamesbond

Joined: 26 Feb 2007
Posts: 2059
Location: The Blue Marble

PostPosted: Tue 03 Dec 2013, 13:36    Post subject:  

Scotchialoo wrote:

Only That's trouble is that's not compatible a "Forward" :/ (Backward is a for example: glibc 2.12)
http://stackoverflow.com/questions/11107263/how-compatible-are-different-versions-of-glibc

Yes that's a problem. The problem is that the chromium was built with a newer version of glibc and therefore expects a newer version of glibc *even though it is unnecessary to do so*.

Quote:
"I have told you trying to update or build an app with a new glibc"
Or that's be what...? That's I will be downloaded a Source?
Not asking you to download from source, in fact, I would discourage you to do so unless you want to experiment yourself. As I said earlier, I myself have never built chromium from source. What I suggested was to use the google-chrome sfs that kirk has created.

Quote:
If it's that's yes... When I will be migrate to another OS with a newest glibc... or I will be wait a another Distro with glibc 2.17...
Well that's your choice. I'm sorry that Fatdog doesn't meet your needs.

Quote:
Or I will be try with a glibc... [Binary command - Portable from /opt will be works.]
Ok, just for fun, I just tested myself now.
1. Build new binutils (2.23.2) - check.
2. Build new glibc (2.18 ) installed in /opt/glibc-2.18 - check
3. Glibc-2.18 working - check (run "LD_LIBRARY_PATH=/opt/glibc-2.18/lib /opt/glibc-2.18/lib/ld-linux-x86-64.so.2 /bin/busybox" shows busybox help messages)
4. Run chrome (LD_LIBRARY_PATH=/opt/glibc-2.18/lib:/usr/lib64/seamonkey:$LD_LIBRARY_PATH:$(pwd) /opt/glibc-2.18/lib/ld-linux-x86-64.so.2 ./chrome --disable-setuid-sandbox --user-data-dir /tmp)
and we are greeted with error:
"./chrome: symbol lookup error: ./chrome: undefined symbol: gconf_entry_get_key".
5. So copy the libgconf and stuff from google-chrome.sfs
6. Re-run chrome above - now we've got the error:
--type=zygote: error while loading shared libraries: --type=zygote: cannot open shared object file
[14079:14079:1204/004740:ERROR:resource_bundle.cc(607)] Failed to load /opt/glibc-2.18/lib/chrome_100_percent.pak
7. Copy chrome_100_percent.pak to /opt/glibc-2.18/lib
8. Re-run chrome, now we've got the error:
--type=zygote: error while loading shared libraries: --type=zygote: cannot open shared object file
9. rm -rf /opt/glibc-2.18, delete /root/chrome-linux, and launch firefox/seamonkey instead (or google-chrome.sfs).
10. Result: happiness Wink

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13
Back to top
View user's profile Send private message 
Scotchialoo

Joined: 25 Oct 2013
Posts: 54
Location: Poland

PostPosted: Tue 03 Dec 2013, 14:37    Post subject: Chromium with Newest glibc on Old glibc
Subject description: Waterfall+2.18 [Arch Linux] on glibc 2.13 [FatDog64]
 

jamesbond wrote:
Scotchialoo wrote:

Only That's trouble is that's not compatible a "Forward" :/ (Backward is a for example: glibc 2.12)
http://stackoverflow.com/questions/11107263/how-compatible-are-different-versions-of-glibc

Yes that's a problem. The problem is that the chromium was built with a newer version of glibc and therefore expects a newer version of glibc *even though it is unnecessary to do so*.

Quote:
"I have told you trying to update or build an app with a new glibc"
Or that's be what...? That's I will be downloaded a Source?
Not asking you to download from source, in fact, I would discourage you to do so unless you want to experiment yourself. As I said earlier, I myself have never built chromium from source. What I suggested was to use the google-chrome sfs that kirk has created.

Quote:
If it's that's yes... When I will be migrate to another OS with a newest glibc... or I will be wait a another Distro with glibc 2.17...
Well that's your choice. I'm sorry that Fatdog doesn't meet your needs.

Quote:
Or I will be try with a glibc... [Binary command - Portable from /opt will be works.]
Ok, just for fun, I just tested myself now.
1. Build new binutils (2.23.2) - check.
2. Build new glibc (2.18 ) installed in /opt/glibc-2.18 - check
3. Glibc-2.18 working - check (run "LD_LIBRARY_PATH=/opt/glibc-2.18/lib /opt/glibc-2.18/lib/ld-linux-x86-64.so.2 /bin/busybox" shows busybox help messages)
4. Run chrome (LD_LIBRARY_PATH=/opt/glibc-2.18/lib:/usr/lib64/seamonkey:$LD_LIBRARY_PATH:$(pwd) /opt/glibc-2.18/lib/ld-linux-x86-64.so.2 ./chrome --disable-setuid-sandbox --user-data-dir /tmp)
and we are greeted with error:
"./chrome: symbol lookup error: ./chrome: undefined symbol: gconf_entry_get_key".
5. So copy the libgconf and stuff from google-chrome.sfs
6. Re-run chrome above - now we've got the error:
--type=zygote: error while loading shared libraries: --type=zygote: cannot open shared object file
[14079:14079:1204/004740:ERROR:resource_bundle.cc(607)] Failed to load /opt/glibc-2.18/lib/chrome_100_percent.pak
7. Copy chrome_100_percent.pak to /opt/glibc-2.18/lib
8. Re-run chrome, now we've got the error:
--type=zygote: error while loading shared libraries: --type=zygote: cannot open shared object file
9. rm -rf /opt/glibc-2.18, delete /root/chrome-linux, and launch firefox/seamonkey instead (or google-chrome.sfs).
10. Result: happiness Wink


Thanks. That's does be help ;D [Three Step.] - Busybox works. Even on a leafpad and geany. (LD_TRACE_LOADED_OBJECTS=1 - in Debugs will be works.)
But that's works only on a "Arch Linux" Method. [FatDog64 Compile with a Developent binutils will be shows a "Segmentation fault"...]
But in 9 Step That's command will be remove glibc-2.18 when I will be keep.
Even I have a same error in a "--type=zygote" a Four step ;D [More easy.]
I copyed a chrome_100_percent.pak to /opt/glibc-2.18 and will be help.
But that's one problem is a doesn't running... (When Command it's works. - But That's not started... Because That's depend a "murrine" and "equinox")
When I am going to find about a libgconf after a "Chromium started" [with Murrine and equinox theme.] - That's optional but That's not important on a Find Chromium runtime...
Back to top
View user's profile Send private message Visit poster's website 
jamesbond

Joined: 26 Feb 2007
Posts: 2059
Location: The Blue Marble

PostPosted: Tue 03 Dec 2013, 23:05    Post subject: Re: Chromium with Newest glibc on Old glibc
Subject description: Waterfall+2.18 [Arch Linux] on glibc 2.13 [FatDog64]
 

Scotchialoo wrote:
Thanks. That's does be help ;D [Three Step.] - Busybox works. Even on a leafpad and geany. (LD_TRACE_LOADED_OBJECTS=1 - in Debugs will be works.)
But that's works only on a "Arch Linux" Method.
I don't know what you mean by "Arch Linux" method.

Quote:
[FatDog64 Compile with a Developent binutils will be shows a "Segmentation fault"...]
Didn't I say it is not easy?

Quote:
But in 9 Step That's command will be remove glibc-2.18 when I will be keep.
Yes - in case you don't get it, I gave up after step 8, so step 9 is just to forget everything and step 10 is to run firefox instead Laughing

Quote:
Even I have a same error in a "--type=zygote" a Four step ;D [More easy.]
I copyed a chrome_100_percent.pak to /opt/glibc-2.18 and will be help.
But that's one problem is a doesn't running... (When Command it's works. - But That's not started... Because That's depend a "murrine" and "equinox")
I don't get what you mean. "murrine" and "equinox" is GTK themes - they have nothing to do with glibc.

Quote:
When I am going to find about a libgconf after a "Chromium started" [with Murrine and equinox theme.] - That's optional but That's not important on a Find Chromium runtime...
I don't get what you mean by this.
_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13
Back to top
View user's profile Send private message 
Scotchialoo

Joined: 25 Oct 2013
Posts: 54
Location: Poland

PostPosted: Wed 04 Dec 2013, 06:53    Post subject: Re: Chromium with Newest glibc on Old glibc
Subject description: Waterfall+2.18 [Arch Linux] on glibc 2.13 [FatDog64]
 

jamesbond wrote:
Scotchialoo wrote:
Thanks. That's does be help ;D [Three Step.] - Busybox works. Even on a leafpad and geany. (LD_TRACE_LOADED_OBJECTS=1 - in Debugs will be works.)
But that's works only on a "Arch Linux" Method.
I don't know what you mean by "Arch Linux" method.

Quote:
[FatDog64 Compile with a Developent binutils will be shows a "Segmentation fault"...]
Didn't I say it is not easy?

Quote:
But in 9 Step That's command will be remove glibc-2.18 when I will be keep.
Yes - in case you don't get it, I gave up after step 8, so step 9 is just to forget everything and step 10 is to run firefox instead Laughing

Quote:
Even I have a same error in a "--type=zygote" a Four step ;D [More easy.]
I copyed a chrome_100_percent.pak to /opt/glibc-2.18 and will be help.
But that's one problem is a doesn't running... (When Command it's works. - But That's not started... Because That's depend a "murrine" and "equinox")
I don't get what you mean. "murrine" and "equinox" is GTK themes - they have nothing to do with glibc.

Quote:
When I am going to find about a libgconf after a "Chromium started" [with Murrine and equinox theme.] - That's optional but That's not important on a Find Chromium runtime...
I don't get what you mean by this.


Ok... But If it doesn't resolve problem with Chromium runtime [with a Forward-compatibile]...
When I want to a find a useless files for a "FatDog-Like Build" for a example: "alsa-lib" without "aterm" (Instead of ~300mb-400mb -> ~210mb,without Seamonkey or With a mesa/linux kernel compile) - for a T2-SDE Trunk. [With a Openbox/LXDE based.] from a "/<t2-trunk>/packages/<base>" - If you want you can write from a Full source folders. (~800 folders)
When If That's ISO build will be completed...
When I want to extract to [LiveUSB/HDD]: "extlinux.conf" [Boot but that's not important] + "initrd" [OS + for example: Trunk.sfs (libraries)] + ldlinux.sys + vmlinuz
I know... I am a doesn't be finding without help... But I will be find for a "easy-make-trunk build"...
Back to top
View user's profile Send private message Visit poster's website 
L18L

Joined: 19 Jun 2010
Posts: 2505
Location: Burghaslach, Germany somewhere also known as "Hosla"

PostPosted: Wed 04 Dec 2013, 09:40    Post subject:  

jamesbond wrote:
...let's name the pot as "fatdog.pot" instead of "fatdog64.pot", so one day we can use it for FatdogArm too...

OK I will rename all TEXTDOMAINs from fatdog64 to fatdog
.. and upload everything under control panel in one package.
(and move fatdog64.mo to fatdog.mo)

jamesbond wrote:
L18L, your momanager pet contains fixmenus. Fatdog uses a totally different fixmenus from Puppy (it is in fact the jwm_menu_create from technosaurus). Do you need that fixmenus in the momanager's operation? If yes then we'll in a jam. If not, I'll just drop it and insert the rest (the momanager and langpack-template) to devx.
It has been Barry's work to use fixmenus. Thus the translator can see his translation of menu items in action.
My fixmenus in momanager is just a bit faster because it uses what everyone can learn from technosaurus (from 15 sec to 5 sec).
Having installed momanager the link to jwm_menu_create was stronger than the copy i.e. the link has continued to work.
This fixmenus link is running in 0.5 sec on my box now!

I did not take notice from all of this. I have changed to "xwin jwm" now and it kind of works because I have a translation file /usr/share/locale/de/LC_MESSAGES/jwm (no .mo).


... and a bug fix:
replace
Code:
eval `grep '^LANG=' /etc/profile`

by
Code:
read LANG < $HOME/.fatdog/language

in all /usr/local/bin/default*
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 2059
Location: The Blue Marble

PostPosted: Thu 05 Dec 2013, 11:28    Post subject:  

Scotchialoo, no offense, but I'm finding it very difficult to understand what you are trying to say. I understand that English is not your primary language - but you're not the only one; there are many others here whose native language isn't English. Some of them also write broken English too but at least but at least they are understandable. Please try to express yourself better. Otherwise none of us can answer your question when we don't even understand what is being asked.

L18L wrote:
OK I will rename all TEXTDOMAINs from fatdog64 to fatdog
.. and upload everything under control panel in one package.
(and move fatdog64.mo to fatdog.mo)
Oops, sorry I forgot renaming the pot/po/mo means you have to redo the TEXTDOMAIN ... but let's do it before the changes get to extensive.

Quote:
It has been Barry's work to use fixmenus. Thus the translator can see his translation of menu items in action.
My fixmenus in momanager is just a bit faster because it uses what everyone can learn from technosaurus (from 15 sec to 5 sec).
Having installed momanager the link to jwm_menu_create was stronger than the copy i.e. the link has continued to work.
This fixmenus link is running in 0.5 sec on my box now!

I did not take notice from all of this. I have changed to "xwin jwm" now and it kind of works because I have a translation file /usr/share/locale/de/LC_MESSAGES/jwm (no .mo).
Hmmm, so I'll just use Fatdog's fixmenus, right?

Quote:

... and a bug fix:
replace
Code:
eval `grep '^LANG=' /etc/profile`

by
Code:
read LANG < $HOME/.fatdog/language

in all /usr/local/bin/default*

My /usr/local/bin/default* doesn't have anything with LANG in it yet ...

cheers!

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13

Last edited by jamesbond on Thu 05 Dec 2013, 12:37; edited 1 time in total
Back to top
View user's profile Send private message 
L18L

Joined: 19 Jun 2010
Posts: 2505
Location: Burghaslach, Germany somewhere also known as "Hosla"

PostPosted: Thu 05 Dec 2013, 12:17    Post subject:  

jamesbond wrote:
L18L wrote:
OK I will rename all TEXTDOMAINs from fatdog64 to fatdog
.. and upload everything under control panel in one package.
(and move fatdog64.mo to fatdog.mo)
Oops, sorry I forgot renaming the pot/po/mo means you have to redo the TEXTDOMAIN ... but let's do it before the changes get to extensive.
No need to be sorry.
pot and po are created automatically by momanager.
rename of .mo is just 1 file
re-definition of TEXTDOMAIN is done now.
All scripts of fatdog-control-panel in one attached file control-panel.tar.gz.

jamesbond wrote:
...Hmmm, so I'll just use Fatdog's fixmenus, right?

....Hmmmm, for now: yes.
Will have to look back into jwm_menu_create deeper.

Quote:
My /usr/local/bin/default* doesn't have anything with LANG in it yet ...
Thanks! It must have been me who has brought it into the game. Embarassed
Anyhow, if it will ever be needed
Code:
read LANG < $HOME/.fatdog/language
is much faster than eval `grep ....`


Next step will be to teach momanager
- create langpack_fatdog_*
- hide translation of /usr/share/desktop-directories/*.directory
- hide translation of /usr/share/sss (SimpleStringSubstitution)
control-panel.png
 Description   jwm menu with German localization
visible by right-click on background
 Filesize   8.62 KB
 Viewed   291 Time(s)

control-panel.png

control-panel-i18n.tar.gz
Description  all scripts of
fatdog-control-panel with internationalization
to be merged into /
gz

 Download 
Filename  control-panel-i18n.tar.gz 
Filesize  149.57 KB 
Downloaded  112 Time(s) 
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 11 of 13 [195 Posts]   Goto page: Previous 1, 2, 3, ..., 9, 10, 11, 12, 13 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

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


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1475s ][ Queries: 12 (0.0067s) ][ GZIP on ]