lutaml_gml_dictionary: <gml:description> element content beginning with a "full-stop / period" causing blank table #299
Comments
|
@ReesePlews yes it's possible because a prefixing dot in AsciiDoc makes it a "caption". So for this column, we could either detect the dot and escape it, or we encode this column as "code" since they are file extensions. This should be configurable in the templates. |
|
thank you @ronaldtse for the information. i was not sure if having a "dot" in the content was allowed or not. i searched around and could not find that a "dot" was an invalid character, but perhaps going through some transformations, something was getting lost. this currently only happens with one table. if a fix is too difficult at this time it could be replaced by a static table. i am sorry but i dont think i can make the changes to the template. let us know what you decide so if needed we have time to make as a static table. thank you. |
hello @kwkwan the lutaml_gml_dictionary block macro has been working very well. the client reports there is one table in the document that has a bit of an issue... it is "empty"
the lutaml_gml_dictionary call is:
lutaml_gml_dictionary::iur/codelists/3.1/ImplicitGeometry_mimeType.xml[template="gml_dict_template.liquid",context=dict]the input xml file is:
https://www.geospatial.jp/iur/codelists/3.1/ImplicitGeometry_mimeType.xml
the gml description tag (shown here) begins with a "full-stop/period"
<gml:description>.gltf</gml:description>is the "full-stop/period" possibly causing a problem and the table is not being populated correctly?
sources/001-v5 ( \sources\001-v5\sections\section-09\section-08.adoc )
this seems to be the only table where this is happening. thank you for checking this.
The text was updated successfully, but these errors were encountered: