Free to rename software for linux

GPRename is a GUI batch file renamer based on Gtk-Perl.

GPRename can rename files numerically, insert/delete characters at/between specified position(s), replace strings (either using regular express or not), and change case.

pyRenamer project allows you to change the name of several files at the same time easily.
Main features:
- You can use patterns to rename files.
- You can use search & replace to rename files.
- You can use common substitutions.
- You can manually rename selected files.
Installation:
tar xzvf pyrenamer-0.1.tar.gz
cd pyrenamer-0.1
./configure --prefix /usr
sudo make install
Enhancements:
- Now you can start pyRenamer in the directory that you want
- Preferences added to set default directories
- Added command line options to set directories
- Fixed bug on {num} pattern and syntax change from {num-2} to {num+2}
- Preview new filename when clicking PAGE_UP, PAGE_DOWN or RETURN on manual rename
- Add button to clear previewed filenames
- Better file selection filter
- Better unicode support
- Some GUI changes
- Bug fixes
- Check if directories set on Preferences are correct
- Remove debug info from console
- Fix bug reading preferences from gconf
- Activate Rename button on selection using keys

massrename is a general-purpose utility for batch-renaming file extensions, as well as strings within the base filename (for example, "SomeblehFile.mp3" to "SomeblahFile.mp3")
Usage: /usr/bin/massrename [ ARGUMENTS ] ...
Examples:
massrename --from mp3 --to ogg # rename *.mp3 to *.ogg
massrename -f ogg -t mp3 -n # rename *.ogg to *.mp3, no logging
Operation Modifiers:
Required arguments:
-f, --from source file extension or string to rename
-t, --to output file extension or string to rename to
Optional arguments:
-b, --beginning add a string to the beginning of the filename
-c, --change-dir DIR rename files in DIR instead of the current directory
-d, --dotfiles rename hidden files too
-e, --end add a string to the end of the filename
-h, --help display this help output and exit
-i, --ignore-case ignores filenames case when searching
for files to rename
-n, --no-logs dont make a log of renamed files
-p, --perl-rename use perls rename() function instead of the systems
"mv" command
-v, --version display version information and exit
-w, --within search for string within filename instead of extension
Enhancements:
- Minor bugfixes.
- The README file has been revised.
- An optional argument "--ignore-case" has been added, allowing massrename to ignore the case of filenames to be renamed at runtime.
- Debian and Red Hat package formats have been added.

Mp3 renamer 2006 by MiKe is a shell script for Linux. MP3 renamer goes by the Unix name of rename-mp3. It looks at MP3 files in a Directory and, using id3v2, will rename all the mp3 files in a nice format according to the id3 tags rename-mp3 will look at both v1 and v2 id3 tags, and will make the output file in a Title-Album-Artist.mp3 format.
It saves time, and not only will it read the id3 tags, but in the event that the MP3 file has no id3 tags, you will be given 4 options
1)abort 2)skip 3)rename 4)write id3 tags, and you are asked what you would like the id3 tag artist, track name and album to be.
This is great if you want the track to be easy to view and yet you still like having a library of music that is all tagged nicely!
Enhancements:
- New stuff: The INSTALLER now works, whereas before it wouldnt copy...

MySpace Friend Renamer provides an extension that allows you to rename your MySpace Friends.

This adds a right click option to Myspace Pages and allows you to change the display name for any of your friends. Handy if your friends change names often, or pick strange and obscure names.

Also in response to comments. If a tab is not in focus when the page loads, the extension will not rename.

I believe that the extension will conflict with other extensions that change pages when they load. If I find a better way to do it, I will change it.

RearSite is a simple collaborative Web site manager. RearSite is an automated Web publishing tool allowing to control who is allowed to access the published documents and also to manage per directories collaboratives tools well adapted to distance learning (forums, chats, shareable calendars, or multimedia quizzes).

An administrator can create users accounts (user name, user passwd, and user home directory), users get logged in and then receive access to their documents.


RearSite is written in PERL (CGI.pm based) and use a FastCGI compliant HTTP server (like APACHE).

Using RearSite is quite simple : after login, the user has access to his home dir and is able to delete, rename, create and edit documents. RearSite is well adapted to install WWW directories previously cooked (using any editors). Its very easy to transfer and install archives (ZIP, tar or tar.gz by now), they are automatically unpacked.

Published documents are public (by default), access restriction may be done using user/password couples, DNS domains or LDAP filters.

The user interface is WWW forms like, so RearSite only needs (on the client side) a Java, JavaScript and frames compliant WWW browser (accepting cookies).

RearSite is now quite secured, the login process (developped in Java) use an MD5 encryption of the user password (combined with a one time key). So, people spying the network cannot use the keys they may have seen. After login, users receive a cookie associated with their computers IP numbers.

RearSite also allows the user to specify who can retrieve his documents by configuring access rights :

documents are public (the default).
documents are restricted to users coming from trusted domains.
documents are restricted to users coming from trusted domains or to HTTP authenticated users.
* documents are restricted to class of users existing in an LDAP directory. This kind of HTTP client authentication needs auth_ldap for Apache (See restricted access by users classes).

Since 1.1, if the administrator wants it, the user is able to use templates to specify per directories access rights. By default (and as an example), the user can easily say that a directory is public, for frenchies only or for frenchies excepted those in the ripoux.fr domain (french joke!).

The user is also able to share his directories with other RearSite users (trusted users). When a directory is shared, a trusted user user is able to delete, rename, add ... files within the directory he received rights for.

The user is also able to recursively process all the file names of all his embeded directories. The functionality provided is to rename all files (lowercase, replace a string within all file names, ...) which simplyfies migration from systems with case-insensitive file names. These functionalities are available by selecting the Special tools button which also give a way to export the current directory within an archive (ZIP or tar.gz).

Since 1.4, a forum can directly be attached to each directories. When a user wants to create a forum, the result is a Forum.html file located within the current directory. This file will give access to the forum. People having access to this file are allowed to post in the forum.

Since 1.6, a chat can directly be attached to each directories. When a user wants to create a chat, the result is a Chat.html file located within the current directory. This file will give access to the chat. People having access to this file are allowed to talk in the chat.

Since 1.9, a shareable calendar can be directly attached to each directories. When a user wants to create a calendar, the result is a Calendar.html file located within the current directory. This file will give access to the calendar. People having access to this file are allowed to read the calendar. Only the owner of a calendar is allowed to update it, but he may allow other users. Accessing his calendar via RearSite allows the owner to update it immediatly. When accessing a calendar via a normal WWW access, the user (owner or not) must be authenticated (via Rearsite configured authentication scheeme) before being allowed to update it.

The chat,forum and calendar functionalities are accessible via the Communications button, they have been designed for distance learning purposes but can easily be used for any groupware needs.

wmtheme is a utility which, generally speaking, allows you to perform certain operations on themes by name. For example, to rename do wmtheme -r oldname newname, or to activate do wmtheme name.
Furthermore, it takes great care to make installation painless, in spite of evolving formats, packaging carelessness, and incompatibility between old themes and current window managers. wmtheme -i theme-package.tar.gz will almost always result in a correct installation.
It will also take steps to clean up settings that dont belong in themes, and disable suspicious-looking shell commands (these sorts of things might occur in Window Maker or Blackbox themes). This behavior can be turned off, however.
Enhancements:
- name matching now prefers an initial substring
- change Blackbox version parser to handle 0.65.0s -version output
- use pod for manpage
- support gtk+ version 2, discontinue support for gtk+ version 1
- remove attempts to compile gtk+ engines
- updates for changes in IceWM theme handling
- remove afterstep support