Hi,
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
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.
AFAIK, this will not be included;
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
On Mon, Nov 19, 2012 at 07:06:10PM +0900, Seong-Kook Shin wrote:
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.
AFAIK, this will not be
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
Hello,
** cin...@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,
