glossarist / iev-document

Auto-generated IEV document from ConceptYAML
1 stars 0 forks source link

Support multi-lingual concepts #18

Closed ronaldtse closed 2 years ago

ronaldtse commented 2 years ago

Sample 1

Screenshot 2021-11-18 at 2 12 48 PM

Sample 2

Screenshot 2021-11-18 at 2 12 58 PM
opoudjis commented 2 years ago

We will have designations in multiple languages, with existing markup using metadata attributes of designations.

The English and French terms are not just designations, but two different languages' versions of the same term. We are going to introduce language as a tag of terms, just as it already a tag of clauses; and we will use multilingual formatting (the @name attribute) to align the English and French term in Semantic XML. We will fold the French under the English term in Presentation XML; and we will need to update the xrefs to account for the fact that there are less terms as a result than there used to be.

opoudjis commented 2 years ago

The French-language term has French metalanguage: term note label, term example label, related term label, term source label. These all need to be redone in French.

opoudjis commented 2 years ago
  1. "modified" needs to be bilingual (French and English)—I will need to move the resolution of to Presentation XML

  2. Arabic, I have finally hit RTL, <> is not wrapping correctly

  3. There is random ordering of termnotes and termexamples between English and French, I need to order them in Presentation XML, not HTML

opoudjis commented 2 years ago

Move rearranging of term notes before term examples to Presentation XML, so that merger of English and French term can happen after it.

opoudjis commented 2 years ago

Do not term a term designation from expression to letter-symbol if it has textual content: stem:[gamma]-ray is an expression, not a letter-symbol.

opoudjis commented 2 years ago

Two other-language terms in the same language are displayed in the same definition list entry, separated by line break.