[deepamehta-devel] Translations DM-style

[Malte Reissig]

Hi Juergen,

one hint regarding "putting high demand on the editors" and translations 
"alos being a demand in another project":

The approach i referenced yesterday (see below, modelling multi-lingual 
values as part of a topic's type definition) has one advantage over the 
one which introduces custom associations manually maintained by editors 
(if that is what you went for):

The advantage is that all translated values are here part of //one// 
page form. Furthermore your editors will not need to take care about 
creating any association manually to connect/hook up various 
translations to a topic (since the core would). This way your 
translations can be added or updated (using the dm4-webclient) through 
(only) editing the topic to be translated.

The only disadvantage (maybe neglectable - i dont know) is: If you plan 
to have many (say 50 or more) translations for a topic performance will 
become an issue in some cases. This is due to the fact that the core API 
does (currently) not provide a method to load a specific translation 
value (modelled as child topic) without loading all of the topics childs 
first.

Meaning, in practice, when for example generating a list of contents - 
displaying labels from a specific translation - performance will 
decrease (in relation to the amount of translations stored in each of 
the list's topics).

Regarding your suggestion. Maybe i can find some time at the end of the 
holiday season (towards nye) and give the "multilingual property" 
approach a go but i can certainly not promise you anything, so please do 
not plan with it. Therefore, just one question: What is the name of the 
topic type to be translated in the TAZ project?

Greetings!

On 15.12.2016 12:03, Juergen Neumann wrote:
>>> > > > >Has anyone done something similar and can share the approach?
>> > > >You can find a multi-lingual topic type definition here:
>> > > >https://github.com/mukil/dm4-wikidata-toolkit/blob/master/src/mai
>> > > >n/resources/migrations/migration3.json
>> > > >
> > >Ok, I'll study this approach.


On 15.12.2016 12:03, Juergen Neumann wrote:
> Hi Malte,
>
> I totally agree (and recently face!) that the way we provide the
> language issue in the gamechangers project puts a high demand on the
> editors. Wouldn't you want to write a small multi-laguage plugin on the
> poperties level as you are suggesting it, as I think we will really
> need it on the longer term. It's also a demand for the TAZ project, so
> time is a bit crucial here. :)
>
> Waht do you say?
>
> Thx,
>
> JuergeN
-------------- n�chster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: <http://lists.deepamehta.de/pipermail/devel-lists.deepamehta.de/attachments/20161216/14975f2c/attachment.html>