1) Content library, this should be a content item and assigned either
to multiple languages or a single language (e.g. english and spanish
versions both link to the english download as there is only one...
which we can then separate, or it defaults to english PDF if there is
no spanish version)
2)Depends what files.. if they are site images, then split them up as
images/EN , images/ES etc have one default language so if you dont
find a resource you can default to the english (for example) so not to
get broken links and errors
3) Accounts.. same repository.. add a preference for language
4) Workflow.. you should have workflow templates that you can use that
are held in the same place.. if you need something special add a
"Workflow for ES content" concept (with the right translation of
course! and make it available to users that are meant to use that
workflow
5) Template Libraries.. I would guess the same here.. are templates
available to all or to only languages? if they are available per
language tag it as so
Hope that helps
On Mon, 20 Sep 2004 11:10:16 +0200, Micha Schopman
<[EMAIL PROTECTED]> wrote:
> And does someone separate content library, file folders, accounts,
> workflow, approval queues, template libraries, etc. per language, or do
> all languages in the system use the same libraries?
>
> Micha Schopman
> Software Engineer
> Modern Media, Databankweg 12 M, 3821 AL Amersfoort
> Tel 033-4535377, Fax 033-4535388
> KvK Amersfoort 39081679, Rabo 39.48.05.380
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
