-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handling bilingual documents with weaving (sequential vs parallel) #101
Comments
|
So there are 3 cases to display images:
|
@ronaldtse The requirements for "weaving/stitching" the bilingual documents: should be marked with the attribute common="true" (in both documents) like this: <table id="table1" common="true">... and table in adoc for first document should have text for both languages (the logic for merging table cell via xslt is too complicated)
should be marked with the attribute span="true" (in both documents) like this: <figure id="figure2" span="true">... Some another comments: Currenly, it shows like this - one footnotes below another:
|
@ronaldtse Alternative variant instead of
|
The easy way is to align on every (significant) document element. I wonder if this should be configurable (i.e. which elements should align across languages.
This should be an anomaly as the original document was done manually.
I consider this table a shared table that is encoded as bilingual and inseparable into two separate per-language tables.
Let's consider these part of the language-specific image.
Correct.
This is acceptable for now. |
@ronaldtse would you like to configure it:
|
Both:
This can be a configurable attribute in Adoc. and
Should work right? |
Apart from the minor detail that you've just made this markup up, Asciidoc will not do anything useful with it, and in any case the collections processing will destroy it because they will insert the document suffix after the id, precisely in order to guarantee identifier uniqueness in the aggregated document. You cannot just insert |
I agree that id should be unique in the collection xml. Some thoughts how XSLT will process xml in this manner (preliminary solution, I have to do some experiments):
|
…les, images and annex
JCGM XSLT updated to produce bilingual document with these rules/properties:
note: attributes names can be chaged, or changed to class. etc. It can be changed in prototype xslt. There are a few restrictions:
So, if this solution is acceptable, then in adoc these property should be added:
|
Wait. These are updates to the information model of Metanorma, and I need to understand them before I can approve them, and make sure they are clear within the context of Metanorma as well. So:
If you're ok with these, I'll realise them in metanorma/metanorma-standoc#420 |
Example1: align-cross-elements="clause", i.e. clauses (begin of clauses) always be aligned in bilingual text. Example2: align-cross-elements="clause li", i.e. clauses, list items (begin of clauses and list items) always be aligned in bilingual text. Example3: align-cross-elements="clause li p", i.e. clauses, list items and paragraphs (begin of clauses, list items and paragraphs) always be aligned in bilingual text. Note that in align-cross-elements we set the name of xml elements (
Actually align-cross-elements can be in any place, may be it would be better in metanorma-collection/align-cross-elements or metanorma-collection/align-cross-elements/manifest.
No problem, the element's structure does not matter.
May be, is there a use case of this tag in real documents?
Agree.
Sorry, I don't understand it. In my proposal
<figure id="figureC-2" name="figtest">
<name>Figure C.2 — Stages of gelatinization</name>
<figure id="figureA-1" name="figtest">
<name>Figure A.1test — Diviseur d’échantillon de type «Bon diviseur» (@common=true)</name> I.e. element with But what |
Also a note that we will need validation on compilation for the semantic XML, i.e. so that the user won't miss alignments (e.g., "the element foo [en] does not have a corresponding element in [fr]"). |
@Intelligent2013 I'm proposing:
It seems laboured, perhaps, but I don't want to presuppose what |
I see. Agree. Regarding to these use cases (https://www.ctan.org/pkg/paracol):
may be it would be better to rename some properties:
for a clearer understanding of objectives the elements. |
|
@manuel489 and @anermina could you encode https://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2012.pdf into asciidoc? Thank you! |
We're moving JCGM documents into https://github.com/metanorma/mn-samples-jcgm. Thanks! |
@manuel489 @anermina we will wait for JCGM to provide further information of JCGM 200, we don't want to manually convert that document, it's long. Thanks! |
The JCGM_200_2012 document uses a different layout than the bilingual SI Brochure which is sequential in "document".
The SI Brochure is composed of the English and French documents placed one after another. (document-level weaving).
JCGM 200 is composed of multiple weaving methods, where two documents are stitched together at different points, sequential in some but parallel in others.
There are different cases that need encoding in this layout.
Sequential
This section of English text corresponds to French text, show English first and French next.
Parallel
Side by side
English text corresponds to French text, placed side by side
Shared element between both languages
Document element applies to both text, e.g. 1 table/image shared by both languages
@Intelligent2013 could you spell out the requirements for "weaving/stitching" the bilingual documents?
Originally posted by @ronaldtse in #88 (comment)
The text was updated successfully, but these errors were encountered: