[Pkg-mozext-commits] [perspectives-extension] 10/44: LOCALIZATION - Convert file to markdown formatting

Sat Jun 6 02:55:27 UTC 2015

This is an automated email from the git hooks/post-receive script.

taffit pushed a commit to branch master
in repository perspectives-extension.

commit 14f5265c216ee8798da2325f4e8f8231cd3219c9
Author: Dave Schaefer <dave.schaefer at gmail.com>
Date:   Sun Nov 2 16:02:53 2014 -0700

    LOCALIZATION - Convert file to markdown formatting
---
 LOCALIZATION    | 86 ---------------------------------------------------------
 LOCALIZATION.md | 82 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 82 insertions(+), 86 deletions(-)

diff --git a/LOCALIZATION b/LOCALIZATION
deleted file mode 100644
index 18d1e1f..0000000
--- a/LOCALIZATION
+++ /dev/null
@@ -1,86 +0,0 @@
-You want to help us translate Perspectives? AWESOME! :D
-
-We're willing to work with you to make translation as easy as possible. Here are some options for how you can help translate Perspectives:
-
-
-
-1. Create an account on Babelzilla:
-
-* http://www.babelzilla.org
-
-- Visit the Perspectives WTS page
-
-* http://www.babelzilla.org/index.php?option=com_wts&extension=5614&type=show
-
-- Sign up for your language and use the Babelzilla tools to translate!
-
-There is also a Babelzilla thread for Perspectives in case you have questions: http://www.babelzilla.org/forum/index.php?showtopic=7172&st=0
-Or feel free to email the dev list.
-
-
-2. Fork the Perspectives project on GitHub ( https://github.com/danwent/Perspectives ), translate, and send us a pull request.
-
-The steps to translate are:
-
-- Create a new folder in plugin/chrome/locale
-- Copy over the .dtd and .properties files from the en-US (or any other) locale
-- Translate the strings inside each of those files
-
-Then push back to Github and send us a pull request. We'll take care of the rest!
-
-
-3. View the strings at https://github.com/danwent/Perspectives/tree/master/plugin/chrome/locale/en-US and email us your translations. We can use them to create a new locale.
-
-
-4. Other - prefer to work via IM? Encrypted email? Carrier pidgeon? Just let us know on the mailing list https://groups.google.com/group/perspectives-dev and we can help ;)
-
-
-
--------
-
-Useful Links
-
-* List of recognized Firefox locales:
-
-https://wiki.mozilla.org/L10n:Teams
-
-
-* MDN guide to Localization:
-
-https://developer.mozilla.org/en/Localization
-(or change the URL for your language)
-
-* How to test locales
-
-http://www.babelzilla.org/forum/index.php?showtopic=1384
-
-(and see test/Testing Localizations.txt in the Perspectives git)
-
-
-
-
--------
-
-For developers:
-
-Steps to remember when publishing a new localization:
-
-0. Make sure all .properties and .dtd files are saved as UTF-8 with no BOM. Otherwise many things fail horribly.
-
-1. Before publishing a release, register the new locale inside chrome.manifest. e.g.
-	locale perspectives fr chrome/locale/fr/
-
-don't forget the trailing slash!
-
-2. Write a line for the locale in the install.rdf:
-	<locale> perspectives/locale/fr-FR/</locale>
-
-adding a <Description> block with a <em:translator>translator name</em:translator> credit is a good thing. Also nicely ask your translator to translate the 'description' and 'creator' fields.
-
-3. Make sure to save the file as as UNIX/UTF-8 encoding.
-
-4. Add a credit inside the AUTHORS file (or a credit to 'anonymous', if the translator prefers)
-
-
-
-
diff --git a/LOCALIZATION.md b/LOCALIZATION.md
new file mode 100644
index 0000000..3651a65
--- /dev/null
+++ b/LOCALIZATION.md
@@ -0,0 +1,82 @@
+# Translating Perspectives
+
+Do you speak a language other than English? Are you willing to donate some time translating English sentences? **Great!**
+
+Perspectives needs both:
+* Translations to new languages
+* Translating English that remains in the current languages
+
+We're willing to work with you to make translation as easy as possible. Here are some options for how you can help translate Perspectives.
+
+
+
+##Options for translating
+
+### Use Babelzilla:
+
+1. Sign up at http://www.babelzilla.org
+2. [Visit the Perspectives WTS page](http://www.babelzilla.org/index.php?option=com_wts&extension=5614&type=show)
+3. Sign up for your language and use the Babelzilla tools to translate!
+
+If you have questions:
+* [Email us on the Perspectives mailing list](https://groups.google.com/group/perspectives-dev)
+* Or post in the [Babelzilla Perspectives thread](http://www.babelzilla.org/forum/index.php?showtopic=7172&st=0)
+
+
+### Use GitHub
+
+1. Fork the [Perspectives project on GitHub](https://github.com/danwent/Perspectives):
+	1. Sign in to GitHub
+	2. Click the 'Fork' button in the top right
+2. Edit the translation files inside [plugin/chrome/locale](plugin/chrome/locale):
+	1. If needed, create a new folder in plugin/chrome/locale and copy over the ```.dtd``` and ```.properties``` files from the en-US locale
+	3. Translate the strings inside each file
+3. Send a pull request
+
+
+### Use email
+
+1. [View the strings on GitHub](https://github.com/danwent/Perspectives/tree/master/plugin/chrome/locale/en-US) and email us your translations. We can use them to create a new locale.
+
+
+### Other
+
+Prefer to work via IM? Encrypted email? Carrier pidgeon? Just [let us know](https://groups.google.com/group/perspectives-dev) and we can help!
+
+
+##Useful Links
+
+* [List of recognized Firefox locales](https://wiki.mozilla.org/L10n:Teams)
+* [Mozilla Developer Guide to Localization](https://developer.mozilla.org/en/Localization) (or change the URL for your language)
+* [How to test locales](http://www.babelzilla.org/forum/index.php?showtopic=1384) (and see ```test/Testing Localizations.txt``` in the Perspectives git)
+
+## Questions
+
+If you have any questions please [email us and ask](https://groups.google.com/group/perspectives-dev).
+
+
+-------
+
+## For Perspectives developers:
+
+###How to publish a new localization
+
+0. Make sure all ```.dtd``` and ```.properties``` files are saved as UTF-8 with no BOM. Otherwise many things fail horribly. The python unit tests should detect this and fail any builds that don't match, so be sure to install python.
+
+1. Before publishing a release, register the new locale inside ```chrome.manifest```. e.g.
+
+ ```locale perspectives fr chrome/locale/fr/```
+
+ Don't forget the trailing slash!
+
+2. Write a line for the locale inside ```install.rdf```:
+
+ ```<locale> perspectives/locale/fr-FR/</locale>```
+
+ Adding a ```<Description>``` block with a ```<em:translator>translator name</em:translator>``` credit is a good thing.
+Also ask your translator nicely to translate the 'description' and 'creator' fields.
+
+3. Make sure to save the file as as UNIX/UTF-8 encoding.
+
+4. Add a credit inside ```plugin/chrome/content/credits/translators.txt``` (or a credit to 'anonymous', if the translator prefers)
+

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-mozext/perspectives-extension.git

