Bug #2160
Mis à jour par Serge Heiden il y a plus de 7 ans
A) For some texts, words are not highlighted in editions.
The IDS of those words not highlighted contain characters that broke the CSS ID syntax rules (e.g " ", "(" and more)
h3. Discussion B) For some Windows and Internet Explorer, words highlight does not work.
Word IDs are built with <text identifier + number> or come from the sources.
If we forge the word ids in import modules, we must normalize/reduce text names to a text identifier, at the level of the corpus.
Three strategies:
* a) normalize/reduce characters or morphemes
* b) escape characters
* c) manage <text name>:<automatic text identifier> hash
b) suppose to escape with respect to the syntax reading the identifier: for example CSS syntax. So different escape algorithms may need to be used depending on context. See the XXX Java library to escape for a lot of different syntaxes.
c) suppose to use the hash in various contexts: eg concordance references, etc.
h3. Solution A1
Define Fix the most simple common compatible syntax compatible with CSS ID syntax and CQL syntax.
Do a) fix the XMLw to XML-TXM step of import modules, modules: in the XML2Ana class:
* normalize/reduce class the text word ID to the bottom syntax
must be normalized.
h3. Solution 2 A2
* add a new All pagers (but Doc import option "force pager) were messing with the first word id generation" for corpora having already when the page was cut using the number of words and was using the next word IDs.
* add a new load option "force id instead of the word id generation" for corpora having already word IDs.
that cuts the page.
h3. Solution B1
Update browser to version IE11 -> highlight should work
The IDS of those words not highlighted contain characters that broke the CSS ID syntax rules (e.g " ", "(" and more)
h3. Discussion B) For some Windows and Internet Explorer, words highlight does not work.
Word IDs are built with <text identifier + number> or come from the sources.
If we forge the word ids in import modules, we must normalize/reduce text names to a text identifier, at the level of the corpus.
Three strategies:
* a) normalize/reduce characters or morphemes
* b) escape characters
* c) manage <text name>:<automatic text identifier> hash
b) suppose to escape with respect to the syntax reading the identifier: for example CSS syntax. So different escape algorithms may need to be used depending on context. See the XXX Java library to escape for a lot of different syntaxes.
c) suppose to use the hash in various contexts: eg concordance references, etc.
h3. Solution A1
Define Fix the most simple common compatible syntax compatible with CSS ID syntax and CQL syntax.
Do a) fix the XMLw to XML-TXM step of import modules, modules: in the XML2Ana class:
* normalize/reduce class the text word ID to the bottom syntax
must be normalized.
h3. Solution 2 A2
* add a new All pagers (but Doc import option "force pager) were messing with the first word id generation" for corpora having already when the page was cut using the number of words and was using the next word IDs.
* add a new load option "force id instead of the word id generation" for corpora having already word IDs.
that cuts the page.
h3. Solution B1
Update browser to version IE11 -> highlight should work