The current naming system of the keys in the Transifex-destined JSON KV file is such that HTML links are sometimes included in the key name.
The naming system for KV pairs takes advantage of surrounding JSON elements in an attempt to provide each V with a sane, unique K. Sometimes, links in the YAML front matter are named as functions (i.e. "Submit") and not as HTML addresses (i.e. http://panicbutton.io/transifex/transifex.html). It is necessary to develop a system for processing links in the latter case. For example, the link could be trimmed to just contain the base address (e.g. the section prior to 'html', in this example, 'transifex').
This is an ongoing translation concern, related to iilab/contentascode#3 and iilab/contentascode#2.
The current naming system of the keys in the Transifex-destined JSON KV file is such that HTML links are sometimes included in the key name.
The naming system for KV pairs takes advantage of surrounding JSON elements in an attempt to provide each V with a sane, unique K. Sometimes, links in the YAML front matter are named as functions (i.e. "Submit") and not as HTML addresses (i.e. http://panicbutton.io/transifex/transifex.html). It is necessary to develop a system for processing links in the latter case. For example, the link could be trimmed to just contain the base address (e.g. the section prior to 'html', in this example, 'transifex').
This is an ongoing translation concern, related to iilab/contentascode#3 and iilab/contentascode#2.