Introduce translation of files

[pgampe (Philipp Gampe)]

One thing came to mind while reading Frans comment: The driver should be actually be able to detect a language variant and report that information to the storage during indexing, e.g for the local driver this could mean that de.foo.txt is the german variant of foo.txt.

[minifranske (Frans Saris)]

Philipp the issue is that the driver doesn’t know the language. The same as it doesn’t know anything of the other metadata we keep in sys_file_metadata. It basically only knows the values we store in sys_file.

Relying on a file prefix doesn’t really sound like a solid solution. What if the editor changes the filename etc.

I don’t think we need to have a automagic solution here. Just give the editor an option to set the contents_language and the related file

[pgampe (Philipp Gampe)]

Philipp the issue is that the driver doesn’t know the language. The same as it doesn’t know anything of the other metadata we keep in sys_file_metadata. It basically only knows the values we store in sys_file.

Well, the driver creates the information in sys_file. It and only it can provide any information about the file. I do not say that the driver needs to provide this information, but - depending on the storage - it might have that information at hand (e.g. knows about variants, etc).

I don’t think we need to have a automagic solution here. Just give the editor an option to set the contents_language and the related file

That is to error prone. Editors will forget it half of the time and it requires manual intervention, therefore troubling any automated process.

[liayn (Markus Klein)]

Another big obstacle I saw back then (and still do now) was with multi-tree sites, where each individual language tree uses sys_language 0. If we still use sys_language records for all of the file languages, how do we match them to the individual trees? FE rendering only uses sys_language 0 in this case

This is indeed a major issue. We ran into the same problem already with custom records as well, where those should have been shared across trees with different default languages => not possible.

[liayn (Markus Klein)]

Well, the driver creates the information in sys_file. It and only it can provide any information about the file. I do not say that the driver needs to provide this information, but - depending on the storage - it might have that information at hand (e.g. knows about variants, etc).

I disagree having any magic involved here. Iff the driver has more info (eg from a cdn or cloud’ish storage) it should of course provide this metadata, but it must never make any conclusion. (unless you write a driver that is specifically tailored to a use case where a language can be detected due to a pattern in the filenames)

[liayn (Markus Klein)]

The big listing of @minifranske reads quite good, yet I’m missing the hard implementation details, specifically when it comes to the relation with sys_file_reference which is again translatable.
Please also write down the specifics you envision in this regard.
Thanks.