This is an automated email from the ASF dual-hosted git repository.

scantor pushed a commit to branch xerces-3.3
in repository https://gitbox.apache.org/repos/asf/xerces-c.git

commit 31b4b3a06105dcd607db9fda9d1883ad7e489bfe
Author: Scott Cantor <canto...@osu.edu>
AuthorDate: Mon Sep 30 13:28:29 2024 -0400

    Fix Docbook errors.
---
 doc/program-others.xml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/program-others.xml b/doc/program-others.xml
index 89a2ac182..89facf5d9 100644
--- a/doc/program-others.xml
+++ b/doc/program-others.xml
@@ -721,21 +721,21 @@ 
parser->getDomConfig()->setParameter(XMLUni::fgXercesSchema, doSchema);
     <anchor name="EntityResolution"/>
     <s2 title="Entity Resolution and NetAccessors">
 
-        <p><strong>All Xerces applications that wish to limit a wide range of 
security risks MUST install
+        <p>All Xerces applications that wish to limit a wide range of security 
risks MUST install
         appropriate implementations of API-specific "entity/resource 
resolution" implementations to
-        govern/police the resolution of external entities by the 
parser.</strong>
+        govern/police the resolution of external entities by the parser.
         </p>   
 
         <p>In the event that an entity resolver wants to delegate the job of 
resolving a particular resource
         to the parser, Xerces will automatically handle local file references 
but will delegate any non-local
-        file URLs to a <em>NetAccessor</em>, a plugin controlled at build time 
supporting access to remote
+        file URLs to a NetAccessor, a plugin controlled at build time 
supporting access to remote
         systems. Most of the built-in implementations are limited, with the 
principal exception of support
-        for <a href="https://curl.haxx.se";>libcurl</a> as an implementation, 
which supports a wide range
+        for <jump href="https://curl.haxx.se";>libcurl</jump> as an 
implementation, which supports a wide range
         of protocols, potentially including http over TLS, which is rarely 
supported in other cases.</p>
 
         <p>It is incredibly important to implement your own entity resolution 
code to ensure that if you
         allow the parser to perform its own resolution, it does so only under 
conditions and against URLs
-        you trust. The library will <strong>NOT</strong> your application from 
the many potential threats
+        you trust. The library will NOT your application from the many 
potential threats
         arising from arbitrary resource resolution.</p>
 
         <p>Notably, entity/resource resolver implementations can be 
accompanied by changing the default


---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org

Reply via email to