From: Seong-Kook Shin <cinsky@gmail.com>
To: Vladimir Lomov <lomov.vl@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to force markup without spaces
Date: Mon, 19 Nov 2012 19:06:10 +0900 [thread overview]
Message-ID: <CAMGhBRS59Lz1MutLJwpOu0_OFk9pRgpFR-cSFDggFGUmrThsWg@mail.gmail.com> (raw)
In-Reply-To: <20121119071139.GM851@smoon>
[-- Attachment #1: Type: text/plain, Size: 2796 bytes --]
Yes, thank for the solution.
By the way, I'll prefer "word joiner" character (U+2060) to "zero width
space" character (U+200B),
because postpositions (grammar) should not be separated on line-break
policy.
Anyway, is there any plan to implement this feature in other way?
Using the solution that you provides makes the org document stick to the
unicode,
so it can't be used in other character encodings.
Thanks.
On Mon, Nov 19, 2012 at 4:11 PM, Vladimir Lomov <lomov.vl@gmail.com> wrote:
> Hello,
> ** cinsky@gmail.com [2012-11-19 14:32:21 +0900]:
>
> > Hi,
>
> > AFAIK, if the markup syntax (=code=, *bold*, ..) is directly followed
> > by non-whitespace characters, then it will not be marked-up:
>
> > =hello=there
> > /not/italic
>
> > This may be right decision on English text, but in some languages, the
> > postposition (grammar) will be postfixed without spaces into the
> > previous noun, so it will be the trouble. (Following text contains
> > Korean characters in UTF-8, you may need additional korean font to
> > read properly)
>
> > =printf=는
> > =bold=로
> > =철수=는
>
> > I'm sure that some other languages will have same problem
> > (e.g. Japanese or Chinese).
>
> > Is there any way to force mark-up on this situation?
>
> > If this pattern cannot be implemented easily, how about to introduce
> > new escaping character to prevent to insert whitespace between
> > marked-up text and the following postfix text? For example:
>
> > =printf=\is => rendered in HTML: <code>printf</code>is
> > *bold*\asdf => rendered in HTML: <b>bold</b>asdf
> > /철수/\는 => rendered in HTML: <i>철수</i>는
>
> > I can't say the above solution is well-designed, but I'm sure that
> > you'll get the point.
>
> May be this will help you:
> http://article.gmane.org/gmane.emacs.orgmode/46263/match=zero+width+space
>
> --
> "Had he and I but met
> By some old ancient inn, But ranged as infantry,
> We should have sat us down to wet And staring face to face,
> Right many a nipperkin! I shot at him as he at me,
> And killed him in his place.
> I shot him dead because --
> Because he was my foe, He thought he'd 'list, perhaps,
> Just so: my foe of course he was; Off-hand-like -- just as I --
> That's clear enough; although Was out of work -- had sold his
> traps
> No other reason why.
> Yes; quaint and curious war is!
> You shoot a fellow down
> You'd treat, if met where any bar is
> Or help to half-a-crown."
> -- Thomas Hardy
>
--
C FAQs: http://c-faq.com/
Korean: http://www.cinsk.org/cfaqs/
[-- Attachment #2: Type: text/html, Size: 4311 bytes --]
next prev parent reply other threads:[~2012-11-19 10:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 5:32 How to force markup without spaces cinsky
2012-11-19 7:11 ` Vladimir Lomov
2012-11-19 10:06 ` Seong-Kook Shin [this message]
2012-11-19 14:40 ` Suvayu Ali
2012-12-13 21:26 ` Bastien
2022-07-25 17:50 ` K
2022-07-25 18:27 ` K
2022-07-25 19:02 ` K
2022-07-26 1:26 ` Ihor Radchenko
2022-07-26 2:23 ` Max Nikulin
2022-07-26 4:26 ` K K
2022-07-26 6:30 ` Max Nikulin
2022-07-26 12:59 ` [PATCH] org-export: Remove zero-width space escapes during export Ihor Radchenko
2022-07-26 14:25 ` Timothy
2022-07-26 15:27 ` András Simonyi
2022-07-26 16:38 ` Max Nikulin
2022-07-27 3:30 ` Max Nikulin
2022-07-28 13:17 ` [PATCH] Add new entity \-- serving as markup separator/escape symbol Ihor Radchenko
2022-07-28 15:34 ` Max Nikulin
2022-07-29 1:43 ` Ihor Radchenko
2022-07-29 2:50 ` Max Nikulin
2022-07-29 9:06 ` [PATCH v2] " Ihor Radchenko
2022-07-30 0:22 ` Samuel Wales
2022-07-30 4:12 ` Samuel Wales
2022-07-30 6:49 ` Ihor Radchenko
2022-07-30 15:44 ` Max Nikulin
2022-07-28 22:20 ` [PATCH] " Tim Cross
2022-07-29 0:32 ` Juan Manuel Macías
2022-07-29 5:49 ` tomas
-- strict thread matches above, loose matches on Subject: below --
2022-07-26 10:24 How to force markup without spaces K
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMGhBRS59Lz1MutLJwpOu0_OFk9pRgpFR-cSFDggFGUmrThsWg@mail.gmail.com \
--to=cinsky@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=lomov.vl@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).