From: Ihor Radchenko <yantar92@posteo.net>
To: Cantoraz Chou <cantoraz@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Timestamp format during export (was: [BUG] [ox-odt] ODT export Chinese/Han script inserts unexpected spaces in each consecutive line)
Date: Sat, 14 Jan 2023 13:54:57 +0000 [thread overview]
Message-ID: <87k01pz0em.fsf@localhost> (raw)
In-Reply-To: <CAJg5Zf04PPHdkSiXx9x9dOBAFE3dL0Ge8YANDz==cwde_H-uoQ@mail.gmail.com>
Cantoraz Chou <cantoraz@gmail.com> writes:
> In my experience, most of weird troubles are related to the (1) language
> habit or (2) mixed use of Ideographs and alphanumeric.
>
> Eg. for (1).
>
> The Org export option keyword `DATE' use a fixed built-in timestamp
> format which is rarely used in Chinese. It's impossible to customize the
> format only for exporting, without touching format in Org.
>
> At present, I have to use a macro to format a Org timestamp to the
> string, that used for `DATE' keyword.
>
> It's best to provide a option/variable to set the timestamp format used
> in exported doc.
There is `org-time-stamp-custom-formats' variable, which is used when
exporting timestamps. Do you need a separate variable for export only
(that does not affect `org-display-custom-times')?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-01-14 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 3:49 [BUG] [ox-odt] ODT export Chinese/Han script inserts unexpected spaces in each consecutive line Cantoraz Chou
2023-01-13 8:20 ` Ihor Radchenko
2023-01-14 13:44 ` Cantoraz Chou
2023-01-14 13:54 ` Ihor Radchenko [this message]
2023-01-14 14:00 ` Pixel table alignment (was: [BUG] [ox-odt] ODT export Chinese/Han script inserts unexpected spaces in each consecutive line) Ihor Radchenko
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=87k01pz0em.fsf@localhost \
--to=yantar92@posteo.net \
--cc=cantoraz@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).