El Martes, 12 de Abril de 2005 19:49, Randy McMurchy escribi�: > I removed the [para] tags wrapping the [screen] tags because of what > the BLFS Editor's Guide says:
Like you said, using <screen> inside a <para> is redundant due that both tags creates their own text blocks. > "screen -- This creates a 'verbatim' environment that allows spacing > to be controlled. Mainly used as it simulates a console. It should > not be encapsulated by [para] unless unscreened text is present." <literallayout> has the same efecct but without the gray background. Is the equivalent to <pre> in HTML. > Another point I was trying to make is that the [userinput] tag > was used as there is stuff in the section that is input by the user. That is the correct use. > However, looking at the Editor's Guide, [userinput] is used mainly > to encapsulate [command] tags. That is a legacy tags style for when using the DSSSL stylesheets. In older versions (i.e., at BLFS 1.0) <userinput> was rendered by the DSSSL as bold, but newest DSSSL and XSL versions render it as normal. In LFS that was fixed hacking the lfs.dsl file (and now via CSS code), but in BLFS was decided to add <command> tags. That is the reason to use diferent command blocks tagging in LFS than BLFS. -- Manuel Canales Esparcia Usuario de LFS n�2886: http://www.linuxfromscratch.org LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.com TLDP-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-book FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
