Akemi Yagi wrote: > It is very much possible that people on the -docs mailing list are not > reading the -devel list where you have posted details on the Artwork. > It will be helpful if you refer to the relevant posts, or better yet > provide more info here, so the translators can figure out what exactly > they should do to help. Akemi, Thank you very much for responding the translation request. Here is more information about centos-art.sh and the steps translators need to follow in order to add their work to it. What is the centos-art.sh script? --------------------------------- The centos-art.sh script is a bash script, written with the intention of standardizing most production tasks inside The CentOS Artwork Repository (https://projects.centos.org/svn/artwork/). It also implements relation between different work lines in order to grantee consistent results between them. How to translate the centos-art.sh script? ------------------------------------------ 1. Download a working copy of The CentOS Artwork Repository to your workstation. See http://wiki.centos.org/ArtWork 2. Once you have a functional working copy, be sure the LANG environment variable refers the locale information you want to contribute. For example, when I translate the centos-art.sh script to Spanish, the LANG environment variable on my system has the `es_ES.UTF-8' value. 3. Run the locale functionality of centos-art.sh as following: centos-art.sh locale trunk/Scripts/Bash --update --edit --dont-commit-changes This command will retrieve translatable strings from all .sh files under `trunk/Scripts/Bash' directory and will create/update the related portable objects inside `trunk/Locales/Scripts/Bash/${LANG}/' directory and later will open related portable objects in your favorite text editor for you to work on content translation. As translator, you don't need to touch the files under `trunk/Locales' directory, the centos-art.sh script does that for you. This would help to keep a consistent directory structure inside the repository. If you need to organize files in a different way, let's talk about it here first. In case you just want to translate a specific functionality, not all of them, use the --filter option. This option accepts a regular expression pattern as value which must match the path used to find files inside the location you provided as argument (trunk/Scripts/Bash in this case). For example, to translate Commons and Render functionalities only, run the following command: centos-art locale trunk/Scripts/Bash --update --edit --filter='(Commons|Render)' --dont-commit-changes In case you remove the --dont-commit-changes option from your commands, centos-art.sh script will perform all the subversion stuff for you. So you don't have to take care of updating your working copy to receive changes from others or remember commands and paths to commit your own changes. Presently, centos-art.sh script uses the following metadata in portable objects: "Report-Msgid-Bugs-To: Documentation SIG <centos-docs@xxxxxxxxxx>\n" "Last-Translator: Documentation SIG\n" but translators can use the `Last-Translator:' field to refer their name and e-mail address if they want ot. Changes of this information will be recored within each commit you make up to the central repository. Basically, this is the procedure translators need to follow in order to contribute their work to centos-art.sh script. There is much more translators can do inside The CentOS Artwork Repository, but let's talk about that later, once centos-art.sh script be localized and translators feel more familiar with centos-art.sh script and the way it operates. In case you face any difficulty following these steps, please let me know. Best regards, -- Alain Reguera Delgado <alain.reguera@xxxxxxxxx> _______________________________________________ CentOS-docs mailing list CentOS-docs@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos-docs
