From: Tim Cross <theophilusx@gmail.com>
To: Eric S Fraga <esflists@gmail.com>
Cc: org-mode-email <emacs-orgmode@gnu.org>,
Robert Klein <roklein@roklein.de>,
Sharon Kimble <boudiccas@skimble.plus.com>
Subject: Re: exporting to latex and docx not honouring carriage returns to tabbing
Date: Thu, 11 Oct 2018 08:06:10 +1100 [thread overview]
Message-ID: <87tvlt4im5.fsf@gmail.com> (raw)
In-Reply-To: <87murmnf2f.fsf@gmail.com>
Eric S Fraga <esflists@gmail.com> writes:
> On Wednesday, 10 Oct 2018 at 08:31, Tim Cross wrote:
>
> [...]
[...]
>
>
> And I highly recommend the koma-script classes as opposed to the default LaTeX ones. For Sharon, the scrreprt class may be what you want.
Yes, koma-script has been my default as well for some time now. I also
use the hitec style, which seems to go down well with the 'tech' crowd.
Around 80% of the time, people look at my documents and are blown away
because of how good they look (content, unfortunately, can vary
significantly!). The only time things become problematic is when a
decision is made to work on a document collaboratively and they want to
use 'track changes'. At this point, I try to convince them to just work
in plain text or org files and I take on the responsibility of
incorporating their changes. This works OK provided they are able to
just work with the org file (either as an org file or as just plain
text) and not get caught up in formatting etc, in which case I can
extract their changes with diff. However, too often, they just don't get
it or cannot resist and insist on changing the formatting without
changing the content, so diffs become less useful.
Tim
--
Tim Cross
next prev parent reply other threads:[~2018-10-10 21:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 9:56 exporting to latex and docx not honouring carriage returns to tabbing Sharon Kimble
2018-10-08 15:54 ` Eric S Fraga
2018-10-09 6:20 ` Robert Klein
2018-10-09 11:06 ` Sharon Kimble
2018-10-09 13:11 ` Eric S Fraga
2018-10-09 16:53 ` Sharon Kimble
2018-10-09 21:31 ` Tim Cross
2018-10-10 12:47 ` Eric S Fraga
2018-10-10 21:06 ` Tim Cross [this message]
2018-10-11 13:24 ` Sharon Kimble
2018-10-11 21:29 ` Tim Cross
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=87tvlt4im5.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=boudiccas@skimble.plus.com \
--cc=emacs-orgmode@gnu.org \
--cc=esflists@gmail.com \
--cc=roklein@roklein.de \
/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).