From: Ruijie Yu via "General discussions about Org-mode." <emacs-orgmode@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Emacs Org Mode <emacs-orgmode@gnu.org>,
Timothy <orgmode@tec.tecosaur.net>
Subject: Re: [orgweb/zh-CN] [DRAFT PATCH] Tentative zh-CN translation
Date: Wed, 12 Apr 2023 00:39:25 +0800 [thread overview]
Message-ID: <sdvcz4az690.fsf@fw.net.yu> (raw)
In-Reply-To: <87a5zeu136.fsf@localhost>
Hello Ihor,
Thanks for your response. I made some changes accordingly, which can be
found here: https://git.sr.ht/~ruijieyu/orgweb/tree/translate/zh-CN--v2 .
More responses inline below.
Ihor Radchenko <yantar92@posteo.net> writes:
> Ruijie Yu via "General discussions about Org-mode."
> <emacs-orgmode@gnu.org> writes:
>
>> This is a tentative patchset for orgweb zh_CN translation.
>
> Thanks!
>
>> * How do I change the heading for the footnote section? In
>> particular, can I set it in a file- or dir-local variable, or in the
>> setup.org file? This is needed for _fully_ translating
>> /quickstart.org.
>
> You just need to use #+language: zh-CN (note dash).
Thank you, that fixes it. I am therefore updating all traces of "zh_CN"
into "zh-CN".
>> * Is translating /elpa.org worth it? I presume not, because part of
>> it describes the use of the now-deprecated Org Elpa repository.
>
> This page is, AFAIK, not referenced anywhere. And obsolete. No need to
> bother.
Noted. I therefore made zh-CN/elpa.org a symlink.
>> * I noticed that /resources/postamble.html is unused in all languages.
>> Should it be deleted?
>
> It is used in every single html. See /publish.sh.
Got it. I have hence added my translation of postamble.html, and
slightly modified publish.sh so that it makes use of the translation.
>> * I have added additional notes regarding zero-width spaces, because
>> CJK languages rarely use spaces whereas markups need them. I
>> presume this is an acceptable addition.
>> + This addition would also be helpful for when _eventually_ the
>> Japanese version is updated or some other CJK language is added.
>
> You can also link to https://orgmode.org/manual/Escape-Character.html
Got it.
>> * I left the changes in a series of commits, each handling one file --
>> please let me know if I should squash them into fewer commits.
>> Alternatively, let me know if I should push this to some online Git
>> repo.
>
> Series of commits is ok.
I have decided to push the changes to an unlisted cloned project on
sourcehut (https://sr.ht/~ruijieyu/orgweb), since otherwise I would have
to generate the patchset in every iteration, and attach the files to
emails _one by one_ on mu4e. Let me know if you need me to attach the
patchset to keep a trace on the ML -- it takes me a while but I can do
it.
>> * Please let me know if there are any guidelines for commit messages
>> which I should follow.
>
> See https://orgmode.org/worg/org-contribute.html#commit-messages
Tried to abide, please confirm.
>> * I think the "#+description:" portion of each *.org file can be just
>> moved into setup.org? That way we don't duplicate it twenty times.
>
> Agree.
Noted. I did not touch the descriptions outside of zh-CN; please let me
know if I should.
>> * There are hyperlinks which link to sites unreachable from mainland
>> China. I have marked them as "external sites" (外网) for now, but I
>> wonder if I should look for equivalent sites accessible from within
>> mainland China.
>
> It will be useful to add alternative websites in Mandarin/Cantonese as a
> secondary link.
Sounds good, will do on my next iteration. One more question: should I
add the secondary link next to the primary link, or should I add them as
footnotes?
> You should not assume that all the Chinese users experience the same set
> of blocked websites. Different provinces have slightly varying rules,
> the rules change with time, and Hong Kong in particular is not likely to
> block much. Not to mention VPN.
Yes, I understand, as I have had first-hand experience on the
aforementioned differences. What I have observed is that Wikipedia and
Google are the two main sites that came to my mind which are universally
blocked from mainland China, both of which are referenced in some degree
in the English version. And at least in the case of Wikipedia, I offer
to look for alternative sites because the task should be relatively easy
for me.
[And small nit, Hong Kong is not a province but a S.A.R. :) ]
>> * When translating /index.org, I noticed that, within the first
>> section, the spacing between the icons and their texts (e.g., the
>> rocket icon and its accompanying text "quickstart") in
>> /zh_CN/index.org are smaller than that of /index.org. I don't know
>> if it is because I unintentionally changed something that caused
>> this.
>
> Timothy, may you take a look?
On second look, this may just be because I ran `C-c C-e h h'. I tried
to run this command on the English site, and the generated site also
behaves like what I described above.
I am curious about the differences between `C-c C-e h h' and publish.sh.
I didn't run publish.sh because I don't think the publish script should
be run locally as-is, since it contains hardcoded paths.
>> * Should I mark English links as "English", and if so, how
>> aggressively should I mark them? Or do you think it is too
>> distracting for readers? I ask because there are some links in /ja
>> that are marked as "English".
>
> I am not sure here. I suggest asking other Chinese users about how
> useful it is.
>
>> - Chinese speakers
>> * Please check for consistency on all major terminologies. The
>> translation was done during a long timespan, and I may have
>> unintentionally chosen different words for the same term on
>> different days.
>>
>> * Please suggest alternative translations for various portions if you
>> see fit. There were some portions where I _struggled_ to come up
>> with sound translations.
>
> You may also ask at https://emacs-china.org/
Thanks, I visited it once but had since forgotten about it. I will post
the three questions above there within the next few days and hopefully
get some feedback about them.
--
Best,
RY
next prev parent reply other threads:[~2023-04-11 17:20 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 ` Ruijie Yu via General discussions about Org-mode. [this message]
2023-04-15 16:01 ` [orgweb/zh-CN] [DRAFT PATCH] Tentative zh-CN translation 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.
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=sdvcz4az690.fsf@fw.net.yu \
--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).