From owner-freebsd-doc@FreeBSD.ORG Wed Jul 24 08:35:14 2013 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 76B65721 for ; Wed, 24 Jul 2013 08:35:14 +0000 (UTC) (envelope-from gabor.kovesdan@gmail.com) Received: from mail-ea0-x236.google.com (mail-ea0-x236.google.com [IPv6:2a00:1450:4013:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0D11421E0 for ; Wed, 24 Jul 2013 08:35:13 +0000 (UTC) Received: by mail-ea0-f182.google.com with SMTP id o10so75441eaj.27 for ; Wed, 24 Jul 2013 01:35:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=PTTNwo3gzA/W/vHNFYNuP1pFzPBESVF1vpYyvj1e9T8=; b=i+AEC35w0hgMj5oUBGJ5Okd3vOPgnd7Pxo1RX5Lb9x3ye4FOGlvqlen/oLz9sIeoRq CmjCEp+qs0NgM5GlWAcqsV//Ou8xly7ocsx1O7/umAqqB+cxK2bUB1HUVyGoNfwdnIiM PqwTRm56RJVT5EK/pLmNqcDQX8XZY/K836DUEdD4tp1Ho+Yq9clj7wC0ztAB/uSCH6El klYUJzlUTPg7zbcJ6fgCcFvgHH9+9hI1nGpZlCQGUc+rtG1FxLvBlZabGJeBpIs/BDmU JFrH/yBstXNf2qVSnA0YWFGp3NRuMiRRGY78UmkV3Hks28d2hCIFn2AgIvEnoODe0Ehc ectg== X-Received: by 10.15.93.134 with SMTP id w6mr36628301eez.25.1374654912341; Wed, 24 Jul 2013 01:35:12 -0700 (PDT) Received: from [192.168.1.117] (catv-80-99-23-232.catv.broadband.hu. [80.99.23.232]) by mx.google.com with ESMTPSA id l42sm64291978eeo.14.2013.07.24.01.35.10 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 24 Jul 2013 01:35:11 -0700 (PDT) Message-ID: <51EF91B1.7020400@FreeBSD.org> Date: Wed, 24 Jul 2013 10:34:57 +0200 From: Gabor Kovesdan User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0a2 MIME-Version: 1.0 To: Warren Block Subject: Re: CFR: documentation rendered in PDF with FOP References: <51EE8750.7040208@FreeBSD.org> <51EF0A9D.8060109@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FBSD Doc project X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jul 2013 08:35:14 -0000 On 2013.07.24. 1:28, Warren Block wrote: > On Wed, 24 Jul 2013, Gabor Kovesdan wrote: > >> On 2013.07.23. 23:11, Warren Block wrote: >> >>> There is something weird about bulleted lists and sub-lists, >>> starting on page 35 of the PDF Handbook (page 7-9 of the content). >>> Some entries in the first list are blank, the ones in the second >>> list have an extra linefeed after the bullet. >> It is a known issue and is actually the result of misplaced >> indexterms, not a bug in the rendering. I've already fixed some of >> them in the English docs but translations still has to be fixed and >> there may be slightly different cases, which I haven't caught yet. We >> should document in fdp-primer that indexterms should be put right >> inside of the text after the referred word. Not between paragraphs, >> not into , not into but right inside >> after the referred word without leaving a single a space. If they are >> not in , it can cuase such problems. And if you put a space >> before the indexterm, there may be a page break and you get a wrong >> page number in the index. But the probability of this latter is very >> low, the former thing is more important. > > Presently, indexes and indeterms are not even mentioned in the FDPP. > I'll start a list of things to add after the doc slush. If you or > anyone else have found things which are not documented well or at all > in the FDPP, please let me know or enter a PR. Thanks! Some more guidelines on indexing would be useful. I'm unsure about the actual conventions, probably we should consult some bibliography. I'm thinking of some hints on what to index. We currently index company names. Should we do it or just technical terms? Shall we index acronyms or the full term and add a see entry for the former ones? How should we use secondary terms? As for translations, I think that indexterms should be translated if the term is translated in the body text but currently it is not always done. We should clarify these questions. Gabor