Checkout Tools
  • last updated 3 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix spelling errors in docs found by codespell. [skip ci]

  1. … 31 more files in changeset.
Use https instead of http when searching with Google.

PR 64058

Fixed by [stephane.blondon gmail.com]

Change 'removed again' to 'removed' as suggested at https://bz.apache.org/bugzilla/show_bug.cgi?id=60026

Happy New Year 2020

  1. … 2 more files in changeset.
Help doc writer to spot places where:

- a link to a directive from within its own <directivesynoptis> should be avoided

This link is now silently removed

- a link to a directive is missing

Try to give some context where to find this missing link

Fix a parsing error when using Ant 1.9.13 without the external Xerces (2.9.0) and Xalan (2.7.1).

The error is: "filter-expr(funcall(current, []), [pred(=(step("attribute", 39), literal-expr(section)))])'. Cause: Erreur lors de la vérification du type de l'expression 'filter-expr(funcall(current, []), [pred(=(step("attribute", 39), literal-expr(section)))])"

This takes us 1 step closer to use Ant 1.9+ and remove Xerces and Xalan from the build chain.

Patch tested with the current doc build chain (Ant 1.6.5 + Xerces + Xalan) on the 2.4.x branch.

Even if actually we don't have any "<Foo>" and "Foo" directives, I've checked that the doc is built correctly in such a case.

Fix typo
Add some additional tests to report badly formatted synopsis.

Comment-out these tests because of the noise it generates, but leave it there, if useful for s.o.

Quireference extract the default value of a directive from the <default> of the corresponding <directivesynopsis> block.

The current implementation expects <default> to be formated like:

directive_name default_value

If the directive name is not there, no default value can be extracted and it is missing in the quickreference table.

This commit adds a basic check to see if the formating looks correct. It catches cases where the directive name is omited or is misspelled.

If it generates too much noise, feel free to revert or improve :)

Give a littlet breath before the permalink
Happy New Year 2019

  1. … 2 more files in changeset.
ran `build bootstrap` and rebuild transformation. sorry for the noise.

  1. … 291 more files in changeset.
Spanish html doc files : UTF-8 encoding in order to get rid of HTML entities.
French html doc files : UTF-8 encoding in order to get rid of HTML entities.

  1. … 490 more files in changeset.
The XSLT Saxon engine warns about some "Ambiguous rule matches".

Use priority to remove the ambiguity.

The only rational for choosing "3" and "4" for these priorities, is that "4" is related to <h4> tags, and 3=4-1 for the previous level.

Tested with the actual Xalan XSL engine:

./build.sh all

with and without the change.

Outputs are exactly the same.

Revert r1842160

Some rules to help me detect un-needed links to directives, or missing ones were sent by error

The XSLT Saxon engine warns about some "Ambiguous rule matches".

Use priority to remove the ambiguity.

The only rational for choosing "3" and "4" for these priorities, is that "4" is related to <h4> tags, and 3=4-1 for the previous level.

Tested with the actual Xalan XSL engine:

./build.sh all

with and without the change.

Outputs are exactly the same.

The XSLT Saxon engine warns that match="@*" will return only attribute nodes, which can't have any attributes or child.

So simplify the xsl rules accordingly.

Tested with the actual Xalan XSL engine:

./build.sh all

with and without the change.

Outputs are exactly the same.

Fix properties, add missing html file

  1. … 69 more files in changeset.
Render <code> in bold in man pages, matching commonly used style in

both help2man and the standard DocBook XSL stylesheets for man output.

Align the regex with the one used in 2.4.x which gives nicer results.
New xsl file which generates ready to copy/paste strings for prettify(.min).js

All the directives are collected in some JS arrays, so that it is easier to upgrade the list

in prettify.js when new directives are added.

'build.sh' will be updated accordingly. A new build target ('prettify') will be added to

update this list. The resulting file is: docs/manual/list_for_prettify.txt

This new file is heavily inspired from convmap.xsl.

It should be possible to go further, but this is already a first step.

Add a permalink functionality to section and diective-section in the generated doc.

This is convenient and consistent with httpd.a.o

Getting a link to a section or a directive is already possible from the TOC, but having it available directly in-place is, IMHO, much more useful.

  1. … 11 more files in changeset.
common.xsl: update year to 2018 in the footer
synopsis.xsl: fix broken translation builds

This commit is a follow up of r1805189, in which

a new logic was added to allow to repeat a directive

name only if its type is different (like SSLPolicy

and <SSLPolicy>). The change broken french translations

since the $this variable, containing the translated

sections, was not used anymore.

The XPath code could surely be improved, but it seems

more pressing to allow our translators to get back

to their daily work without interference.

build.sh validate-* worked fine, as well as the build.sh fr

translation.

doc xsl/dtd: introduce idtype attribute for directivesynopsis

In r1805193 synopsis.xsl was changed to allow two directives

of different type (like <SSLPolicy> and SSLPolicy) to share

the same name but have different ids (and please validate-xml/xhtml).

The downside of this action was that all the quicklinks to

existing directive sections (like <If>, <VirtualHost>, etc..)

were changed, possibly breaking external clients already

referencing them.

This change introduces a new attribute in the directivesynopsis

DTD, namely 'idtype', that will be appended to 'name'

in the id generation by synopsis.xsl. This will rollback

link names to their previous values and will allow documentators

to fine tune directivesynopsis sections as they need

(for example we have recently introduced mod_md's

ManagedDomain/<ManagedDomain>, and modssl's SSLPolicy/<SSLPolicy>).

This approach seems more precise and less invasive to me.

Of course the name of the attribute can be changed later on

to whatever term would fit best, the main concern for me at

the moment is to restore the trunk documentation to its previous

state.

  1. … 1 more file in changeset.
common|synopsis.xsl: rename directive type=sections id generation

This commits is a follow up of r1805189 and it is meant

to allow directives with the same name but different type

to coexist in the same document without triggering errors

while executing validate-xhtml.

For example: mod_md.xml recently introduced the following:

* ManagedDomain

* <ManagedDomain> (this one is type=section)

In my opinion this is a perfectly valid use case and it should

be allowed/handled correctly by the doc generation process/validation.

In order to avoid clashing the directive ids will get a suffix

called "section" if type=section will be present as param.

Quicklinks, <directive> links have been updated to the new

scheme to avoid dandling pointers in the doc.

Comments/reviews are welcome, if I left something behind

please let me know.

synopsis.xsl: do not render two times the same

directive HTML if more than one

directive share the same name.

This has happened when mod_md.xml was introduced,

and the following directives shared the same name:

* ManagedDomain

* <ManagedDomain>

With the current code each time that a node needs

to be rendered it will emit a duplicate, ending up

in the above example with 4 sections rather than two.

Uniqueness of sections will be ensured by the HTML

elements ids, to avoid errors before committing for

example (accidental duplicates, etc..).

merge in the override index
  1. … 8 more files in changeset.
Happy New Year 2017

  1. … 2 more files in changeset.