Each Cōdex should also explain related files

[fititnt]

Related:

• Generic tooling for explain files of published dictionaries (file validation; human explanation) #12
• MVP of [1603:1:??] /Documentation about 1603 types of files/ #10

---

Currently each /Cōdex/@lat-Latn both document all direct information on the main /Dictiōnāria/@lat-Latn and attach explanations of lingual and interlingual information which de facto will appear on the /Cōdex/@lat-Latn. This can be improved, but already works.

However, we also need to do a similar approach, but for the archive files themselves. Such documentation needs to be targeted: only appear for files which actually are pre-compiled. Also already with exact file names.

Reasoning

Each /Cōdex/@lat-Latn have as target audience humans likely to review or fix errors on source of the Information. However, we know that users also intended to create derived works (or which may be tempted to do a lot of copy and pasting) may not know that we explicitly have machine readable files.

We're also having issues with Unicode rendering of the graphenes. So more than one option of Codex needs to be documented and extra information.

The PDF (despite being less accessible) has the advantage of allowing embed fonts so we're sure end users can at bare minimum see the content. However this depends on our realistic skill to implement it correctly. The issue on this point ishttps://github.com/EticaAI/multilingual-lexicography/issues/13. The ASCIIdoctor version is already the one we use to prepare the PDF (and could be used to export to many other formats) so we document that version too.

Limitation

The embed descriptions of files should not be overlong as this would be better done by dedicated books which explain the files better. The motivation for this is also that the explanation of the files would be better to not be hard to be translated. And by keeping short and focused, we somewhat help with this.

[fititnt]

Status quo

Each Cōdex already uses heavily these group of dictionaries

• [1603:1:51] //Dictiōnāria Linguārum ad MMXXII ex Numerordĭnātĭo//
  • for linguistic content (like language codes, example ara-Arab = Macrolingua Arabica (Abecedarium Arabicum) )
• [1603:1:7] //Dictiōnāria basibus dē rēs interlinguīs//
  • for inter-linguistic content (like the properties, example: ix_wikip655 = /translator/@eng-Latn)

Other not so integrated dictionaries

• [1603:1:1] //Numeroclatura Generālium ad MM ex Numerordĭnātĭo//
  • This already is used (actually hard requirement), maybe it could be improved a bit with the MVP of better management of Dictiōnāria + Cōdex automated updated (necessary for future schedule/cron) MVP of better management of Dictiōnāria + Cōdex automated updated (necessary for future schedule/cron) #29
• [1603:1:99] Nōtitiae temporāriōrum circā librārium
  • This is what Brazilians would call gambiarra. Not ideal, but temporary messages previously hard-coded on Codex generation are at least moved to here

Dictionaries NOT integrated (need prepare dictionaries first)

These ones are done as we develop the things. so they do exist as dictionaries, but are not used yet 100% integrated to explain the Codex

• [1603:1:6] /Dictiōnāria de terminī typīs/
• [1603:1:101] //Dictiōnāria Archīōrum ad MMXXII ex Numerordĭnātĭo//

[fititnt]

Already implemented some months ago. Minor improvements could be done (likely move some things from python code to tabular format) but the main issues was solved.