From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: help-gnu-emacs@gnu.org
Subject: Re: [ANN] org-tchanges.el
Date: Mon, 13 May 2024 09:49:35 +0100 [thread overview]
Message-ID: <87seym2j1c.fsf@ucl.ac.uk> (raw)
In-Reply-To: 86zfsv1phu.fsf@gmx.net
On Sunday, 12 May 2024 at 12:33, James Thomas wrote:
> Just want to let you know of a (small) package I made for org users to
> collaborate easily with users of Word Processing (Office) software .docx
> files; using its 'track changes' feature.
>
> https://codeberg.org/quotuva/org-tchanges
This looks potentially quite useful. Couple of questions:
1. Is there an expected route to creating the .docx file from the .org
file that ensures that the changes are represented accurately?
2. What is a "tooltip" in an org file?
Thank you,
eric
--
Eric S Fraga via gnus (Emacs 30.0.50 2024-03-25) on Debian 12.0
next prev parent reply other threads:[~2024-05-13 8:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-12 7:03 [ANN] org-tchanges.el James Thomas
2024-05-13 8:49 ` Eric S Fraga [this message]
2024-05-13 22:37 ` [ANN] org-tchanges.el: Collaborate with Office (docx) users using 'track changes' James Thomas
2024-05-14 8:07 ` Eric S Fraga
2024-05-14 20:24 ` tpeplt
2024-05-14 21:58 ` James Thomas
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87seym2j1c.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=help-gnu-emacs@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.
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).