RE: [Bodington-developers] Localisation issue

[Colin T. <col...@co...>]

I agree with Matthew (I might even have nagged him into responding ;-)...

Although I can see that template internationalisation doesn't make a huge
difference to the UHI requirement, it seems odd to me to have the facility
to translate resources (especially when the translation can get out of synch
when the original is changed, as Matthew pointed out.) Is there no other
solution to the problem? Allowing the ability to tag/link a set of resources
which provide e.g. a help building, in multiple languages but only display
the one that uses the users chosen language?

I think we need to resolve any issues before (doing the Big Template
Shuffle) and releasing stuff... don't want to end up with a changed database
schema, etc that we're stuck with?


Colin

> -----Original Message-----
> From: bod...@li...
> [mailto:bod...@li...]On Behalf Of
> Alistair Young
> Sent: 10 May 2005 12:06
> To: Matthew Buckett
> Cc: Bodington Developers
> <bod...@li...> >>
> Bodington Developers
> Subject: Re: [Bodington-developers] Localisation issue
>
>
> it's in there now and it works so I'd say leave it. The reason it's
> there is not a lot changes when you change the language as all the
> Resource strings are in the db.
>
> We have help buildings etc which need to be translated to
> Gaelic. When
> you look at it, the templates don't provide much output when compared
> with the resources.
>
> There will be Resources which don't need localised, such as language
> specific content - no point translating a teach yourself
> Gaelic course
> to Russian but there will also be Resources that do need translated,
> such as help buildings, navigation etc. If a Resource is
> common to all
> users then it'll need translated.
>
> Alistair
>
>
> On 10 May 2005, at 11:58, Matthew Buckett wrote:
>
> > Alistair Young wrote:
> >> On my travels in qLand I found a potential problem with
> localisation.
> >> Questionnaire responses are stored in the big_strings table. I
> >> thought big_strings was for system entites, such as
> Resources, rather
> >> than user submitted data. Localising big_strings en masse via db
> >> extract and translator is now much more complicated.
> >
> > Although I am keen on Bodington having i18n (ability to
> translate the
> > templates and outputted messages) I don't see that being able to
> > localize the resources is a "big win". And some issues
> didn't seem to
> > get resolved:
> >
> > What happens if someone updates the English version of a
> resource? Do
> > you still display out of date translated version?
> >
> > Won't most installation be creating resources in their own locale?
> >
> > I think that the localization of resource is a aiming for a small
> > market and significantly complicates the Bodington codebase.
> >
> > --
> > +--Matthew Buckett-----------------------------------------+
> > | VLE Developer, Learning Technologies Group               |
> > | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/       |
> > +------------Computing Services, University of Oxford------+
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by Oracle Space Sweepstakes
> > Want to be the first software developer in space?
> > Enter now for the Oracle Space Sweepstakes!
> > http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
> > _______________________________________________
> > Bodington-developers mailing list
> > Bod...@li...
> > https://lists.sourceforge.net/lists/listinfo/bodington-developers
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
>