Hi.
I just converted my test-site from Localizer to
PlacelessTranslationService and found the little build.sh very useful.
But I am using Windows. So I put together a little build.bat doing the
same thing as build.sh. I thought it might be useful for somebody else.
I've tested it only on WinXP but I think it should also run on Win2k.
Greetings Hanno Schlichting
content of build.bat:
@echo off
dir /B *.po > trans.txt
for /F "tokens=1,* delims=. " %%i in (trans.txt) do (
echo Input: %%i.%%j
echo Output: %%i.mo
msgfmt %%i -o %%i.mo
)

Renaud Pacalet wrote:
> Hello ploneers,
>
> I like plone. I love it. May I help for the French translation? It would
> be a real pleasure and a great honor.
Bienvenue à bord. :-)
You can join the french translation team on traduction@...
Sending a mail to sympa@... with subject "SUB traduction"
should work.
Limi : could you update the "existaing translations" page on plone.org
with the above adress for the french translation?
Regards,
--
Ronan

Hello ploneers,
I like plone. I love it. May I help for the French translation? It would
be a real pleasure and a great honor.
Best regards and many many thanks for all this nice and usefull job,
Renaud.
--
Renaud Pacalet, ENST, 46 rue Barrault 75634 Paris Cedex 13
###### Tel. : 01 45 81 78 08 | Fax : 01 45 80 40 36 ######
# Fight Spam! Join EuroCAUCE: http://www.euro.cauce.org/ #

I took the opportunity to write down some thoughts I've had recently on
supporting multilingual content in Plone - perhaps some of it is
interesting or useful enough to find its way into Plone.
This is written from a content provider perspective and is a bit of a
draft requirements list for maintaining a multilingual site with some or
all content translated. None of this is about how to actually code the
implementation.
There are many opportunities for misunderstandings due to use or abuse
of terminology. In the below draft, "document" is used loosely in its
everyday meaning.
Contents:
A. General
A.1. Support for multiple languages should be the default
A.2. Full support for RFC2616 content negotiation for languages
A.3. Supportive functionality - Add language support short list
A.4. Workflow for "Document needs updating/reviewing"
B. Translations, translating and maintaining translations
B.1. Source language for translation purposes
B.2. Update translations when source document changes
B.3. Simple translator aids
B.4. Coordinated publishing and withdrawal of original and translations
A. General
A.1. Support for multiple languages should be the default
The functionality of I18NLayer should be transparent to users and
provided by default (ie. no need to first add the I18NLayer). End-user
content writers shouldn't be exposed to the inner guts of Plone.
A.2. Full support for RFC2616 content negotiation for languages
Document language must be fully settable, including variants. Note that
this might include more than two levels. For example "en", "en-GB",
"sv-FI-Narpes".
http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.10http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.4
A.3. Supportive functionality - Add language support short list
Most sites will support only a few languages most of the time. Thus it
makes sense to put these languages on a configurable short list to be
used in the user interface to simplify and speed up working with content.
A.4. Workflow for "Document needs updating/reviewing"
Add begin-review and review-by attributes to documents, such that the
document enters an update/review workflow -- while the current version
is still being published -- at the begin-review date. The review-by is a
deadline when the review must be done (no effect on the site if not
ready on time).
B. Translations, translating and maintaining translations
B.1. Source language for translation purposes
It should be possible to mark one language variant of a document as the
source for translations to the other languages it is available in.
B.2. Update translations when source document changes
When the source language document is edited, translations made from the
source language should be marked as needing updating of the translation
(enter translation update workflow). It should be possible to view the
changes made in the source document. Possible use "document needs
updating/reviewing" workflow as specified in A.4. above.
B.3. Simple translator aids
1) Side by side view of source doucment and translation.
2) Multilingual dictionary tool.
B.4. Coordinated publishing and withdrawal of original and translations
Need marker for when a translation is completed and ready to be
published; if attempting to publish the document and translations and
there are unfinished translations the user should be warned that not all
material is ready. If the user chooses to continue to publish anyway,
only completed translations should be published. Publishing and
withdrawal should be simultaneous for all (completed) translations of a
document.
--
Leonard Norrgard
leonard.norrgard@...

