Title: Hello,
Author: Eric Gagnon
Published: February 26, 2018

---

 [  ](https://profiles.wordpress.org/anonym999999/) [Eric Gagnon](https://profiles.wordpress.org/anonym999999/)
11:48 pm _on_ February 26, 2018     
Tags: [fr_CA ( 120 )](https://make.wordpress.org/polyglots/teams/?locale=fr_CA),
[request ( 1,481 )](https://make.wordpress.org/polyglots/tag/request/)   

# Hello,

I’m a bit lost of where I should report an issue regarding [#fr_CA](https://make.wordpress.org/polyglots/teams/?locale=fr_CA).

With the updates, I now see a “Mise à jour (**non breaking space htmlHTML HTML is
an acronym for Hyper Text Markup Language. It is a markup language that is used 
in the development of web pages and websites. encoded**)!” message. It’s a technical
bug (use of html encoding in a place where it is not supported) and also a french
error.

It’s a pretty common error with web application to see this, the requirement is 
for a fine space before !, but as we dont have the character (that you have in software
like Indesign by exemple) so some people think using a unbreaking space is valid
replacement, it’s not.

From “Office Québecois de la langue française”, we can find the rule “Pas d’espace
ou une espace fine”: http://bdl.oqlf.gouv.qc.ca/bdl/gabarit_bdl.asp?id=2039

So it should really have stayed as “Mise à jour!”.

I suppose it was a bulk replacement so there are surely other case.

Where should I report this?
 [#request](https://make.wordpress.org/polyglots/tag/request/)

### Share this:

 * [  Threads ](https://make.wordpress.org/polyglots/2018/02/26/hello-18/?share=threads)
 * [  Bluesky ](https://make.wordpress.org/polyglots/2018/02/26/hello-18/?share=bluesky)
 * [  Facebook ](https://make.wordpress.org/polyglots/2018/02/26/hello-18/?share=facebook)
 * [  X ](https://make.wordpress.org/polyglots/2018/02/26/hello-18/?share=x)
 * [  Mastodon ](https://make.wordpress.org/polyglots/2018/02/26/hello-18/?share=mastodon)
 * [  WhatsApp ](https://make.wordpress.org/polyglots/2018/02/26/hello-18/?share=jetpack-whatsapp)
 * [  LinkedIn ](https://make.wordpress.org/polyglots/2018/02/26/hello-18/?share=linkedin)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fpolyglots%2F2018%2F02%2F26%2Fhello-18%2F%23respond&locale=en_US)

 * [To-do](https://make.wordpress.org/polyglots/2018/02/26/hello-18/?output_format=md#)

 1.  ![](https://secure.gravatar.com/avatar/890bd890338f9b6a17143a65ac10a20410e135583d95106bb09f20d91f66afe2?
     s=32&d=mm&r=g)
 2.   [Tor-Bjorn Fjellner](https://profiles.wordpress.org/tobifjellner/)  11:50 pm 
     _on_ February 26, 2018
 3.  Hi [@anonym999999](https://profiles.wordpress.org/anonym999999/) Thanks, you just
     did report this.
      Since we’ve got the tag for [#fr_CA](https://make.wordpress.org/polyglots/teams/?locale=fr_CA)
     in the post, the GTEGeneral Translation Editor A General Translation Editor (often
     referred to as GTE) is a person, who has global access to validate strings on **
     all projects for a specific locale.**’s of that localeLocale Locale = language
     version, often a combination of a language code and a region code, for instance
     es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported 
     by WordPress in [https://make.wordpress.org/polyglots/teams/](https://make.wordpress.org/polyglots/teams/)
     should be notified. Interesting, is there any risk that we’ve got the same problem
     in other French localesLocale Locale = language version, often a combination of
     a language code and a region code, for instance es_MX denotes Spanish as it’s 
     used in Mexico. A list of all locales supported by WordPress in [https://make.wordpress.org/polyglots/teams/](https://make.wordpress.org/polyglots/teams/)?
     What about [#fr_FR](https://make.wordpress.org/polyglots/teams/?locale=fr_FR) 
     and [#fr_BE](https://make.wordpress.org/polyglots/teams/?locale=fr_BE) ?
 4.   * ![](https://secure.gravatar.com/avatar/03fec775ba7bbccce7139a73dd5e741fbaa2069cf384cf2c5b328d391dd82266?
        s=32&d=mm&r=g)
      *  [fxbenard](https://profiles.wordpress.org/fxbenard/)  7:05 am _on_ February
        27, 2018
      * [@anonym999999](https://profiles.wordpress.org/anonym999999/) [@tobifjellner](https://profiles.wordpress.org/tobifjellner/),
        
        In fr_FR it’s a typographical error not to use non breaking spaces before :;?
        etc. As we noticed that   might be visible in some UIUI UI is an acronym for
        User Interface - the layout of the page the user interacts with. Think ‘how
        are they doing that’ and less about what they are doing. (it will be more and
        more the case with the use of JS) they all have been removed from WP coreCore
        Core is the set of software required to run WordPress. The Core Development
        Team builds WordPress. translations and we are asking all our PTEs to use «
        real » non breaking space avalaible by French extended keyboard or the alt+
        255 shortcut. I guess it’s something not in use yet in fr_CA and might be done
        as well. More infos: [https://github.com/audrasjb/translate-wordpress-fr_FR#suivre-les-r%C3%A8gles-typographiques-fran%C3%A7aises](https://github.com/audrasjb/translate-wordpress-fr_FR#suivre-les-r%C3%A8gles-typographiques-fran%C3%A7aises)
      * Bonne journée
 5.  ![](https://secure.gravatar.com/avatar/4ec496e84e28f9d86d863cdfeb04f272474dc9b58587a65527b09506a8f20ee8?
     s=32&d=mm&r=g)
 6.   [Pascal Casier](https://profiles.wordpress.org/casiepa/)  7:57 am _on_ February
     27, 2018
 7.  [@anonym999999](https://profiles.wordpress.org/anonym999999/), could you indicate
     where exactly you see this? If we find it back on the screen, we might find where
     the code is and that could help us in finding the correct translation stringString
     A string is a translatable part of the software. A translation consists of a multitude
     of localized strings.. We can then see with [@mia](https://profiles.wordpress.org/mia/)
     from the [#fr_CA](https://make.wordpress.org/polyglots/teams/?locale=fr_CA) team
     where to change it.
 8.  But as [@fxbenard](https://profiles.wordpress.org/fxbenard/) indicates, the non
     breaking space is needed in front of the exclamation mark following our guidelines.
 9.   * ![](https://secure.gravatar.com/avatar/49ffbb3a9c570050132767d2208dfb8a08e5f4f5a4b6176ce8423f9aa14a3111?
        s=32&d=mm&r=g)
      *  [anonym999999](https://profiles.wordpress.org/anonym999999/)  2:46 pm _on_
        February 27, 2018
      * I posted a sample bellow.
 10. ![](https://secure.gravatar.com/avatar/49ffbb3a9c570050132767d2208dfb8a08e5f4f5a4b6176ce8423f9aa14a3111?
     s=32&d=mm&r=g)
 11.  [anonym999999](https://profiles.wordpress.org/anonym999999/)  2:38 pm _on_ February
     27, 2018
 12. Hello,
 13. Thanks for the followup, sorry I was really lost yesterday, it’s pretty hard to
     find the context / history of change of language text but I was able to figure
     it out and the change was done last year.
 14. The exemple where I noticed it first is here : [https://imgur.com/a/iVy9h](https://imgur.com/a/iVy9h)
     but I wonder if there was not a recent change in code that could have change the
     display behavior in that context.
 15. I was not aware of the french fr different rule.
 16.  * ![](https://secure.gravatar.com/avatar/49ffbb3a9c570050132767d2208dfb8a08e5f4f5a4b6176ce8423f9aa14a3111?
        s=32&d=mm&r=g)
      *  [anonym999999](https://profiles.wordpress.org/anonym999999/)  2:44 pm _on_
        February 27, 2018
      * I was able to find the rules here but I guess that what we could find in a “
        Ramat” bible (ie. [http://www.ramat.ca/files/extrait-le-ramat-de-la-typographie.pdf](http://www.ramat.ca/files/extrait-le-ramat-de-la-typographie.pdf)):
        [http://www.graphicvertigo.com/elephant/les-regles-typographiques-de-la-ponctuation-francaise/](http://www.graphicvertigo.com/elephant/les-regles-typographiques-de-la-ponctuation-francaise/)
      * I used to work in a french publishing house (who publish the Visual Dictionnary)
        and these where the things that we had to discuss when working on our electronic
        projects as there are not support for fine space.
      * I think that the recommandation from Office Québecois de la langue française
        to not use space when there is no fine space available (to prevent unintended
        line break) is more practical.
         - ![](https://secure.gravatar.com/avatar/49ffbb3a9c570050132767d2208dfb8a08e5f4f5a4b6176ce8423f9aa14a3111?
           s=32&d=mm&r=g)
         -  [anonym999999](https://profiles.wordpress.org/anonym999999/)  2:49 pm _on_
           February 27, 2018
         - Here is a blog post that compare the rules of fr_CA and fr_FR : [http://www.guylabbe.ca/blog/regles-typographiques-quebec-france.html](http://www.guylabbe.ca/blog/regles-typographiques-quebec-france.html)
            * ![](https://secure.gravatar.com/avatar/49ffbb3a9c570050132767d2208dfb8a08e5f4f5a4b6176ce8423f9aa14a3111?
              s=32&d=mm&r=g)
            *  [anonym999999](https://profiles.wordpress.org/anonym999999/)  2:50 pm
              _on_ February 27, 2018
            * So I guess there will be two different problem to adress, the rules of
              fr_CA and the problem of display of htmlHTML HTML is an acronym for Hyper
              Text Markup Language. It is a markup language that is used in the development
              of web pages and websites. encoded text in some context that doesnt support
              it.
               - ![](https://secure.gravatar.com/avatar/49ffbb3a9c570050132767d2208dfb8a08e5f4f5a4b6176ce8423f9aa14a3111?
                 s=32&d=mm&r=g)
               -  [anonym999999](https://profiles.wordpress.org/anonym999999/)  7:40
                 pm _on_ March 7, 2018
               - I left the issue aside as I had another priority. Should I report 
                 the issue of the display of text itself ([https://imgur.com/a/iVy9h](https://imgur.com/a/iVy9h))
                 somewhere? I would guess this problem is visible in fr_FR no?
               - ![](https://secure.gravatar.com/avatar/49ffbb3a9c570050132767d2208dfb8a08e5f4f5a4b6176ce8423f9aa14a3111?
                 s=32&d=mm&r=g)
               -  [anonym999999](https://profiles.wordpress.org/anonym999999/)  8:28
                 pm _on_ March 7, 2018
               - BTW , I’m working for bibliothèque et archives nationales du québec
                 and I have asked to our “services linguistiques” what they tought 
                 about the issue, this is what I got, confirming that the rule in fr_CA
                 is “without space” but :
               - “… ce n’est pas très grave qu’il y ait un espace insécable devant 
                 le !, alors je te propose de faire la chose la plus simple. De toute
                 façon, Word met un espace devant le ! (je passe mon temps à les enlever
                 dans les fichiers…).
               - Donc, on peut vivre avec ou sans l’espace devant le !.”
               - So I wont push myself for the text changes, I’ll just do the followup
                 for the display bug.
 17. ![](https://secure.gravatar.com/avatar/6eb7a807c02fddd489bf4707d2763f9b54c543d6d5457edfdb34e0059c9600e0?
     s=32&d=mm&r=g)
 18.  [mialevesque](https://profiles.wordpress.org/mialevesque/)  4:43 pm _on_ March
     9, 2018
 19. Thank you, [@anonym999999](https://profiles.wordpress.org/anonym999999/). I have
     removed the   and I am now going back to remove the unnecessary spaces for fr_CA.
     I welcome the help and support to improve fr_CA wherever and whenever possible.
     I have not had much time to volunteer in the past 6 months. The blog post was 
     very helpful. Best.
 20. ![](https://secure.gravatar.com/avatar/49ffbb3a9c570050132767d2208dfb8a08e5f4f5a4b6176ce8423f9aa14a3111?
     s=32&d=mm&r=g)
 21.  [Eric Gagnon](https://profiles.wordpress.org/anonym999999/)  4:57 pm _on_ March
     9, 2018
 22. Cool thanks.
 23. I have opened a ticket yesterday for the display issue : [https://core.trac.wordpress.org/ticket/43505](https://core.trac.wordpress.org/ticket/43505)(
     even with the fr_CA fix, it will still affect fr_FR).
 24. By the way, the staff responsible for the revision of our text identified this
     other text that could be improved (froms comment configuration section).
 25. L’auteur d’un commentaire doit **renseigner **son nom et son adresse courriel.
 26. Would be better as:
      L’auteur d’un commentaire doit **inscrire **son nom et son
     adresse courriel.
 27.  * ![](https://secure.gravatar.com/avatar/6eb7a807c02fddd489bf4707d2763f9b54c543d6d5457edfdb34e0059c9600e0?
        s=32&d=mm&r=g)
      *  [mialevesque](https://profiles.wordpress.org/mialevesque/)  5:11 pm _on_ March
        9, 2018
      * Super. Please thank them for the suggestion. I have updated this stringString
        A string is a translatable part of the software. A translation consists of 
        a multitude of localized strings. as well.

### Leave a Reply 󠀁[Cancel reply](https://make.wordpress.org/polyglots/2018/02/26/hello-18/?output_format=md#respond)󠁿

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fpolyglots%2F2018%2F02%2F26%2Fhello-18%2F&locale=en_US)
to post a comment.

# Post navigation

[← German translation editor for WooCommerce Stripe Payment Gateway plugin?](https://make.wordpress.org/polyglots/2018/02/26/german-translation-editor-for-woocommerce-stripe-payment-gateway-plugin/)

[Hello Polyglots, I am the plugin author for →](https://make.wordpress.org/polyglots/2018/02/27/hello-polyglots-i-am-the-plugin-author-for-153/)