Translations
Comments
-
Not an answer here but something else to consider when doing translations. Generally when we translate for a client, and the translation is unique to that client, we put the translation in the locales directory of the theme. If the client uses Lithe as a mobile theme, those translations are not available on mobile. If the client has a unique plugin for their set up you can put it in the plugin, that way it is always present.
6 -
First, there's our basic translations in Transifex. When something is technically wrong (not flavorfully wrong) with a translation OR if we're missing a translation entirely, we refer them to Transifex. That is the one true source of all base translation.
Second, there is the code layer that Patrick covered. We can set flavor-changing, customer-specific translations best via plugin or theme.
Third, there is the console override. This is a blunt tool because it is language-agnostic - an override there overrides the translations regardless of language, so it cannot be used on a multilingual subcommunities site.
11 -
@Derrick said:
Is this the scenario where we should bill for our time?Yes: custom + language-specific.
0
