From: Florent Michel <florent.m42@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: Hyphenated word in html export
Date: Fri, 8 Nov 2024 07:04:13 +0000 [thread overview]
Message-ID: <CALOhoeJZBeASvp7wiAjY7eO7NQ6Te6q9sq7ebDh5SRS=z5wxrw@mail.gmail.com> (raw)
In-Reply-To: <cd01c9e0-887b-4b0a-b7d7-645cf89869ff@rik.users.panix.com>
[-- Attachment #1.1: Type: text/plain, Size: 2011 bytes --]
Thank you Rik! I confirm this works, both on my minimal example and longer
document.
On Fri, Nov 8, 2024, 02:51 Rik Kabel <ConTeXt@rik.users.panix.com> wrote:
> On 2024-11-07 17:56, Florent Michel wrote:
>
> Apologies for the double email.
>
> I raised just after sending the previous one that using the ‘proper’ utf-8
> hyphen character (0x2010) instead of 0x002d solves the issue.
> I'd be interested to hear if someone has an easier-to-type
> solution, though.
>
> Le jeu. 7 nov. 2024 à 22:35, Florent Michel <florent.m42@gmail.com> a
> écrit :
>
>> Hello,
>>
>> Is there a way to preserve hyphenated words in the html export?
>> When exporting a document with ConTeXt, hyphens in the middle of words
>> seem to be replaced by soft hyphens, which are not displayed by my web
>> browser.
>>
>> Minimal example:
>>
>> \setupbackend[export=yes]
>> \starttext
>> co-worker
>> \stoptext
>>
>> The resulting .html file contains:
>> <div>
>> coworker</div>
>>
>> (There is apparently a soft hyphen between ‘co’ and ‘worker’. The pdf
>> seems to render correctly.)
>>
>> Cheers,
>> Florent
>>
> If you use *\setupbackend[export=yes,hyphen=no]* you will get a hard
> hyphen (hex 2D) where you show a soft hyphen (hex AD). Whether that
> addresses your larger document I cannot say, but it solves the problem for
> your example. See <https://wiki.contextgarden.net/Command/setupexport>.
>
> --
> Rik
>
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
> archive : https://github.com/contextgarden/context
> wiki : https://wiki.contextgarden.net
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 4086 bytes --]
[-- Attachment #2: Type: text/plain, Size: 511 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2024-11-08 7:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 22:35 [NTG-context] " Florent Michel
2024-11-07 22:56 ` [NTG-context] " Florent Michel
2024-11-08 2:48 ` Rik Kabel
2024-11-08 7:04 ` Florent Michel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALOhoeJZBeASvp7wiAjY7eO7NQ6Te6q9sq7ebDh5SRS=z5wxrw@mail.gmail.com' \
--to=florent.m42@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).