On 08/11/2011 06:44 AM, Philipp Hahn wrote:
Currently only tabs and blanks are used for tokenizing the description, which breaks when a term is at the end of a line or has () appended to it. 1. Use also other white space characters such as new-lines and carriage return for splitting. 2. Remove some common non-word characters from the token before lookup.
Signed-off-by: Philipp Hahn<hahn@univention.de> --- docs/newapi.xsl | 9 ++++++--- 1 files changed, 6 insertions(+), 3 deletions(-)
I am not fluent in reading xsl files. How would I go about testing if the output is more visually appealing? I can ack on the basis of comparison on before vs. after appearance, but only if I figure out which files are affected to compare a view in my browser of the generated html. My gut feel is that this is probably right, but unless someone more familiar with the file format speaks up, or unless I can test the results, I won't push this just yet. -- Eric Blake eblake@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org