add i18n-id & keep i18n attributs on development mode

I’m submitting a…

[ x ] Feature request

Current

i18n attributs are always removed from templates and we have path in xmb file to retrace where i18n attribut is used but we have not id in DOM when visiting app

Expected

Keep i18n attributs when app is not on production mode + add i18n-id="897897789678".

What is the motivation / use case for changing the behavior?

I think on developement mode we can kepp i18n on our html template because:

1. we can select i18n attribut with CSS to let traductors know what is translatable/missing
2. If we have an more attribut added like i18n-id="897897789678" we could listen onclick on each these attributs and open modal to translate text directly/instantly while visiting webapp. We already have meaning&description but that’s not enough (we have problems to translate our app french-german) this will avoid us maintain our “xmb->excel file” tool and avoid share xls file to traductor while he can just visit webapp and translate in place, and with id it is easy to find traduction in compiler output file messages.xmb
3. Angular create so many insignifiants attributs on production so why not theses for useful usecase only on developement mode. 😀

Environment

all

Others

see https://github.com/angular/angular/issues/11042 see https://github.com/angular/angular/issues/20055

[kasperstorgaard]

Any developments on this one? I have almost exact use case, and am wondering if I will have to fork the compiler to make something like this work for us.

[petebacondarwin]

Your feature request seems reasonable… although it would not be enough IMO since this would require the translator to step through every part of the app in order to see all the potential translations. Be aware also that after v9 developers will also be able to create messages in code too using $localize tags. So these will not be available to the translated via browsing the pages of the app.