question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[remark-typo]: french quotes not inserted on some WTF cases

See original GitHub issue

Here is the sentence :

Les propriétaires de l'application créent un <<contenu>>, lui donne des <<méta données>> et les visiteurs vont pouvoir accéder à la fiche ainsi rédigée de ces contenus.

Here is the result :

Un CMS distingue deux types d’utilisateurs : les propriétaires et les visiteurs. Le concept est le suivant : Les propriétaires de l’application créent un <<contenu>>, lui donne des «méta données» et les visiteurs vont pouvoir accéder à la fiche ainsi rédigée de ces contenus.

the “contenu” part is not properly translated. It is translated if we put a blanck space between << and c.

It is expected not to have to put this extra space.

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
StaloneLabcommented, Dec 15, 2022

Okay, finally we should be able to solve it correctly. I found one of our plugins, remark-fix-guillemets, which already does what we want. It was certainly forgotten during one of the refactorings. I included it in my PR for ZMarkdown 11.2. The problem reported by @AmauryCarrade about adding NBSP was also solved by a simple fix to the plugin.

1reaction
StaloneLabcommented, Dec 14, 2022

I recently investigated this problem, which was more complicated than I expected, and am left with the following:

  • allowing the syntax without space would be complicated, because of how remark works internally, and of how the plugin was designed (visiting the tree after tokenization). I am not ready to rewrite this plugin (or any other) without a micromark migration (because the job would be done twice), but anyway I take note of this issue;
  • what I suggest is therefore to enforce the following syntax: << [content] >>, with spaces inside, that will be replaced by NBSP. It would solve the issue in the following way: <<méta données>> will give the same result as <<contenu>>: no french quotes.
Read more comments on GitHub >

github_iconTop Results From Across the Web

Issues · zestedesavoir/zmarkdown - GitHub
[remark-typo]: french quotes not inserted on some WTF cases semver/bugfix This is a minor backward-compatible fix status/verified This has been checked by a ......
Read more >
How to force equal spaces around French quotation marks?
as Bernard says ~ is the wrong space in any case but all ~ on a line will stretch by the same amount...
Read more >
quotes - CSS-Tricks
The quotes property in CSS allows you to specify which types of quotes are used when quotes are added via the content: open-quote; ......
Read more >
Smart quotes in Word - Microsoft Support
Smart quotes in Word ... As you type text, Word automatically changes straight quotation marks ( ' or " ) to curly quotation...
Read more >
Quotation mark - Wikipedia
Quotation marks are punctuation marks used in pairs in various writing systems to set off direct speech, a quotation, or a phrase.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found