From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yujie Wen Subject: Re: How to remove spaces for soft line-breaks Date: Tue, 9 Jul 2013 13:23:31 +0800 Message-ID: References: <878v1hfoki.fsf@bzg.ath.cx> <51DB96F8.8060108@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=90e6ba3fcd7f9bb1ed04e10d5c9e Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49773) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UwQOl-0001Ex-Hw for emacs-orgmode@gnu.org; Tue, 09 Jul 2013 01:23:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UwQOi-0008A5-Pe for emacs-orgmode@gnu.org; Tue, 09 Jul 2013 01:23:35 -0400 Received: from mail-ie0-x233.google.com ([2607:f8b0:4001:c03::233]:56087) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UwQOi-00089t-Hu for emacs-orgmode@gnu.org; Tue, 09 Jul 2013 01:23:32 -0400 Received: by mail-ie0-f179.google.com with SMTP id c10so11328661ieb.24 for ; Mon, 08 Jul 2013 22:23:31 -0700 (PDT) In-Reply-To: <51DB96F8.8060108@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "emacs-orgmode@gnu.org Mode" --90e6ba3fcd7f9bb1ed04e10d5c9e Content-Type: text/plain; charset=ISO-8859-1 Hi, Christian, 2013/7/9 Christian Wittern > Hi Bastien, Yujie > > On 2013-07-08 17:22, Bastien wrote: > >> Hi Yujie, >> >> Yujie Wen writes: >> >> I am wondering whether there is a way to forbid such spaces, or if >>> no such a way, whether it is possible to work out a patch to forbid >>> it. >>> >> I would try M-x visual-line-mode RET and see if you like it. >> > Well, this will not solve the problem for the OP, which occurs during > export. > > What has to be done, I think, is to remove the CR/LF characters for > Chinese (and Japanese, Korean etc.) text when exporting to HTML, because > they will otherwise show up in the displayed HTML as single space > characters. > I used to thinking of removing CR/LF at the parsing or exporting stage. But now I think it is not a perfect solution since it will remove by mistake some meaningful spaces. For example, in an English/Chinese mixed texts whereas lines are sometimes broken at between two English words, which is often the case when we fill graphs with m-q. Discerning meaningful and meaningless spaces for Chinese and Japanese is rather too complicated a topic. Chinese rarely use spaces for separating words, Japanese sometimes use spaces for separating syntax elements. Korean, by my instinct at staring on Korean scripts, does use spaces to separate words. I guess, this requires either a derived custom export engine or a > internationalization framework that allows the specification of the text > language. > > Christian > > > -- > Christian Wittern, Kyoto > > > Regards, Yujie --90e6ba3fcd7f9bb1ed04e10d5c9e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi, Christian,

2013/7/9 Christian Wittern <cwittern@gmail.com>=
Hi Bastien, Yujie

On 2013-07-08 17:22, Bastien wrote:
Hi Yujie,

Yujie Wen <yjwen= .ty@gmail.com> writes:

I am wondering whether there is a way to forbid such spaces, or if
no such a way, whether it is possible to work out a patch to forbid
it.
I would try M-x visual-line-mode RET and see if you like it.
Well, this will not solve the problem for the OP, which occurs during expor= t.

What has to be done, I think, is to remove the CR/LF characters for Chinese= (and Japanese, Korean etc.) text when exporting to HTML, because they will= otherwise show up in the displayed HTML as single space characters.
I used to thinking of removing CR/LF at the parsing or ex= porting stage. But now I think it is not a perfect solution since it will r= emove by mistake some meaningful spaces. For example, in an English/Chinese= mixed texts whereas lines are sometimes broken at between two English word= s, which is often the case when we fill graphs with m-q.

Discerning meaningful and meaningless spaces for Chinese and= Japanese is rather too complicated a topic. Chinese rarely use spaces for = separating words, Japanese sometimes use spaces for separating syntax eleme= nts. Korean, by my instinct at staring on Korean scripts, does use spaces t= o separate words.

I guess, this requires either a derived custom export engine or a internati= onalization framework that allows the specification of the text language.

Christian


--
Christian Wittern, Kyoto



Regar= ds,
Yujie
--90e6ba3fcd7f9bb1ed04e10d5c9e--