TYPO3 Core

Hi Mathias,

Yes, I know:
to edit metadata click the title
to translate metadata, click the World (toggle) Symbol and so on.

But if metadata in default language do not exist, the toggle icon should not be shown. As you said, you can't translate something which does not exist. :)

For the future it's fine for me to add metadata without translations. But until now we translate and only stuff which exists can be translated.

But now you can add metadata to an element if not metadata is given in default language. And this seems to be wrong for me in the actual concept.

In TYPO3 7 this is an UX thing. We are taaking about translation, think as an editor.

I hope this will make it a little bit clearer now.

Argh, I know! Don't let's talk about things we discussed years ago. So please close this issue and let's discuss those stuff in person or at a sprint.

Closing the ticket won't help.
It will result in the same situation as we are in now.
People discuss things, do not write them down and two years down the road we discuss them again :)

So yes please.. let's discuss things but no, let's not close this ticket.

Ok, imagine:
From a devs point of view there will exist some metadata.
Form an editos point of view nothing is there if mo metadata is written by someone.
From an translation view - and let's talk about software - nothing can be translated if here is not default language!

Let me try to explain without any dev stuff:

You have a nice text:
you send the text ot a translator and what you will get back is the translated text.

You have a nice picture with empty meta data:
You send the picture to a translator and you will get back "???" - nothing.

The translator can't work with emty values.

Hi,

does this issue still exist?

Yes, this issue still exists.
Ich can edit metadata in all languages, even if there is no text in metadata in default language.
So if you have an automatic process of Translation like Trados or any other translation software, the translator will get an empty file - so he will not be able to translate.

Since we had some issues with meta data translations too the question that came up with our issues is:
Can we get visible metadata records using a page record of the type folder resulting in a pid other than 0, so we can translate them with the L10nmgr?

Here are some cents we can add to this topic:

First of all "translation" technically and from an editor's point of view means:

I got "this" in one language and need "that" in another language.

Best example for this use case are subtitles: An image containing a headline either in the default or the target language, which does not need a caption in that particular language but in any other language.
Usually professional translators don't get just single records for translation anyway, but the rest of the texts and images too to provide some context for the translation process.

So it doesn't hurt at all to have empty values in the default language, since either there will be a context resulting in a translated string or there will be no context resulting in the same empty string as in the default language.