Caminiti, with assistance from Juan Molina. Thanks!
Submitted by: Federico Caminiti <demian.fc@gmail.com>
Differential Revision: https://reviews.freebsd.org/D3825
- comparing 'Linux' vs 'FreeBSD' is comparing apples and fruit: one is
just the kernel and the other is a specific distribution.
- the license 'debate' is well covered elsewhere
- it still references CVS
- comparing the development style of '300 committers' vs 'going through
the maintainer' is a straw man and doesn't reflect how Linux works (or
how BSD works)
- the supported platforms list is old and incorrect
- the "Extensible Frameworks" section belongs elsewhere
- the 'security' section is a feature list, not a comparison and is
missing important features
etc.
Discussed with: mjg
If I understand correctly the build broke because the non-english articles
import from the english version of fbsd-from-scratch.
Remove the translated articles for the articles I removed in English
As remko@ assign this to me:
Implement a quick-and-dirty solution to fix a broken link on the Spanish
version of the website and link to the Spanish send-pr.html.
The Spanish version of the website has not seen an update since 2010
therefore most changes since then are either not available or are broken.
The send-pr web form is still working though. Tested with PR www/187222.
- Replace /XML/{doc,www}/ with /XML/ in SysId.
- Remove empty stylesheets in share/xsl and point share/xml/empty.xsl via
XML catalog instead.
- Change the L10N layer in freebsd-*.xsl not to use localized XSLT
stylesheets directly.
- Move share/xsl/* to share/xml and remove share/xsl.
- Remove obsolete share/web2c/pdftex.def.
now picked up via share/xsl/*.xsl and they are empty when there is no
localized content in it. This prevents inconsistency between share/xsl/*.xsl
and the localized ones.
picked up via XML catalog in freebsd50.ent or xhtml10-freebsd.dtd,
not entities.ent. The L10N entities always come first to be able to
override everything.
- Define as   in EUC-JP encoding. This is a workaround to
prevent an invalid character in EUC-JP caused by converting 0xa0 in
UTF-8 (EUC-JP does not allow 0xa0) in XSLT processing. Theoretically
it should be   still in the final XML output.
- Make XML catalog resolution consistent for l10n.ent. This should be
revisited for the others later.
element but into a deeper paragraph, optimally right after the
referenced word without spaces even [1] but somehow the schema allows
badly nested indexterms. Correct such entires in the whole documentation
set.
- Add constraints to check for invalid indexterm entries.
See also: http://www.sagehill.net/docbookxsl/GenerateIndex.html#Indexterms [1]
some tools. (Either removed if the affected text has been removed
from the English version or moved into parentheses.)
- Add constaints to avoid programlisting, screen and footnote in tables.
