From: James Thomas <jimjoe@gmx.net>
To: help-gnu-emacs@gnu.org
Subject: Re: [ANN] org-tchanges.el: Collaborate with Office (docx) users using 'track changes'
Date: Tue, 14 May 2024 04:07:06 +0530 [thread overview]
Message-ID: <86seylqqy5.fsf_-_@gmx.net> (raw)
In-Reply-To: <87seym2j1c.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Mon, 13 May 2024 09:49:35 +0100")
Eric S Fraga wrote:
> 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?
As I see it, you could first export it as barely as possible, but
because changes are made only afterward, to the exported version, it
shouldn't make much difference. Also, as mentioned, the ediff3 method
with the ancestor file could be used to hide common changes ('$$')
brought about by the reverse conversion, for more accuracy.
> 2. What is a "tooltip" in an org file?
I meant the 'help-echo' of the 'highlight'ed regions in the buffer. Also
accessible by C-h . (display-local-help) with point placed there.
Currently 'deletion' comments are removed, but I'm working on an
alternative that preserves that as well.
Regards,
James
next prev parent reply other threads:[~2024-05-13 22:37 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
2024-05-13 22:37 ` James Thomas [this message]
2024-05-14 8:07 ` [ANN] org-tchanges.el: Collaborate with Office (docx) users using 'track changes' 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=86seylqqy5.fsf_-_@gmx.net \
--to=jimjoe@gmx.net \
--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).