(URGENT) CIPM Declaration from CIPM meeting 90 shows mistaken # character in title

[ronaldtse]

As you can see there is an issue with a # inserted into the declaration's description here:

The particular line originates from here:

• https://github.com/metanorma/bipm-data-outcomes/blob/eafca5cf19d3e19f63386d009e1a6a3cc0f40a35/cipm/meetings-fr/meeting-90.yml#L84

Then in relaton-data-bipm here:

• https://github.com/relaton/relaton-data-bipm/blob/9affdaf0d71dcc758666fe8a9ab9631f2b36f542/data/cipm/meeting/declaration/2001-00.yaml#L11

And it seems that it is actually a normal white space, so I don't know why it became a # (which typically indicates a missing glyph).

Ping @Intelligent2013 @andrew2net to fix this.

Originally posted by @ronaldtse in #223 (comment)

[andrew2net]

@ronaldtse there is no "#" in relaton-data-bipm, right? So we need to check renderer.

[ronaldtse]

Yes it seems like a rendering problem. However can you help double check that the space in your data is a normal space? Thanks.

[andrew2net]

Just checked, they are normal 32 code space

[Intelligent2013]

In the PDF generated on my machine (Win10) there isn't #:

The font Times New Roman Italic is using for the text rendering:

The difference between your and my PDF means that some 'space' character is missing in your font instance (may be old). Some years we have the similar issues. If you need I can find, but in any case the new font should be used.

In the Presentation XML there are two spaces between «  and unités :

• space 0x202F Narrow No-Break Space
• space 0x20

My Times New Roman font instance contains 0x202F character:

In the semantic XML only one space:

In meeting-90.yml and 2001-00.yaml only one space 0x20:

@opoudjis could you take a look at the reason why 0x202F appears in the Presentation XML?

[andrew2net]

@ronaldtse maybe the problem is not in spaces. The "«" is not an UTF-8 symbol

>  "« unités SI » et « unités du SI »"[0].ord
=> 171

> 171.chr
 => "\xAB"

> puts 171.chr
(irb):190:in `write': "\xAB" from ASCII-8BIT to UTF-8 (Encoding::UndefinedConversionError)

[opoudjis]

The additional space is my fault. I am applying French punctuation rules to generated references, which is appropriate, but I should not be inserting spaces after gullemets, if spaces are already there, even if they are the "wrong" space (normal space instead of the correct 202f.) Needs fix to isodoc-i18n, will do hotfix shortly.

[opoudjis]

tested with * [[[PV57_5, CIPM RES (1948, F)]]]: I'm currently unable to fetch * [[[PV69, CIPM Declaration (2001)]]]. Confirmed that it is no longer inserting extra 202f:

<bibitem id="PV57_5" type="proceedings" schema-version="v1.2.9">
<formattedref>Comité International des Poids et Mesures (1948) 
<em>Adoption de « degré Celsius »</em> (Paris : Bureau international des poids et mesures) 

[manuelfuenmayor]

Fix confirmed: