Re: [O] Ignore following space coding?

2013-04-24 Thread Bastien
Hi Hideki,

Hideki Saito hide...@gmail.com writes:

 The problem is if I'm trying to write:
 文字*太字*文字

 This essentially prevents text surrounded by * treated as a regular
 character as opposed to marked as bold, as this is pretty much
 equivalent of the following case:

 aa*bb*aa

If I remember correctly, this was asked already once and we did try
to find a solution, but nothing was good.

Org (and Emacs?) heavily relies on distinguishing words with spaces,
so maybe you should consider an Org file as you do consider a program
file: spaces are often mandatory.  This is the case when you want to
put some words in bold font.

HTH,

-- 
 Bastien



Re: [O] Ignore following space coding?

2013-04-24 Thread Hideki Saito
Hello Bastien
Yeah, I figured correctly implementing this would be the biggest
thing. (I think it involves the implementation of the full
morphological analysis model into Emacs!)


 If I remember correctly, this was asked already once and we did try
 to find a solution, but nothing was good.


I was thinking in more of a quick hack / workaround that possibly
exists -- for instance, as \ would escape the following letter (for
instance \\ for \) but that can cancel out the following
character, for example, when parsed through exporters. (Couldn't think
of any myself, so I was just curious.)

 Org (and Emacs?) heavily relies on distinguishing words with spaces,
 so maybe you should consider an Org file as you do consider a program
 file: spaces are often mandatory.  This is the case when you want to
 put some words in bold font.

I think I will take your suggestions, and perhaps, I might think of
some post-export processor that interact with exported LaTeX file
(where this is more pertinent in my case) to correct linguistic
irregularities.

Thank you for your insight on this!

Hideki Saito hide...@gmail.com
http://goo.gl/ErBLy



Re: [O] Ignore following space coding?

2013-04-24 Thread Vladimir Lomov
Hello,
** Hideki Saito [2013-04-22 02:36:09 -0700]:

 Hello,
 I briefly searching the list and but I'm unsure if this was discussed
 before, so excuse me if this was discussed before.

 I've got a question regarding how I can make this work with languages
 that doesn't separate words with spaces.

 The problem is if I'm trying to write:
 文字*太字*文字

 This essentially prevents text surrounded by * treated as a regular
 character as opposed to marked as bold, as this is pretty much
 equivalent of the following case:

 aa*bb*aa

 I could make the previous text so it says:
 文字 *太字* 文字 (aa *bb* aa)

 inserting space between them. But this means that space gets exported.
 I'm curious if there are any way I can tell Org-mode yes there's a
 space here so you know where to separate but do not treat like so when
 you are exporting.

 If there are any suggestions, that will be helpful!

 Cheers,

 Hideki Saito hide...@gmail.com
 http://goo.gl/ErBLy

If I understand you correctly these may help you:
http://www.mail-archive.com/emacs-orgmode@gnu.org/msg45926.html
http://www.mail-archive.com/emacs-orgmode@gnu.org/msg37638.html
http://www.mail-archive.com/emacs-orgmode@gnu.org/msg59490.html

---
WBR, Vladimir Lomov


-- 
Just because you're paranoid doesn't mean they AREN'T after you.



[O] Ignore following space coding?

2013-04-22 Thread Hideki Saito
Hello,
I briefly searching the list and but I'm unsure if this was discussed
before, so excuse me if this was discussed before.

I've got a question regarding how I can make this work with languages
that doesn't separate words with spaces.

The problem is if I'm trying to write:
文字*太字*文字

This essentially prevents text surrounded by * treated as a regular
character as opposed to marked as bold, as this is pretty much
equivalent of the following case:

aa*bb*aa

I could make the previous text so it says:
文字 *太字* 文字 (aa *bb* aa)

inserting space between them. But this means that space gets exported.
I'm curious if there are any way I can tell Org-mode yes there's a
space here so you know where to separate but do not treat like so when
you are exporting.

If there are any suggestions, that will be helpful!

Cheers,

Hideki Saito hide...@gmail.com
http://goo.gl/ErBLy