translate file itself in a file entity using Entity tranlsation

Have you enabled entity translation for file entities in the entity translation UI?

I have the same issue. Most fields on a file entity can be translated, however the file field cannot be translated.

Examples:

1) Say I upload an English video with an English title in the title field. I can add a Spanish title using entity translate but I can't add a Spanish video. I'd like to because the original video has language specific content.

2) A client wants to upload their annual report as a pdf in 2 different languages. At the moment they couldn't do this within 1 file entity as the media field doesn't offer translation.

Questions/thoughts:

1) Is this actually a Media module issue? After all it's a Media field that doesn't have the feature.
2) Are there ways around the problem? Perhaps, for example, all we need to do is have separate file entities for each language a file is in. I can see this being a problem on a file page. Say there was a page for an english language video; if the site visitor switched language on that page then the English video would still display. We could perhaps show links to other language videos via entity reference. Bit of a hack though.

Hmm my mistake: Actually it's not a Media field. I'm not sure what it is :(

Thanks for replying Sylvain!

I think you're totally right about the file being THE entity. I guess it represents an actual file, so it would be a bit odd to switch in another one.

I'm to have a go at doing it the old way as well. I've found this module: https://www.drupal.org/project/media_translation which does it that way. It's not well maintained though, so I think I'll have a bit of work to do!

Andrew

I am also very interested by that feature.

Did you make any progress ?

Thanks.

Hi enorniel,

In the end I ended up not linking the file translations at all. If a page is in say English editors pull in English files for display, If in French, editors pull in French files. The different translations of a file are not linked at all. It does mean a bit more work for editors, but it's the best I could come up with.

As discussed above I don't think it makes sense to have different translations of a file on a file entity, because a file entity represents a single file.

Thanks. But I should disagree on your conclusion.

There are some cases where a file should be completely translated in the same entity to be more efficiently processed by other mechanisms.

For instance, if a user wants to see the last Marvel: Avengers 2 on video stream website based on Drupal (officially of course), he wants certainly see it in his own language. He will use the search_api to look for it in the catalog. Maybe, that video will be spotlighted, its tags changed to display a promotional tag...

If the catalog has 10000 and more videos and the website is translated in 50 languages, just imagine how to manage that if a video is 50 bundles.

I know where you're coming from. But I still think file entity represents individual files.
For example (with file entity representing individual files), if you had a language field on file entity you could 'tag' each file with a language.
If you had multiple files within a file entity how would you do that? You would only have one language field. Would you create another entity for each file?
What I've done in another project, and I think what Sylvian did, was create another entity that can take multiple files. For example a Movie entity that you can attach multiple file entities to.

Do let me know if you find a better solution though! It'd be great if there was one.

I'm going to add a vote for translatable files, because I have exactly the issue where I am forced into a messy solution of creating a node wrapper in order to do this:
I want to have views (or search results) of media entities, but in some cases e.g. videos, these need to be in the user's language. I can't just add a language field, as not every file has a translation for every language and there would therefore not be the nice functionality of falling back to a default language where no translation exists - for example having a movie trailer in Spanish and English, I would want to show the English trailer for other languages - not to mention the loveliness of having a translate interface rather than uploading all the videos as separate items.

I agree in many projects a file entity should be a specific file. But if file entity was capable of translating the file field the choice would then be down to the developer for what is best for a project.

I'm using mediaelement.js to display videos. I'm constructing the video using multiple files, including closed caption files, mrt and webm videos, and chapter markers. I'm putting them together at the theme level with a custom node template. Not being able to translate the file means I have to add translation logic into the template, ugh. I'm beginning to regret moving to entity translation instead of content translation. -- edit, oh, I just found the button to translate the field. It was toward the bottom of the field edit page.