Translations occur in two English source markdown files

[naturalshine]

The files 0001-01-01-setup-language.md and 0001-01-01-settings-language.md seem inconsistent with the current translation process -- should each be cut to only include the English "action" and "title"? Or -- in the case that they're a different translation logic, should they even be "marked" for translation at all (i.e. should we change the "title" key to a non-white-listed key?) @jmatsushita
Relevant to iilab/contentascode#3

[jmatsushita]

Interesting case. Let's keep this open, keep them as non translatable for
now and let's document this in a "adding a new language" page in our docs.
I think we can solve it when we have a way to deal with more granular
aggregation of content, I.e. asking the translators to translate only
part of the file.
On 16 Feb 2016 18:19, "cst" [email protected] wrote:

The files 0001-01-01-setup-language.md
https://github.com/PanicInitiative/panicbutton.io/blob/master/_posts/mobile/0001-01-01-setup-language.md
and 0001-01-01-settings-language.md
https://github.com/PanicInitiative/panicbutton.io/blob/contentascode/_posts/mobile/0001-01-01-settings-language.md
seem inconsistent with the current translation process -- should each be
cut to only include the English "action" and "title"? Or -- in the case
that they're a different translation logic, should they even be "marked"
for translation at all (i.e. should we change the "title" key to a
non-white-listed key?) @jmatsushita https://github.com/jmatsushita
Relevant to iilab/contentascode#3
iilab/contentascode#3

—
Reply to this email directly or view it on GitHub
#27.

[naturalshine]

Great! I'll do this documentation today :)