Goals of this document
- To provide easy to use instructions for the people involved in localizing Camino, who need to distribute autonomously their work or need to send it to who builds the multilanguage package
- To create standard rules to be followed when localizators build their packages
- To allow circulation of smaller packages among localizators, so that broadband shouldn't be a requirement in order to participate to the project

- This document assumes that you have Apple's Developer Tools installed; if you don't have them, you wouldn't be able to work on the localization, anyway. Please see our AppleGlot How-To for more information about getting started in the localization workflow
- You need to be comfortable with the terminal: no particular skills are needed, you just have to be able to type in easy commands and change your working directory with the cd command

Tools we use
- A shell script that helps extracting the localization content from a localized application
- A preflight script that will be useful with the package (it checks wether the user selected folder actually contains the Camino application)
- A background image for your installer package to become good looking and Camino-esque
+ You may download the 2 scripts and the background image, conveniently archived and organized in folders ready for packaging: download the archive
- PackageMaker (included with Apple's Developer Tools*)
- A file compression utility (the ZIP archiver available in OS X 10.3 and later will be our first choice)

Prepare for the packaging
- Uncompress the archive you have downloaded; it will become a folder that will contain some stuff needed for the packaging: inside that folder, you find a script pkg_make.sh and 2 subfolders: Content and Resources
- Inside Resources you find the preflight script and the background image
- Add to the Resources folder 2 RTF files, named Welcome.rtf and ReadMe.rtf
- Welcome.rtf is the first thing that the user will read when she launches the installer package: keep it short and just announce that the user is about to install a localization for Camino; the more you keep this text generic, the less you will have to update it when Camino is updated (for example, avoid to specify here the version number)
- ReadMe.rtf might contain a translation of the Release Notes.rtf file that comes with the original Camino distribution
- Copy the freshly localized version of the Camino full application to the folder we're working on (the one containing pkg_make.sh)

Extracting content
- Run the pkg_make.sh script against the localized Camino.app: 1) open the Terminal application; 2) cd to the folder where you have Camino.app and the pkg_make.sh script; 3) type sh pkg_make.sh
- Move, trash or rename the Camino application
- Now you should have a new subfolder in your working folder, named Camino_app; check that it contains all the resources related to the language you are working on
- Rename the subfolder to Camino.app; after answering positively to a dialog, the folder appears now with the icon of a generic application
- Put the Camino.app extracted from the localized package inside the Content subfolder

Package making

Instructions for Package Maker available with Mac OS 10.3 Developer Tools
- Launch PackageMaker (usually found in /Developer/Applications/Utilities/)
- In the "Description" tab that pops up first, write a title for your package: feel free to use your language, if you wish
- In the "Files" tab, select the "Content" subfolder of your working folder and keep "Compress Archive" checked
- In the "Resources" tab, select the "Resources" subfolder of your working folder
- In the "Info" tab: Default Location: /Applications; Post-Install Action: No Restart Required; Authorization Action: Root Authorization; Flags: check only "Relocatable" and leave others unchecked
- In the "Version" tab, write the information you wish: they're not vital for the package to work correctly
- Before proceeding, make sure you save the document, so that you won't have to re-enter information next time you build a package; we suggest that you save the document inside your working folder
- Select the File > Create Package menu item; choose a file name for your package and save it (as usual, we suggest to use your working folder as a container for all things packaging); the file name shouold follow this schema: Camino-[version#]_[lang-code].pkg (i.e. Camino-0.8.4_it.pkg or Camino-0.9a1_zh-tw_zh-cn.pkg)
- You should get a confirmation dialog about succesful package creation

Instructions for Package Maker available with Mac OS 10.4 Developer Tools
- Launch PackageMaker (usually found in /Developer/Applications/Utilities/)
- Choose "Single Package Project" and click OK
- In the Contents tab, Choose your package folder (the top folder, containing the pkg_make.sh script)
- In the Configuration tab, choose "Root" as authentication method, "None" as Post-Install Action, and check the checkbox titled "Relocatable" (leave all other checkboxes unchecked).
- In the Scripts tab, choose your Resources folder.
- In the "Version" tab, write the information you wish: they're not vital for the package to work correctly
- Choose "Build..." from the Project-menu

- Compress the package using the built-in OS X archiver or any other applications that creates ZIP files

Now you're ready to upload your package or send it to the CaminoL10n project mantainers. The compressed archive should weight several hundreds of KB, making it a better choice than distributing the full Camino application.