From 81bd19a5f232c84993c48535068c1791e937accc Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Sun, 29 Oct 2017 17:04:53 +0200 Subject: Update project URLs to https:// --- doc/cxx/tree/guide/index.xhtml | 50 +++++++++++++++++++++--------------------- 1 file changed, 25 insertions(+), 25 deletions(-) (limited to 'doc/cxx/tree/guide/index.xhtml') diff --git a/doc/cxx/tree/guide/index.xhtml b/doc/cxx/tree/guide/index.xhtml index e2a860d..4731480 100644 --- a/doc/cxx/tree/guide/index.xhtml +++ b/doc/cxx/tree/guide/index.xhtml @@ -176,15 +176,15 @@

Permission is granted to copy, distribute and/or modify this document under the terms of the - GNU Free + GNU Free Documentation License, version 1.2; with no Invariant Sections, no Front-Cover Texts and no Back-Cover Texts.

This document is available in the following formats: - XHTML, - PDF, and - PostScript.

+ XHTML, + PDF, and + PostScript.

@@ -278,7 +278,7 @@ document is intended for C++ developers and software architects who are looking for an XML processing solution. For a more in-depth description of the C++/Tree mapping refer to the - C++/Tree + C++/Tree Mapping User Manual.

Prior experience with XML and C++ is required to understand this @@ -293,7 +293,7 @@ information useful:

@@ -1032,7 +1032,7 @@ hello (std::istream&);

For more detailed information on the --type-naming, --function-naming, --type-regex, and other --*-regex options refer to the NAMING - CONVENTION section in the XSD + CONVENTION section in the XSD Compiler Command Line Manual.

2.7 Generating Documentation

@@ -1144,7 +1144,7 @@ $ doxygen hello.doxygen distribution.

You can view the result of the steps described in this section - on the Hello + on the Hello Example Documentation page.

@@ -1161,7 +1161,7 @@ $ doxygen hello.doxygen handling of vocabularies that use XML Schema polymorphism, XML Schema to C++ namespace mapping, and thread safety. For more ways to configure the generated code refer to the - XSD + XSD Compiler Command Line Manual.

@@ -1213,7 +1213,7 @@ $ doxygen hello.doxygen your schemas with the --generate-polymorphic option to produce polymorphism-aware code. For more information on working with polymorphic object models, refer to - Section 2.11, + Section 2.11, "Mapping for xsi:type and Substitution Groups" in the C++/Tree Mapping User Manual.

@@ -1229,11 +1229,11 @@ $ doxygen hello.doxygen

The default mapping of namespace URIs to C++ namespaces can be altered using the --namespace-map and --namespace-regex compiler options. For example, - to map namespace URI http://www.codesynthesis.com/my to + to map namespace URI https://www.codesynthesis.com/my to C++ namespace cs::my, we can use the following option:

---namespace-map http://www.codesynthesis.com/my=cs::my
+--namespace-map https://www.codesynthesis.com/my=cs::my

A vocabulary without a namespace is mapped to the global scope. This @@ -1568,7 +1568,7 @@ class people_t overcome this limitation we can mark certain schema types, for which content order is not sufficiently preserved, as ordered. For more information on this functionality refer to - Section + Section 2.8.4, "Element Order" in the C++/Tree Mapping User Manual.

For complex schemas with many levels of nested compositors @@ -1895,7 +1895,7 @@ ps.push_back (std::move (jane_p)); // assumes ownership

For more information on the non-copying modifier functions refer to - Section + Section 2.8, "Mapping for Local Elements and Attributes" in the C++/Tree Mapping User Manual. The above application produces the following output:

@@ -1930,7 +1930,7 @@ ps.push_back (std::move (jane_p)); // assumes ownership the mapping of built-in XML Schema types to C++ types and how to work with them. This section provides an overview of the built-in types. For more detailed information refer - to Section + to Section 2.5, "Mapping for Built-in Data Types" in the C++/Tree Mapping User Manual.

@@ -2232,7 +2232,7 @@ ps.push_back (std::move (jane_p)); // assumes ownership fundamental or standard C++ types to map to. As a result, these types are implemented from scratch in the XSD runtime. For more information on their interfaces refer to - Section + Section 2.5, "Mapping for Built-in Data Types" in the C++/Tree Mapping User Manual.

@@ -2252,14 +2252,14 @@ ps.push_back (std::move (jane_p)); // assumes ownership to generate types for root elements instead of parsing and serialization functions. This may be useful if your XML vocabulary has multiple root elements. For more information on element types refer to - Section + Section 2.9, "Mapping for Global Elements" in the C++/Tree Mapping User Manual.

In this section we will discuss the most commonly used versions of the parsing functions. For a comprehensive description of parsing - refer to Chapter + refer to Chapter 3, "Parsing" in the C++/Tree Mapping User Manual. For the people global element from our person record vocabulary, we will concentrate on the following three parsing functions:

@@ -2474,7 +2474,7 @@ catch (const xml_schema::exception& e) error or warning message for each entry. For more information about this and other exceptions that can be thrown during parsing, refer to - Section + Section 3.3, "Error Handling" in the C++/Tree Mapping User Manual.

@@ -2536,7 +2536,7 @@ catch (const std::ifstream::failure&) generate types for root elements instead of parsing and serialization functions. This may be useful if your XML vocabulary has multiple root elements. For more information on element types refer to - Section + Section 2.9, "Mapping for Global Elements" in the C++/Tree Mapping User Manual.

@@ -2544,7 +2544,7 @@ catch (const std::ifstream::failure&)

In this section we will discuss the most commonly used version of serialization functions. For a comprehensive description of serialization refer to - Chapter + Chapter 4, "Serialization" in the C++/Tree Mapping User Manual. For the people global element from our person record vocabulary, we will concentrate on the following serialization function:

@@ -2679,7 +2679,7 @@ catch (const xml_schema::exception& e) error or warning message for each entry. For more information about this and other exceptions that can be thrown during serialization, refer to - Section + Section 4.4, "Error Handling" in the C++/Tree Mapping User Manual.

-- cgit v1.1