From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 815EAE00C15; Tue, 17 Jun 2014 05:55:04 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham version=3.3.1 X-Spam-HAM-Report: Received: from astoria.ccjclearline.com (astoria.ccjclearline.com [64.235.106.9]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 56348E00C0A for ; Tue, 17 Jun 2014 05:54:51 -0700 (PDT) Received: from [69.196.158.250] (port=47666 helo=crashcourse.ca) by astoria.ccjclearline.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1WwsuY-0003Od-Go for yocto@yoctoproject.org; Tue, 17 Jun 2014 08:54:50 -0400 Date: Tue, 17 Jun 2014 08:51:17 -0400 (EDT) From: "Robert P. J. Day" X-X-Sender: rpjday@localhost To: Yocto discussion list Message-ID: User-Agent: Alpine 2.11 (LFD 23 2013-08-11) MIME-Version: 1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - astoria.ccjclearline.com X-AntiAbuse: Original Domain - yoctoproject.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - crashcourse.ca X-Source: X-Source-Args: X-Source-Dir: Subject: any plans on more carefully distinguishing docbook markup in yocto docs? X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 12:55:04 -0000 Content-Type: TEXT/PLAIN; charset=US-ASCII i'm sure i asked this once before, but is there any long-term plan for more carefully marking up the yocto docs semantically? as in, most things that represent filenames or variables or commands or code are simply tagged as , even when this is not really appropriate. to be semantically precise, one should be more carefully selecting among tags such as , , , and so on. for now, i suspect the rendering toolchain wouldn't change what's eventually produced, but in the future, i think more careful markup would allow the generation of much prettier docs. thoughts? rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================