From: Ihor Radchenko <yantar92@posteo.net>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] orgweb: Update org-ruby link (tools)
Date: Sun, 09 Jun 2024 11:51:49 +0000 [thread overview]
Message-ID: <87jziy2v1m.fsf@localhost> (raw)
In-Reply-To: <v440ti$vjf$1@ciao.gmane.io>
Max Nikulin <manikulin@gmail.com> writes:
> On 09/06/2024 02:18, Ihor Radchenko wrote:
>> Max Nikulin writes:
>>> ... I have tried to blindly update zh-CN file. Likely it should be
>>> done more accurately.
>>
>> Yes. Let's not fiddle with Chinese version. It is already out of sync,
>> but we cannot do much unless we get someone Chinese-speaking volunteer.
>
> Feel free to skip chunks you do not like.
Applied.
I retained the old description in the Chinese translation.
https://git.sr.ht/~bzg/orgweb/commit/96072c43b4a497f614f3bb4251da341b9df3b5b9
https://git.sr.ht/~bzg/orgweb/commit/29cbf1f4b433f6dc008aad1a71a9b60367740d33
>>> Would it be acceptable to add an additional link to the dedicated page
>>> on Worg?
>>> [[https://orgmode.org/worg/org-tutorials/org-ruby.html][Worg]]
>>
>> Yes, but I'd prefer if such link would be not just a text link, but
>> something more compact. Maybe something like "wiki" button on top-left
>> corner of the logo.
>
> I do not like and idea of a button over an active link.
>
> Since org-ruby has no its own logo I would consider 3 smaller links instead:
> - https://github.com/wallyqs/org-ruby with the github logo
> - https://rubygems.org/gems/org-ruby with the current gem icon
> - https://orgmode.org/worg/org-tutorials/org-ruby.html with styled
> "Worg" text.
I do not mind as long as the overall style remains consistent. Feel free
to submit a patch.
>> Note that the extended tools page on
>> https://orgmode.org/worg/org-tools/index.html already has the link you proposed.
>
> Formally it is more appropriate for
> https://orgmode.org/worg/org-translators.html "Org-mode Import/Export
> Tools". (I have no idea why this page is not in the org-tools folder.)
Historical, I guess.
We may move it, but I am not sure if it is a big deal.
> From my point of view, when a user sees the ruby icon nothing suggests
> that, besides clicking on the link, they may find additional info on a
> page linked from another page accessible through a link at the bottom of
> the current one.
That's true. On the other hand, tools page is not really a Wiki.
It is ok to put some links to the wiki/worg, but not at the cost of
information overloading.
--
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>
prev parent reply other threads:[~2024-06-09 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-08 16:25 [PATCH] orgweb: Update org-ruby link (tools) Max Nikulin
2024-06-08 19:18 ` Ihor Radchenko
2024-06-09 10:41 ` Max Nikulin
2024-06-09 11:51 ` Ihor Radchenko [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=87jziy2v1m.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@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).