emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: ST <smntov@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Localized org-mode
Date: Tue, 08 May 2018 20:21:42 +0200	[thread overview]
Message-ID: <87bmdqrosp.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <1525801068.2021.56.camel@gmail.com> (ST's message of "Tue, 08 May 2018 20:37:48 +0300")

ST <smntov@gmail.com> writes:

> Why? Run "detranslator" before you start parsing. I.e. based on your
> 1-to-1 vocabulary "detranslator" will substitute all :EIGENSCHAFTEN: and
> all other org syntax back to English :PROPERTIES: etc.. Then apply
> parser as usual.

You cannot blindly replace all ":EIGENSCHAFTEN:" with ":PROPERTIES:"
because some of them could be real ":EIGENSCHAFTEN:", which is valid
syntax. IOW, you need to parse the buffer to know what ":EIGENSCHAFTEN:"
ought to be replaced, so you're running in circles.

> Writing is only a half of the problem. Imagine Cyrillic or Chinese text
> mixed with Latin letters. Org is not html (that hides its syntax once
> rendered) and it is supposed to be smoothly readable in raw plain texta
> form. Even worth - imagine right-to-left texts like Hebrew or Persian
> mixed up with left-to-right Latin letters. It's not aesthetical.

If that's an aesthetic issue, we could fix it on the aesthetic side.

For example, you can localize timestamps with `org-display-custom-times'
and `org-time-stamp-custom-formats'. It could be possible to do
something similar, i.e., to use overlays, e.g., on top of properties
drawers. Of course, this wouldn't change the underlying appearance, but
the solution is much less invasive than what you suggest.

Do you want to propose a patch?

  reply	other threads:[~2018-05-08 18:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 13:02 Localized org-mode ST
2018-05-08 14:10 ` Nicolas Goaziou
2018-05-08 17:37   ` ST
2018-05-08 18:21     ` Nicolas Goaziou [this message]
2018-05-09  7:45       ` ST
2018-05-09  8:19         ` Nicolas Goaziou
2018-05-09 11:36           ` Diego Zamboni
2018-05-09 12:07             ` Kaushal Modi
2018-05-09 12:43               ` Jean-Christophe Helary
2018-05-09 13:25                 ` Nicolas Goaziou
2018-05-09 13:48                   ` Jean-Christophe Helary
2018-05-09 15:41                     ` Diego Zamboni
2018-05-09 23:36                       ` Jean-Christophe Helary
2018-05-09 20:28                 ` Kaushal Modi
2018-05-11 22:23                 ` Göktuğ Kayaalp
2018-05-12  0:29                   ` Jean-Christophe Helary
2018-05-12 11:07                     ` Göktuğ Kayaalp
2018-05-12 11:58                       ` Jean-Christophe Helary
2018-05-12 19:24                   ` ST
2018-05-12 22:48                     ` Göktuğ Kayaalp
2018-05-12 23:48                       ` Jean-Christophe Helary
2018-05-09 12:34             ` ST
2018-05-21 14:44 ` Rasmus

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=87bmdqrosp.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=smntov@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).