I took the opportunity to write down some thoughts I've had recently on
supporting multilingual content in Plone - perhaps some of it is
interesting or useful enough to find its way into Plone.
This is written from a content provider perspective and is a bit of a
draft requirements list for maintaining a multilingual site with some or
all content translated. None of this is about how to actually code the
implementation.
There are many opportunities for misunderstandings due to use or abuse
of terminology. In the below draft, "document" is used loosely in its
everyday meaning.
Contents:
A. General
A.1. Support for multiple languages should be the default
A.2. Full support for RFC2616 content negotiation for languages
A.3. Supportive functionality - Add language support short list
A.4. Workflow for "Document needs updating/reviewing"
B. Translations, translating and maintaining translations
B.1. Source language for translation purposes
B.2. Update translations when source document changes
B.3. Simple translator aids
B.4. Coordinated publishing and withdrawal of original and translations
A. General
A.1. Support for multiple languages should be the default
The functionality of I18NLayer should be transparent to users and
provided by default (ie. no need to first add the I18NLayer). End-user
content writers shouldn't be exposed to the inner guts of Plone.
A.2. Full support for RFC2616 content negotiation for languages
Document language must be fully settable, including variants. Note that
this might include more than two levels. For example "en", "en-GB",
"sv-FI-Narpes".
http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.10http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.4
A.3. Supportive functionality - Add language support short list
Most sites will support only a few languages most of the time. Thus it
makes sense to put these languages on a configurable short list to be
used in the user interface to simplify and speed up working with content.
A.4. Workflow for "Document needs updating/reviewing"
Add begin-review and review-by attributes to documents, such that the
document enters an update/review workflow -- while the current version
is still being published -- at the begin-review date. The review-by is a
deadline when the review must be done (no effect on the site if not
ready on time).
B. Translations, translating and maintaining translations
B.1. Source language for translation purposes
It should be possible to mark one language variant of a document as the
source for translations to the other languages it is available in.
B.2. Update translations when source document changes
When the source language document is edited, translations made from the
source language should be marked as needing updating of the translation
(enter translation update workflow). It should be possible to view the
changes made in the source document. Possible use "document needs
updating/reviewing" workflow as specified in A.4. above.
B.3. Simple translator aids
1) Side by side view of source doucment and translation.
2) Multilingual dictionary tool.
B.4. Coordinated publishing and withdrawal of original and translations
Need marker for when a translation is completed and ready to be
published; if attempting to publish the document and translations and
there are unfinished translations the user should be warned that not all
material is ready. If the user chooses to continue to publish anyway,
only completed translations should be published. Publishing and
withdrawal should be simultaneous for all (completed) translations of a
document.
--
Leonard Norrgard
Tel.: +358-400-434808
Email: leonard.norrgard@...

On Tuesday 26 August à 01:04, Alexander Limi · Plone Solutions wrote:
> Hi,
>
> We would like to arrange a meeting on IRC to discuss the implementation of
> multilingual content in Plone and the CMF with some of the experienced
> multilingual developers in the Zope world.
>
> The meeting is scheduled at 18:00 Paris time this Wednesday the 27th of
> August on the #plone IRC channel on irc.freenode.net.
Unfortunatly I'll not possible for me to be there :( I'm living today
for one week of holidays and won't have access to irc there. I'll
register to the plone-i18n mailing-list and looking for your summary
there when I'll be back.
regards
--
Sylvain Thénault LOGILAB, Paris (France).
http://www.logilab.comhttp://www.logilab.frhttp://www.logilab.org

Hi,
We would like to arrange a meeting on IRC to discuss the implementation o=
f=20
multilingual content in Plone and the CMF with some of the experienced=20
multilingual developers in the Zope world.
The meeting is scheduled at 18:00 Paris time this Wednesday the 27th of=20
August on the #plone IRC channel on irc.freenode.net.
Check your local time here: http://tinyurl.com/l5wv
The meeting will discuss multilingual content types and how they should b=
e=20
implemented. The goal is to discuss alternative implementation approaches=
,=20
come up with a plan for development that people are happy with - and=20
ultimately set some goals for development, so everybody can start pulling=
=20
in the same direction. :)
Explicitly invited are the following people:
- Sylvain Th=E9nault from Logilab (France)
- Simon Eisenmann from Struktur (Germany)
- Lalo Martins (Brazil) - Kapil Thangavelu (USA)
- Pierre-Julien Grizel from Ingeniweb (France)
- Florent Guillaume from Nuxeo (France)
- Alexander Limi, Helge Tesdal and Geir B=E6kholt from Plone Solutions=20
(Norway)
We would like to invite any interested parties to join the conversation,=20
and would especially welcome participants from Japanese, Chinese, Thai,=20
Korean and Arabic-speaking countries.
The follow-up discussions will be held on the plone-i18n mailing list, an=
d=20
a summary of the meeting will be posted online.
We hope you have time to join us, and look forward to seeing you there.
--=20
__________________________________________________________________
Alexander Limi =B7 Interaction Architect =B7 Plone Solutions
Plone Co-Founder =B7 http://plone.org =B7 Connecting Content
Development =B7 Training =B7 Support =B7 http://www.plonesolutions.com
__________________________________________________________________

