On 27/06/2023 18:14, Étienne Deparis wrote:
Oh, very sorry, actually it effectively leaves the spaces as this in the
output file. I was confused by Firefox, who makes the replacement
(interpret non-breaking spaces UTF-8 char as breaking, and replace them
by regular space when copy/pasting
On 27/06/2023 18:14, Étienne Deparis wrote:
Oh, very sorry, actually it effectively leaves the spaces as this in the
output file. I was confused by Firefox, who makes the replacement
(interpret non-breaking spaces UTF-8 char as breaking, and replace them
by regular space when copy/pasting
Étienne Deparis writes:
>>> - spaces to be replaced by their HTML entity (either or
>>> )
>>
>> You can achieve it using space entities.
>
> I’m not sure to understand your proposal: directly write
> into my
> org document?
You can write \nbsp{}.
See
mar. 27 juin 2023 à 12:54, yanta...@posteo.net a écrit :
I cannot reproduce.
Oh, very sorry, actually it effectively leaves the spaces as this
in the
output file. I was confused by Firefox, who makes the replacement
(interpret non-breaking spaces UTF-8 char as breaking, and replace
Étienne Deparis writes:
> Ceci est un exemple :
>
> N’est-il pas interessant ?
> ...
> ...
> However, after export all those spaces have disapeared. I cannot
> find
> where in the code this replacement is made, thus if one know
> better how
> the exporter run here, it would be great to
Hi,
If I’m not wrong, I think I just came across a little issue while
using
HTML export in org mode.
As a french writer, we use a lot of non-breaking spaces¹ in
various
situation. For exemple before double column or question mark:
Ceci est un exemple :
N’est-il pas interessant ?
¹
