Path: csiph.com!usenet.pasdenom.info!goblin2!goblin.stu.neva.ru!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.004 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'subject:: [': 0.04; '(at': 0.04; 'lines,': 0.07; 'modify': 0.07; 'messing': 0.09; 'repeated': 0.09; 'structure,': 0.09; 'toc': 0.09; 'jan': 0.12; 'template': 0.14; 'changes': 0.15; 'copied.': 0.16; 'from:addr:torriem': 0.16; 'from:name:michael torrie': 0.16; 'losing': 0.16; 'subject:non': 0.16; 'language': 0.16; 'wrote:': 0.18; 'wed,': 0.18; 'bit': 0.19; 'basically': 0.19; 'file,': 0.19; 'mechanism': 0.19; 'subject:] ': 0.20; 'import': 0.22; 'putting': 0.22; 'separate': 0.22; 'header :User-Agent:1': 0.23; "aren't": 0.24; 'convenient': 0.24; 'tend': 0.24; 'file.': 0.24; 'chapter': 0.26; 'least': 0.26; 'header:In- Reply-To:1': 0.27; 'installed': 0.27; 'michael': 0.29; 'chris': 0.29; 'am,': 0.29; 'document.': 0.30; 'along': 0.30; 'discovery': 0.31; 'embedding': 0.31; 'markup': 0.31; 'styles': 0.31; 'subject:programs': 0.31; 'up:': 0.31; 'file': 0.32; 'this.': 0.32; 'front': 0.32; 'another': 0.32; 'open': 0.33; 'plain': 0.33; 'style': 0.33; 'table': 0.34; 'maybe': 0.34; 'subject:from': 0.34; 'but': 0.35; 'add': 0.35; 'templates': 0.36; 'similar': 0.36; 'should': 0.36; 'too': 0.37; 'project': 0.37; 'being': 0.38; 'message-id:@gmail.com': 0.38; 'to:addr:python-list': 0.38; 'files': 0.38; 'does': 0.39; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'how': 0.40; 'even': 0.60; 'read': 0.60; 'full': 0.61; 'simply': 0.61; 'times': 0.62; 'more': 0.64; 'linked': 0.65; 'believe': 0.68; 'content,': 0.68; 'clearer': 0.84; 'composing': 0.84; 'partially': 0.84; 'ram,': 0.84; 'divided': 0.91; 'subject:free': 0.91 X-Virus-Scanned: amavisd-new at torriefamily.org Date: Tue, 07 Jan 2014 10:10:04 -0700 From: Michael Torrie User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.12) Gecko/20130105 Thunderbird/10.0.12 MIME-Version: 1.0 To: python-list@python.org Subject: Re: [way OT] Migrating from non-free programs to LibreOffice References: <7wfvp2gg6v.fsf_-_@benfinney.id.au> <52CC2F0F.8040703@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 44 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1389114633 news.xs4all.nl 2861 [2001:888:2000:d::a6]:60674 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:63440 On 01/07/2014 09:58 AM, Chris Angelico wrote: > On Wed, Jan 8, 2014 at 3:45 AM, Michael Torrie wrote: >> I tend to add my own [styles] >> for quotes, captions, etc. After composing the document, >> then you modify the styles to set the spacings, fonts, indentations, >> border lines, etc. The workflow is very similar to using LyX, or even a >> plain markup language for that matter. > > That's all very well when you put everything into a single file, but > how do you manage those styles across a multi-file book? Mum's project > was partially rescued by the discovery that you can import styles from > another document, but that's still unworkable for repeated edits. Sorry should have been clearer on this. I do use multiple documents with LO with a master document. The table of contents can even be generated across documents. I believe my TOC is in my master document, along with the front matter. As for styles, basically you create a master template style that you use as a basis for each of your files (master document as well as the subdocuments). I make all my changes to the master template style and then when I open the various documents LO will update the templates. They aren't linked templates per se; they are copied. But the mechanism works okay, if a bit clunky. > >> The weakest part of LibreOffice is embedding images. > > And that's why this particular book is being divided up: it's full of > images. Putting the whole thing into a single file makes that file way > way too big to work with (at least on the computer Mum's using - it's > X times larger than her installed RAM, so Writer is constantly > hammering the page file), and there's no convenient way to read in > only part of the file. Hence my recommendation of a markup system like > LaTeX that simply *references* images, and which deliberately isn't > WYSIWYG; plus, having the concept of content, structure, and style all > separate means it's not difficult to build just one file - maybe not > even a whole chapter - while still being confident that all pages > reference the same styles. LO does reference images if you would like. But I find embedding the whole works is just more self-contained. And with multiple file documents the chances of losing data or messing with pagination are contained to individual sections.