Hi all,
today I updated all the translation files to match the Plone 3.0 release
candidate 1 state.
For Archetypes and ATContentTypes there have been only about three or
four new messages each, but in the Plone domain we have around 60 new
messages and about 30 removals. The other files have seen no changes.
I also did one major update that was one my list for some time: We use
certain HTML entites like — (a longer dash) and … (a
horizontal ellipsis) in the Plone templates. So far these have been
replaced by a simple dash and three dots in the translation templates,
in order for you not having to handle any of those entities. As a
general rule we try to avoid any HTML as much as possible in the
translation files.
Starting today instead of substituting these entities with simple
characters we use proper Unicode characters which preserve the special
meaning of these two entities:
— is now — instead of -
… is now … instead of ...
This update has set another 60 messages in your translation to fuzzy
status. You can simply review those by searching for the above two
characters and decide if you want to keep the simple ASCII characters or
use the proper Unicode symbols. Simply delete the #, fuzzy line for
those where you want to keep the old translation.
This change also forced me to update some files to use an UTF-8 encoding
instead of some variants of ISO-8859-* as the above characters have no
representation in those encodings.
If you have any questions about this, please don't hesitate to ask.
Hanno
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/_______________________________________________
Plone-i18n mailing list
Plone-i18n@...
https://lists.sourceforge.net/lists/listinfo/plone-i18n
