public inbox for edbrowse-dev@edbrowse.org
 help / color / mirror / Atom feed
From: chris@the-brannons.com
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] soft hyphen
Date: Fri, 29 May 2015 13:50:42 -0700	[thread overview]
Message-ID: <87fv6ff6ql.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20150428161303.eklhad@comcast.net> (Karl Dahlke's message of "Thu, 28 May 2015 16:13:03 -0400")

I wonder if it would be worth implementing the semantics described
in Wikipedia.  Here they are, just for reference:

<quote>
The soft hyphen tells the user agent where a line break can occur.
Those browsers that interpret soft hyphens must observe the following semantics.
If a line is broken at a soft hyphen,
a hyphen character must be displayed at the end of the first line.
If a line is not broken at a soft hyphen,
the user agent must not display a hyphen character.
</quote>

The page you linked in your original post would look great with the soft
hyphens removed.  Maybe just remove them for now, and consider using
them as part of word-wrapping at a later date?

-- Chris

      reply	other threads:[~ UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Karl Dahlke
 ` chris [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=87fv6ff6ql.fsf@mushroom.localdomain \
    --to=chris@the-brannons.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).