bodington-developers

[Bodington-developers] Resource localisation code - in or out?

[Alistair Y. <ali...@sm...>]

ok folks, vote time again.

org.bodington.i18n handles template localisation, though it also handles
Resource localisation too.

There's unease about Resource localisation, so should the code come out,
or stay and allow people who want to translate Resources to do so?
Removing it won't affect template localisation.

i18n was always going to be a pig to retrofit and the tools aren't covere=
d
by it. The most important one I can think of is the questionnaire tool,
which can't be localised.

Facility hasn't been touched as it's a massive effort requiring all hands
on deck.

The obvious gain from removing it is the db schema stays the same. The
loss is you can't localise Resources. This could lead to the case where a
help building, for instance, has many physically separate localised
instances, rather than just one.

Resource 1i8n code - in or out?

in++

Alistair


--=20
Alistair Young
Senior Software Engineer
UHI@Sabhal M=F2r Ostaig
Isle of Skye
Scotland

Re: [Bodington-developers] Resource localisation code - in or out?

[Matthew B. <mat...@co...>]

Alistair Young wrote:
> ok folks, vote time again.
> 
> org.bodington.i18n handles template localisation, though it also handles
> Resource localisation too.
> 
> There's unease about Resource localisation, so should the code come out,
> or stay and allow people who want to translate Resources to do so?

If you think you can improve it then I'm not completely against it in 
the short term.

> Removing it won't affect template localisation.

Cool.

> i18n was always going to be a pig to retrofit and the tools aren't covered
> by it. The most important one I can think of is the questionnaire tool,
> which can't be localised.

I wonder if this might be the tip of the iceberg? The messaging room 
also uses BigStrings to store the posted messages.

> The obvious gain from removing it is the db schema stays the same. The
> loss is you can't localise Resources. This could lead to the case where a
> help building, for instance, has many physically separate localised
> instances, rather than just one.

My concern is that if it went into a release we would then have to 
support it in future versions.

> Resource 1i8n code - in or out?

-1

Although I am happy for it to stay in while it is worked on and 
improved. In its current state I don't think it is ready to go into a 
released version.

-- 
+--Matthew Buckett-----------------------------------------+
| VLE Developer, Learning Technologies Group               |
| Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/       |
+------------Computing Services, University of Oxford------+

Re: [Bodington-developers] Resource localisation code - in or out?

[Alistair Y. <ali...@sm...>]

> In its current state I don't think it is ready to go into a released 
> version
what sort of probs do you see with it Mathew? I can't really see how it 
can be improved without radically altering the db schema. As it is, the 
only alteration is the on-the-fly creation of language specific 
big_strings tables.

There was talk earlier of pulling all strings out of big_strings for 
mass translation to save time but that can't happen now as big_strings 
is a dump for all strings, not just system ones.

Alistair


On 11 May 2005, at 10:57, Matthew Buckett wrote:

> Alistair Young wrote:
>> ok folks, vote time again.
>> org.bodington.i18n handles template localisation, though it also 
>> handles
>> Resource localisation too.
>> There's unease about Resource localisation, so should the code come 
>> out,
>> or stay and allow people who want to translate Resources to do so?
>
> If you think you can improve it then I'm not completely against it in 
> the short term.
>
>> Removing it won't affect template localisation.
>
> Cool.
>
>> i18n was always going to be a pig to retrofit and the tools aren't 
>> covered
>> by it. The most important one I can think of is the questionnaire 
>> tool,
>> which can't be localised.
>
> I wonder if this might be the tip of the iceberg? The messaging room 
> also uses BigStrings to store the posted messages.
>
>> The obvious gain from removing it is the db schema stays the same. The
>> loss is you can't localise Resources. This could lead to the case 
>> where a
>> help building, for instance, has many physically separate localised
>> instances, rather than just one.
>
> My concern is that if it went into a release we would then have to 
> support it in future versions.
>
>> Resource 1i8n code - in or out?
>
> -1
>
> Although I am happy for it to stay in while it is worked on and 
> improved. In its current state I don't think it is ready to go into a 
> released version.
>
> -- 
> +--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

Re: [Bodington-developers] Resource localisation code - in or out?

[Matthew B. <mat...@co...>]

Alistair Young wrote:
>> In its current state I don't think it is ready to go into a released 
>> version
> 
> what sort of probs do you see with it Mathew? I can't really see how it 
> can be improved without radically altering the db schema.

How would you implement it if you were to change the DB schema?

 > As it is, the
> only alteration is the on-the-fly creation of language specific 
> big_strings tables.

I see the synchronization problems between languages when one language 
changes.

The problems might occur with some resources that use big strings for 
user data.

> There was talk earlier of pulling all strings out of big_strings for 
> mass translation to save time but that can't happen now as big_strings 
> is a dump for all strings, not just system ones.

I wasn't aware of this. Did you imagine this being done after a clean 
install?

-- 
+--Matthew Buckett-----------------------------------------+
| VLE Developer, Learning Technologies Group               |
| Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/       |
+------------Computing Services, University of Oxford------+

RE: [Bodington-developers] Resource localisation code - in or out?

[Adam M. <ada...@co...>]

Are we not biting off too much here for 2.6?  We're on a tight timescale
already?? 

adam

--
Adam Marshall:       OUCS, 13, Banbury Rd. Oxford OX2 6NN.
Shameless plug:      Use the Bodington VLE http://bodington.org
Blog:                http://ramble.oucs.ox.ac.uk/blog/adamm/
Cheese of the month: Cheshire (not to be underestimated) 

| -----Original Message-----
| From: bod...@li... [mailto:bodington-
| dev...@li...] On Behalf Of Alistair Young
| Sent: 11 May 2005 11:30
| To: Matthew Buckett
| Cc: Bodington Developers
| Subject: Re: [Bodington-developers] Resource localisation code - in or
| out?
| 
| > In its current state I don't think it is ready to go into a released
| > version
| what sort of probs do you see with it Mathew? I can't really see how it
| can be improved without radically altering the db schema. As it is, the
| only alteration is the on-the-fly creation of language specific
| big_strings tables.
| 
| There was talk earlier of pulling all strings out of big_strings for
| mass translation to save time but that can't happen now as big_strings
| is a dump for all strings, not just system ones.
| 
| Alistair
| 
| 
| On 11 May 2005, at 10:57, Matthew Buckett wrote:
| 
| > Alistair Young wrote:
| >> ok folks, vote time again.
| >> org.bodington.i18n handles template localisation, though it also
| >> handles
| >> Resource localisation too.
| >> There's unease about Resource localisation, so should the code come
| >> out,
| >> or stay and allow people who want to translate Resources to do so?
| >
| > If you think you can improve it then I'm not completely against it in
| > the short term.
| >
| >> Removing it won't affect template localisation.
| >
| > Cool.
| >
| >> i18n was always going to be a pig to retrofit and the tools aren't
| >> covered
| >> by it. The most important one I can think of is the questionnaire
| >> tool,
| >> which can't be localised.
| >
| > I wonder if this might be the tip of the iceberg? The messaging room
| > also uses BigStrings to store the posted messages.
| >
| >> The obvious gain from removing it is the db schema stays the same. The
| >> loss is you can't localise Resources. This could lead to the case
| >> where a
| >> help building, for instance, has many physically separate localised
| >> instances, rather than just one.
| >
| > My concern is that if it went into a release we would then have to
| > support it in future versions.
| >
| >> Resource 1i8n code - in or out?
| >
| > -1
| >
| > Although I am happy for it to stay in while it is worked on and
| > improved. In its current state I don't think it is ready to go into a
| > released version.
| >
| > --
| > +--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