Extract-pet 1.7 - localised
Extract-pet 1.7 - localised
Extract-pet 1.7 - localised
Purpose: a simple right-click on pet package to extract all
files with their paths preserved. The original
file remains untouched.
Requirements for v1.7: Rox Filer or Thunar file manager.
Tested on Carolina and PreciseNOP which use Thunar.
Warning: When destination of extraction is a FAT32 drive -->
certain characters in filename aren't allowed. This can
cause potential problems!!! In particular I have found the colon
character to be a problem on files stored on USB sticks. You will
get a strange,confusing warning message.
I have improved Tazoc's script to give an additional
place to store the extracted folder and localised
the app.
It uses a combination of yaf-splash and Xdialog messages.
Purpose: a simple right-click on pet package to extract all
files with their paths preserved. The original
file remains untouched.
Requirements for v1.7: Rox Filer or Thunar file manager.
Tested on Carolina and PreciseNOP which use Thunar.
Warning: When destination of extraction is a FAT32 drive -->
certain characters in filename aren't allowed. This can
cause potential problems!!! In particular I have found the colon
character to be a problem on files stored on USB sticks. You will
get a strange,confusing warning message.
I have improved Tazoc's script to give an additional
place to store the extracted folder and localised
the app.
It uses a combination of yaf-splash and Xdialog messages.
- Attachments
-
- Extract-pet.pot.gz
- pot file for translators to fill and send back
- (2.11 KiB) Downloaded 1049 times
-
- Extract-pet-1.7.pet
- application to install
- (2.94 KiB) Downloaded 1875 times
-
- Extract-pet_NLS-1.7.pet
- foreign locales -French and German
- (2.03 KiB) Downloaded 1384 times
Last edited by don570 on Sat 16 Mar 2013, 19:26, edited 8 times in total.
new version 1.4
I've been concentrating on getting my extraction programs to work correctly
even when the packages have whitespace in their name. This happens
(albeit rarely) when the Windows downloader finds a similar file
stored on your hard disk so it makes a name change automatically
during the download. The file isn't corrupted at all . It's just that the
filename now has a space . An example --->
Fixed in version 1.4 extract-pet
_____________________________________________
I discovered that extractions shouldn't be done to
a Fat32 drive such as a USB stick. That's because Fat32 doesn't
support the colon character in filenames whereas linux does.
This could cause potential problems, so the general rule
should be DON"T DO EXTRACTION TO FAT32
_______________________________________________________
I've been concentrating on getting my extraction programs to work correctly
even when the packages have whitespace in their name. This happens
(albeit rarely) when the Windows downloader finds a similar file
stored on your hard disk so it makes a name change automatically
during the download. The file isn't corrupted at all . It's just that the
filename now has a space . An example --->
Code: Select all
bash_advanced_guide-6.6e (1).pet
_____________________________________________
I discovered that extractions shouldn't be done to
a Fat32 drive such as a USB stick. That's because Fat32 doesn't
support the colon character in filenames whereas linux does.
This could cause potential problems, so the general rule
should be DON"T DO EXTRACTION TO FAT32
_______________________________________________________
New version 1.5
-I've worked on the warning messages.
-I've found that problems with extracting on a Fat32 drive are rare
except for scripts that I have written!! That's because I use
a colon character for localization files i.e. fr:french or de:german
_______________________________________________________
-I've worked on the warning messages.
-I've found that problems with extracting on a Fat32 drive are rare
except for scripts that I have written!! That's because I use
a colon character for localization files i.e. fr:french or de:german
_______________________________________________________
new version 1.6
new version 1.6
- I have included LOC304 and LOC305. I was working too fast and
left them out
These locales will warn people about extracting on a FAT32 USB stick.
I have read on internet that not only some text characters won't
translate proplerly but also links have a problem with FAT32.
___________________________________________
- I have included LOC304 and LOC305. I was working too fast and
left them out
These locales will warn people about extracting on a FAT32 USB stick.
I have read on internet that not only some text characters won't
translate proplerly but also links have a problem with FAT32.
___________________________________________
version 1.7
version 1.7
Conversion to gettext localization and compatibility to
Thunar file manager. Tested on Carolina and PreciseNOP
which use Thunar.
There are French and German translations available.
I include the pot file which anyone can fill in translations to
their native language and send back to me.
Remove fake .gz extension to obtain pot file.
I can quickly make a mo file, which is placed in NLS file.
.
Conversion to gettext localization and compatibility to
Thunar file manager. Tested on Carolina and PreciseNOP
which use Thunar.
There are French and German translations available.
I include the pot file which anyone can fill in translations to
their native language and send back to me.
Remove fake .gz extension to obtain pot file.
I can quickly make a mo file, which is placed in NLS file.
.
- xanad
- Posts: 400
- Joined: Fri 28 Feb 2014, 14:56
- Location: 2 locations: MonteRosa Alp and Milano
- Contact:
Hi Don570
Extract-pet 1.7 - italian language
very useful
Extract-pet 1.7 - italian language
very useful
- Attachments
-
- Extract-pet.tar.gz
- (1.26 KiB) Downloaded 662 times
Uextract is what I use now. It is properly supported.
http://murga-linux.com/puppy/viewtopic.php?t=87864
____________________________________________________
http://murga-linux.com/puppy/viewtopic.php?t=87864
____________________________________________________