From: Ruijie Yu via "General discussions about Org-mode." <emacs-orgmode@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Timothy <orgmode@tec.tecosaur.net>, emacs-orgmode@gnu.org
Subject: Re: [orgweb/zh-CN] [DRAFT PATCH] Tentative zh-CN translation
Date: Sun, 16 Apr 2023 23:12:30 +0800 [thread overview]
Message-ID: <sdv4jpf3lhf.fsf@netyu.xyz> (raw)
In-Reply-To: <875y9wt298.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
> Ruijie Yu via "General discussions about Org-mode."
> <emacs-orgmode@gnu.org> writes:
>
>> I underwent a (painfully long) process of git magickery so that each
>> "translation" commit only _translates_ a file, instead of adds a brand
>> new file with brand new contents. This means reviewers can have an
>> easier time to just review the diff without needing to look back and
>> forth between two files.
>
> Thanks!
>
>> + <asside class="right" style="position: relative; z-index: -1">
>> + <h4>概述显示</h4> <!-- TODO: I don't know if this is the best way to phrase it -->
>
> I'd look into, for example, how Chinese version of WPS office names outlines.
Thanks, installing it now and will take a look.
> Also, I noticed that in tools.org you changed
>
> -org-mode-parser
> +/org-mode-parser/
>
> This probably belongs to the English version as well.
Should the English version change belong to a new commit, unrelated to
the translation patchset? Or would I just modify it in the same commit
where I translate zh-CN/tools.org?
--
Best,
RY
next prev parent reply other threads:[~2023-04-16 15:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 17:48 [orgweb/zh_CN] [DRAFT PATCH] Tentative zh_CN translation Ruijie Yu via General discussions about Org-mode.
2023-04-11 11:09 ` Ihor Radchenko
2023-04-11 16:39 ` [orgweb/zh-CN] [DRAFT PATCH] Tentative zh-CN translation Ruijie Yu via General discussions about Org-mode.
2023-04-15 16:01 ` Ruijie Yu via General discussions about Org-mode.
2023-04-16 12:55 ` Ihor Radchenko
2023-04-16 15:12 ` Ruijie Yu via General discussions about Org-mode. [this message]
2023-04-16 15:34 ` Ihor Radchenko
2023-04-21 2:33 ` [orgweb/zh-CN] [DRAFT PATCH v7] " Ruijie Yu via General discussions about Org-mode.
2023-04-22 14:31 ` Ihor Radchenko
2023-04-22 14:56 ` Ruijie Yu via General discussions about Org-mode.
2023-04-22 15:20 ` Ihor Radchenko
2023-04-23 0:48 ` Ruijie Yu via General discussions about Org-mode.
2023-06-13 12:04 ` Ihor Radchenko
2023-06-14 4:46 ` Ruijie Yu via General discussions about Org-mode.
2023-06-14 12:29 ` Ihor Radchenko
2023-12-08 14:37 ` Ihor Radchenko
2023-04-16 13:10 ` [orgweb/zh-CN] [DRAFT PATCH] " Ihor Radchenko
2023-04-16 14:04 ` Hanno Perrey
2023-04-16 15:04 ` Ruijie Yu via General discussions about Org-mode.
2023-04-16 15:17 ` Ruijie Yu via General discussions about Org-mode.
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=sdv4jpf3lhf.fsf@netyu.xyz \
--to=emacs-orgmode@gnu.org \
--cc=orgmode@tec.tecosaur.net \
--cc=ruijie@netyu.xyz \
--cc=yantar92@posteo.net \
/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).