From docs-return-12866-archive-asf-public=cust-asf.ponee.io@httpd.apache.org Thu Sep 27 22:55:03 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 34F23180675 for ; Thu, 27 Sep 2018 22:55:03 +0200 (CEST) Received: (qmail 21659 invoked by uid 500); 27 Sep 2018 20:55:02 -0000 Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: docs@httpd.apache.org List-Id: Delivered-To: mailing list docs@httpd.apache.org Received: (qmail 21649 invoked by uid 99); 27 Sep 2018 20:55:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Sep 2018 20:55:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id D85031A020A for ; Thu, 27 Sep 2018 20:55:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3 X-Spam-Level: *** X-Spam-Status: No, score=3 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id nAkIsxCTlc5l for ; Thu, 27 Sep 2018 20:55:00 +0000 (UTC) Received: from smtp.smtpout.orange.fr (smtp09.smtpout.orange.fr [80.12.242.131]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 97F395F300 for ; Thu, 27 Sep 2018 20:54:59 +0000 (UTC) Received: from [192.168.1.41] ([90.126.241.217]) by mwinf5d69 with ME id gkus1y00L4i89ZE03kutBb; Thu, 27 Sep 2018 22:54:53 +0200 X-ME-Helo: [192.168.1.41] X-ME-Date: Thu, 27 Sep 2018 22:54:53 +0200 X-ME-IP: 90.126.241.217 Subject: Re: svn commit: r1793922 - in /httpd/httpd/branches/trunk-override-index/docs/manual: index.xml mod/core.xml mod/overrides.xml sitemap.xml style/css/manual.css style/modulesynopsis.dtd style/xsl/common.xsl style/xsl/overrideindex.xsl References: <20170504225359.8B31E3A3B85@svn01-us-west.apache.org> <3d60f063-3546-ff51-22b9-8f6a7f0b227f@wanadoo.fr> <18356dd5-a39b-f37f-0d21-01a51d2a9b4f@wanadoo.fr> To: docs@httpd.apache.org From: Christophe JAILLET Message-ID: <6f5e686e-c6a8-5bf0-86fd-2bcbbe9b3629@wanadoo.fr> Date: Thu, 27 Sep 2018 22:54:51 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------F96E5EBF7BA0C4E72B879348" Content-Language: en-US --------------F96E5EBF7BA0C4E72B879348 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Le 27/09/2018 à 21:43, Jacob Champion a écrit : > On Thu, Sep 27, 2018, 1:10 AM Christophe JAILLET > > > wrote: > > So, if we want to use either XSLT engine, we should avoid this > functionality. > > > I'm not an XSLT expert, but it seems like trying to maintain > compatibility for both XSLT 1.0 and 3.0 simultaneously could be a > serious pain. If we're updating the toolchain, is it time to also > update the XSLT version we've standardized on? > > --Jacob > +1 All warnings/error generated by Saxon are now fixed on trunk and are compatible with Xalan, except this EXSLT issue. We'll need to move forward and use Java 9+ one day. The bug in (the un-maintained) Xalan, will stop us, unless we find a work-around. Switching to UTF-8 is apparently a solution. Using another (maintained) XSLT engine is another approach. Would be +1 for the latter. CJ --------------F96E5EBF7BA0C4E72B879348 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit
Le 27/09/2018 à 21:43, Jacob Champion a écrit :
On Thu, Sep 27, 2018, 1:10 AM Christophe JAILLET <christophe.jaillet@wanadoo.fr> wrote:

So, if we want to use either XSLT engine, we should avoid this functionality.


I'm not an XSLT expert, but it seems like trying to maintain compatibility for both XSLT 1.0 and 3.0 simultaneously could be a serious pain. If we're updating the toolchain, is it time to also update the XSLT version we've standardized on?

--Jacob

+1

All warnings/error generated by Saxon are now fixed on trunk and are compatible with Xalan, except this EXSLT issue.

We'll need to move forward and use Java 9+ one day. The bug in (the un-maintained) Xalan, will stop us, unless we find a work-around.

Switching to UTF-8 is apparently a solution.
Using another (maintained) XSLT engine is another approach.

Would be +1 for the latter.

CJ


--------------F96E5EBF7BA0C4E72B879348--