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:17:56 +0800 [thread overview]
Message-ID: <sdvzg7726hh.fsf@netyu.xyz> (raw)
In-Reply-To: <87zg78rn13.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
> Ruijie Yu <ruijie@netyu.xyz> writes:
>
>>> 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.
>
> mu4e does not support multiple selection when attaching files? AFAIK,
> Emacs supports drag-and-drop for attachments.
Hanno provided additional hints on that, and I will try to use dired to
place attachments in my next iteration.
>>>> * 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.
>
> It will be a good idea.
I'll update all "#+description" fields outside zh-CN in a single,
separate commit, unless you have other ideas.
>>> 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?
>
> IMHO, it will make sense to have an immediately visible alternative
> link. So, secondary link will do. Or you may even make the Chinese link
> primary, as the one that is more likely to be useful.
Noted.
>> 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.
>
> Publishing is quite a bit different. For example, it tries hard to make
> the HTML anchors stable. There are other differences as well.
Got it. As evident from some of my other messages, I have therefore
switched over to using publish.sh because I want to be able to see how
exactly each page looks.
--
Best,
RY
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.
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. [this message]
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=sdvzg7726hh.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).