Author Topic: Converting our in House Scripts to PerlGTK  (Read 12829 times)

Offline Neal ManBear

  • Administrator
  • Super Villain
  • *****
  • Posts: 15847
  • LXDE! Coffee, Bacon and Cheesecake!
Re: Converting our in House Scripts to PerlGTK
« Reply #90 on: September 05, 2010, 07:18:27 AM »
Great!

New icon:


Offline rayman2

  • Full Member
  • ***
  • Posts: 71
Re: Converting our in House Scripts to PerlGTK
« Reply #91 on: September 09, 2010, 11:13:29 AM »
I don't know Perl(yet), but I'm willing to learn it(I'm still young :D).
Anything I can do(when I've finished some Perl tutorials)?
« Last Edit: September 09, 2010, 11:15:03 AM by rayman2 »

Offline Neal ManBear

  • Administrator
  • Super Villain
  • *****
  • Posts: 15847
  • LXDE! Coffee, Bacon and Cheesecake!
Re: Converting our in House Scripts to PerlGTK
« Reply #92 on: September 10, 2010, 01:43:26 AM »
Great!

New icon:




Is this new icon to be used for gezSwitch4 also? 


Yes, please use it.

Offline Neal ManBear

  • Administrator
  • Super Villain
  • *****
  • Posts: 15847
  • LXDE! Coffee, Bacon and Cheesecake!
Re: Converting our in House Scripts to PerlGTK
« Reply #93 on: September 10, 2010, 02:33:44 AM »
I had to resize it to 48 x 41 pixels.  Is that ok?

Certainly it is okay. Create whatever size you need.

Offline Mark342

  • Sr. Member
  • ****
  • Posts: 334
Re: Converting our in House Scripts to PerlGTK
« Reply #94 on: September 10, 2010, 05:50:41 PM »
New version of gezSwitch4:
http://www.box.net/shared/5b81xo0rap

Changes:
Removed "Update" button, because all it did was update the bootsplash file used by switch-themes.
This button served almost no purpose because the boosplash file used by switch-themes is already updated when a theme is changed in gezSwitch4.

Added "Refresh" button to reload the list of themes.
Changed the "Apply", "Quit", and "Reload" buttons to use stock items. This should give these buttons support for built-in GTK translations so no one has to translate them.

And finally:
Added support for translations of the main strings. **Needs to be tested**  ;)


Update on the status of the update notifier:
All of Travis's suggestions have been implemented.
Currently, the only thing holding it back from a new release is my virtualbox troubles. :(
This prevents me from testing the new changes.
Hopefully, I can get this back up and running soon.
Anything worth doing is worth overdoing.

Registered Linux user #493318
Register yourself here: Linux Counter

Offline Neal ManBear

  • Administrator
  • Super Villain
  • *****
  • Posts: 15847
  • LXDE! Coffee, Bacon and Cheesecake!
Re: Converting our in House Scripts to PerlGTK
« Reply #95 on: September 11, 2010, 05:05:20 AM »
I believe that the .po files go in /usr/share/locale.

Offline maik3531

  • Full Member
  • ***
  • Posts: 129
Re: Converting our in House Scripts to PerlGTK
« Reply #96 on: September 11, 2010, 06:08:10 AM »
Quote
Yes a testing package would be better. Are you going to build one?



I have taken as version 1.3 because I used the existing spec.

http://uploaded.to/file/o3itb2
« Last Edit: September 11, 2010, 06:17:26 AM by maik3531 »
Please excuse my English

Offline Texstar

  • Administrator
  • Super Villain
  • *****
  • Posts: 12514
Re: Converting our in House Scripts to PerlGTK
« Reply #97 on: September 11, 2010, 06:22:11 AM »
I have installed the latest version of gezSwitch4 in Zen mini which I have converted to Spanish with addlocale.
Not all things get translated.  Do I need to copy the messages.po file somewhere special?  I've never tested locale stuff.






That looks simply awesome!

Thanks to everyone who donates. You keep the servers running.

Offline slax

  • Sr. Member
  • ****
  • Posts: 391
    • PCLinuxOS Gnome Edition
Re: Converting our in House Scripts to PerlGTK
« Reply #98 on: September 11, 2010, 07:55:12 AM »
Great work ! :)

When it's finished, please send POT files for translations...



Offline Mark342

  • Sr. Member
  • ****
  • Posts: 334
Re: Converting our in House Scripts to PerlGTK
« Reply #99 on: September 11, 2010, 12:57:20 PM »
Ongoto, nothing has been translated yet. :D
A translator needs to use poedit to translate the strings.
Then the po is made into a mo.
The mo is shipped with the application.
The buttons using stock items are translated already because the translations are provided by GTK.

This guide on the forum should still work (with extra info in TRANSLATE.txt)
http://www.pclinuxos.com/forum/index.php/topic,57750.0.html

If a translation doesn't exist, it will default back to the original English text.
« Last Edit: September 11, 2010, 01:08:09 PM by Mark342 »
Anything worth doing is worth overdoing.

Registered Linux user #493318
Register yourself here: Linux Counter

Offline maik3531

  • Full Member
  • ***
  • Posts: 129
Re: Converting our in House Scripts to PerlGTK
« Reply #100 on: September 11, 2010, 03:57:07 PM »
Quote
This guide on the forum should still work (with extra info in TRANSLATE.txt)
http://www.pclinuxos.com/forum/index.php/topic,57750.0.html


The description under the link is only for bash scripts not for Perl Translation

-L DE
Die Beschreibung unter dem Link gilt nur für Bash Scripte nicht für Perl Übersetzung

in Perl with (N (TEXT)

Example:
BEGIN { unshift @::textdomains, 'update-notifier' }

    my $notif1 = Gtk2::Notify->new_with_status_icon(N('System update status',
        'Please wait, checking for new updates', 'networking_configuration_section', $status_icon));





Please excuse my English

Offline Mark342

  • Sr. Member
  • ****
  • Posts: 334
Re: Converting our in House Scripts to PerlGTK
« Reply #101 on: September 11, 2010, 07:54:35 PM »
Great work ! :)

When it's finished, please send POT files for translations...


Apparently, po files generated by xgettext are the same as pot files.
http://www.hagelnx.com/prog/782

Nevertheless, I have updated the tar.gz file so it contains a pot file.
I also discovered that it needs to be named the same name as the textdomain of the program.
So this was changed as well.
This now includes an example.po file that reverses the english words instead of translating them.

I've tested it and it seems to work fine.
TRANSLATE.txt was updated a bit.

http://www.box.net/shared/5b81xo0rap
« Last Edit: September 11, 2010, 07:57:43 PM by Mark342 »
Anything worth doing is worth overdoing.

Registered Linux user #493318
Register yourself here: Linux Counter

Offline rubentje1991

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2110
  • Rubenus Parvus MCMXCI
Re: Converting our in House Scripts to PerlGTK
« Reply #102 on: January 30, 2012, 01:58:59 PM »
Will this work be included in a next version of PCC?
Or is there still much work to be done?


[yes, I know it's an old topic; but it came in my mind - and maybe I just overlooked something (and thus already available); or it got unnoticed during time]


Thanks in advance!  :)

Offline Neal ManBear

  • Administrator
  • Super Villain
  • *****
  • Posts: 15847
  • LXDE! Coffee, Bacon and Cheesecake!
Re: Converting our in House Scripts to PerlGTK
« Reply #103 on: January 30, 2012, 02:06:55 PM »
Don't know when, Ruben. When I've got caught up a bit, I will take another look.     

Offline rubentje1991

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2110
  • Rubenus Parvus MCMXCI
Re: Converting our in House Scripts to PerlGTK
« Reply #104 on: January 30, 2012, 02:33:21 PM »
Don't know when, Ruben. When I've got caught up a bit, I will take another look.     

Take your time..... just wanted to mention it (and no, I don't want to give you stress..... but hurry up you  :P ;D ;D)
Thanks for replying  :)