Matthieu Huin mhuin@redhat.com writes:
Since there was no opposition so far to react-redux-i18n, I went on and finished the translation coverage. French speakers: vous pouvez voir ce que ça donne ici: https://882d44f6443dbd84112c-b429f7b1939d4fc1f35718a4403a0d7a.ssl.cf1.rackcd... Certaines traductions (ou non-traductions) prêtent à débat, n'hésitez pas à commenter sur gerrit. :)
I think my biggest concern with this is how awkward the Translate component is to use. It looks like every string needs an identifier, so what's currently: <Link> Summary </Link>
Turns in to: <Link> <Translate value='buildContainer.build.summary' /> </Link>
In python, with gettext, the change is more like: print("Summary")
to: print(_("Summary"))
This is not only less typing, but critically, the developer doesn't need to create an identifier for the string (and ensure it's unique within the relevant namespace). This makes it easier for developers to perform maintenance on code, and increases the likelihood of compliance with the i18n standards (and therefore a higher rate of translatable strings).
Is there any kind of system like this for react? It seems at the very least, we should be able to do something like:
<Link> <t> Summary </t> </Link>
and have that work like gettext. Does something like that exist?
-Jim