|
Subject: Re: docs content Newsgroups: gmane.comp.web.zope.plone.devel Date: 2004-06-04 11:07:38 GMT (4 years, 13 weeks, 3 days, 20 hours and 51 minutes ago)
Milos Prudek wrote:
> >> 1)
> >>
> >> First of all, I want to write what YOU think is a good material. So
> >> you tell me what YOU want to have in it. In no particular order.
> >> Putting it in order is my job.
>
> Can someone post answer to the question above? I'd like to have some
> consensus on this.
>
Well, since I recall that it took me a while to get that,
I suggest you try hard to get the big picture right from the
onset because there are a few things that can easily be confused:
1. User interface versus content
2. Fixed language sites (but maybe different from English)
versus multilingual sites
3. The user's perspective versus the admin's perspective versus
the developer's perspective (and here: coders versus translators)
Details
* Out-of-the-box Plone "only" supports a localizable user
interface (the button and tab labels, (help) messages,
standard dialogs, some docs).
To support CONTENT in DIFFERENT languages further actions
have to be taken (explain, e.g., the language tool and
how to use it to set the default language to soemthing
other than English and how to restrict the set of languages
offered to the users to choose from. Then point out that
something like i18n layer/folder is needed to support
multilingual content).
* Users of Plone sites shouldn't worry at all except when the
site's content is multilingual. Then they need to know how to provide
there own contributions such that it's OK with the different
languages supported.
* For admins just stress again that there is a difference between
a site using a language other than English and sites that are
multilingual.
I would also note how to set these up respectively, e.g., using
an access rule or the language tool for the first case but adding
i18n layer/folder for the second.
* for coders I would list and explain the 'dos' and 'don'ts' as
outlined in the plone.org/i18n section
* Then you can dive readily into the details including techicalities
underlying the different translation approaches.
* for developers: I'm not really into this business myself.
The i18n support for CMFBibliographyAT (my most advanced product
so far) was initiated by David Convent.
I still have no clue what so ever how to generate a .pot file
(i.e., how to get started).
I do know how to generate a .po file from there but I don't know
how to keep .pot and .po files in sync when things develop/expand.
I only very briefly looked at KBable and almost immediately decided
to stay with emacs and to do everything by hand (which cannot be the
right thing
|
|
|