[TYPO3-dam] DAM & multilinguism

[Achim Eichhorn]

Hello Laurent,

first of all, I am sorry, that I don't have a solution to your special 
problem,
but I think, it is related to a problem, I posted a few weeks ago
and I think it should considered together.

So far I understand, DAM localization is build on typo3 standard 
localization
features. Somewhere in  Rene's docs you can find which fields can be 
localized, and which fields
will be the same for every language. So there is one record for the standard 
language and for
each trnaslated! record another localzed record, which has a pointer to his 
parent.

... I will now repeat our problem in short, perhaps there is a way to to 
bring this all together
and produce a common sollution... ?

1. Situatuion:
Our customer has a database with about 3000 pictures, every year there will 
be approx
150-500  new pictures. This pictures are stored in DAM in different folders 
300, 150 and 72 dpi.
Addionaly we have got a csv-file, which holds for each picture localized 
meta data in four languages.
Indexing should be done in one step!

2. We are using DAM file module for indexing and are currently implementing 
a module
which can scan the csv-file for an specific asset file and then we are 
adding the additinal
meta data to the record for this specific file (this will be done during 
standard indexing,
Rene has described this already...)

But our problem is:

3. What is the standard way during DAM indexing for creating multi-language 
Meta Data?
Currently we are only creating records for the standard language (in our 
case german),
but what would be the way to create the other language records?

I thinkt we should forulate exactly, wha we need:
my needs would be:

1. An API for multi lingual indexing of DAM. Assets. (And a common way, how 
to index multlingual content...)
2. Translation of categories (to tell the truth, I was not aware of this 
'til you mentioned it..!)

Perhaps you could express your needs in such short sentences, too?
I think this would be a good initial point for starting a discussion about 
changing the DAM.


Greetings Achim.





"Laurent Verhoest" <Laurent.Verhoest at advoo.fr> schrieb im Newsbeitrag 
news:mailman.7349.1156191228.24118.typo3-project-dam at lists.netfielders.de...
> Hi all,
>
> I have a problem on an internal project using the DAM in several langages 
> and here are my thoughts (long mail following, sorry for the long read, 
> especially if this issue has already been discussed).
>
> I know you can create a 'translated' record of a DAM object cheating with 
> the 'alternate langage page' of the "Media" root. But you can only 
> translate part of the metadata (like title, desc and so on)
>
> That's ok for me not to translate everything in the metadata, but there 
> are 2 pb (imho) :
> - first : you can't change the file (physical on disk) itself ! If i 
> happen to publish a pdf in english, and then its translated version in 
> french, i would like to change the real file people will download. That's 
> currently impossible because the "File" section (when editing metadata) is 
> readonly (and related data for the translated record in tx_dam is empty).
> - second : DAM categories can't be translated :-((
>
>
> I think first pb could be solved because in the DB, all fields exists to 
> change the file & path and that way we keep the link between a file and 
> its translated version.
> I have tried to work around the first pb by cheating the config of fields 
> and set them writable. But it's not much worth because i can only type a 
> filename and a path, ican't upload the real file (except via direct ftp, 
> but that's cheating and not the way my users would work).
>
> One good thing would be to add a last action in the "File" section of the 
> metadata in order to replace the current file with a new one to be 
> uploaded.
> But there is another pb i think, it is that the Media>File view gets to 
> list file by reading the disk directory, not the database (maybe i missed 
> sth though). So files will be mixed up. Better presentation would be to 
> use the on in the Web>List view, where you can see the files and the link 
> between a file and its translated version (would need to add a column to 
> localize a file).
>
>
> For the second pb (multilingual categories), it would requiere a change in 
> DB as table tx_dam_cat doesn't handle multilang (adding the columns 
> sys_language_uid and l18n_parent), and modifying the BE to and a 
> translated version of a category.
> My idea would be to be that i add a english doc A and set it category to 
> C1. Then i create the translated version of doc A in french : it keeps the 
> link to cat C1, but if i log in the BE in french, i can see the French 
> version of cat C1, and if i search for it using cat C1, i find the version 
> in the current lang.
> (i don't know if all this last stuff is really clear...)
>
>
> What do you think about all this, and thanks for your help/advice ?
>
> Laurent