WayneDon Krebs32692003-08-21T16:37:00Z2003-06-03T21:34:00Z2003-08-21T16:37:00Z12201256EN5 Systems Corp.10215429.3821
Bankruptcy Filings Great Marketing Lists
People who have filed bankruptcy begin almost immediately to try to re-establish themselves. They are debt-free and not likely to file again for seven years. Opportunities to profitably market to this group exist for virtually every product and service area including:
· Automotive
· Secured and unsecured credit cards
· Mortgages and home equity loans
· Furniture and Household items
· Consumer Lending
Lists We Provide
Publicrecord information directly from Bankruptcy Court files
Filings,discharges, and closed cases as late as the last 24 hours
NationalCoverage
Zipand state selects
Deliveryvia FTP, Email,
Do your Own List with our Daily Bankruptcy Report Software and SAVE
· For almost all courts
· For any date range, and settable to run unattended
· Retrieves filers data, judge, trustee, attorney and creditor matrix data as desired.
· Loads all data into a MSSQL database ready to use for account suppression, marketing, etc.
· Use companion Query Program to view, count, and/or export data to a file.
· See our website at http://www.dailybankruptcyreport.com
Call 1-866-476-2495 for quote or Email us. Great Prices .
Daily Bankruptcy Reports Serving Bankruptcy Data Customers for over 20 years
102 Highway 87 North Comfort, TX. 78013 830-995-3091 866-476-2495
To be removed from our database click Remove Me

Hi Jakub,
Jakub Kasprzycki wrote:
> Hello,
> I would like to join the Plone Translation Team.
> I am from Poland and speak polish.
this is quite easy ;-) as i wrote earlier:
are you familiar on how to translate plone?
this document might be useful:
http://plone.org/development/i18n/translators-guidelines
in the case of the polish language currently Radoslaw Stachowiak
(http://plone.org/development/i18n/existing-translations) did a first
translation. it would be great if you can proof-read the current
translation and add missing strings to the po file.
best regards
jodok
--
jodok batlogg
solution2u.net gmbh . hof 4 . a-6861 alberschwende
fon +43 5579 85777-65 . fax -77 . mobil +43 699 11841546
http://solution2u.net/ . batlogg(at)solution2u(dot)net
have a nice day

hi keng-ly,
UnCertificate UnKnow wrote:
> Dear plone-i18n@...,
>
> My name Keng-ly from Thailand. I want to translate Plone from English to
> Thai language.
as i wrote earlier:
if you are not familiar on how to translate plone,
this document might be useful:
http://plone.org/development/i18n/translators-guidelines
in the case of the thai language there is no translation yet.
(http://plone.org/development/i18n/existing-translations)
just take the .pot template for your translation and start ;-)
contact the mailinglist if you like to integrate your translation to the cvs
tree.
thanks!
jodok
--
jodok batlogg
solution2u.net gmbh . hof 4 . a-6861 alberschwende
fon +43 5579 85777-65 . fax -77 . mobil +43 699 11841546
http://solution2u.net/ . batlogg(at)solution2u(dot)net
have a nice day

Dear plone-i18n@...,
My name Keng-ly from Thailand. I want to translate Plone from English to Thai language.
Thanks/BRgds,
Keng-Ly
---------------------------------
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.

Hi,
I've scheduled a localisation / i18n talk for the Plone Conference, but
haven't yet found anyone wanting to talk about it. We are looking for
someone to talk about how to setup up i18n, use it in Plone, do
translations and real world lessons learned.
i18n is of huge importance to Plone and it would be a shame not to have
this reflected in the conference. A talk will get you into the
conference for free, get a t-shirt and even a free drink from me.
If you are interested please email me or conference1@...
Thanks.
--
Andy McKay
http://www.agmweb.ca

Hi,
We intend using Plone soon for some South African community sites.
Country code = za.
Tickbox Technologies want to become custodian of the translation of
Plone in Afrikaans.
--
Alida Delport
Tickbox Technologies
Cape Town
http://tickbox.co.za
e-mail: alida@...
Cell: +27-(0)83-628-2479