String translation

[Hugues Boily]

Hi Colin,

I am done - see attached.

Cheers,
Hugues

Colin Clark wrote:
> Hi Hugues,
>
> We've pretty much wrapped up all the internationalization work for each screen in Engage 0.3. Just about all the user-visible strings in the app have been moved into language bundles, and are ready to be translated. The few exceptions are the Artifact View page, My Collection, and the alt text for the Navigation Bar. We're working on these today.
>
> Jess kindly put together a document with a list of all the strings that need to be translated. She rightly describes the work as a "matching game." In short, you just need to look at the English strings in Jess' file and specify their French equivalents. In several cases, some of us have used our awkward grade school French to do a rough translation. Hopefully you will find it suitably amusing.
>
> All our string bundles are formatted as JSON, so they take following form: 
>
>  * Quotation marks around all keys and values. 
>  * Colons separate keys from values. 
>  * String template tokens start with %, and should remain in English--they'll be replaced with values from the model.
>
> Here's an example:
>
> {
>     "categoryHeader": "Upcoming (%size)",
>     "title": "Exhibitions"
> }
>
> I think the easiest process is for you to fire this document back to us with the French translations, and we'll make sure the end up in the correct files within the Engage source package.
>
> Let me know if you need a hand with any of this,
>
> Colin
>
>   

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Engage-03-Strings_HUGUES.txt
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20100205/3c4834b3/attachment.txt>