Doc: Use https for links to unicode.org
* Change all outbound links in user-facing documentation. * Reflow lines that exceed 100 cols as mandated by clang-format. * Add unicode.org as a global \externalsite. Pick-to: 6.2 6.1 5.15 Change-Id: I2ba1e434aa913e678406d62c2801f1a8b2d9e4f4 Reviewed-by: Topi Reiniö <topi.reinio@qt.io>
This commit is contained in:
parent
50e664835b
commit
7968281444
@ -532,3 +532,7 @@
|
|||||||
\externalpage http://facebook.github.io/zstd/
|
\externalpage http://facebook.github.io/zstd/
|
||||||
\title Zstandard Site
|
\title Zstandard Site
|
||||||
*/
|
*/
|
||||||
|
|
||||||
|
/*!
|
||||||
|
\externalpage https://www.unicode.org/
|
||||||
|
\title Unicode standard
|
||||||
|
@ -49,7 +49,7 @@
|
|||||||
****************************************************************************/
|
****************************************************************************/
|
||||||
|
|
||||||
//! [1]
|
//! [1]
|
||||||
QString url = QLatin1String("http://www.unicode.org/");
|
QString url = QLatin1String("https://www.unicode.org/");
|
||||||
//! [1]
|
//! [1]
|
||||||
|
|
||||||
|
|
||||||
|
@ -165,7 +165,7 @@ QT_BEGIN_NAMESPACE
|
|||||||
QT_IMPLICIT_QCHAR_CONSTRUCTION.
|
QT_IMPLICIT_QCHAR_CONSTRUCTION.
|
||||||
|
|
||||||
For more information see
|
For more information see
|
||||||
\l{http://www.unicode.org/ucd/}{"About the Unicode Character Database"}.
|
\l{https://www.unicode.org/ucd/}{"About the Unicode Character Database"}.
|
||||||
|
|
||||||
\sa Unicode, QString, QLatin1Char
|
\sa Unicode, QString, QLatin1Char
|
||||||
*/
|
*/
|
||||||
@ -173,8 +173,8 @@ QT_BEGIN_NAMESPACE
|
|||||||
/*!
|
/*!
|
||||||
\enum QChar::UnicodeVersion
|
\enum QChar::UnicodeVersion
|
||||||
|
|
||||||
Specifies which version of the \l{http://www.unicode.org/}{Unicode standard}
|
Specifies which version of the \l{Unicode standard} introduced a certain
|
||||||
introduced a certain character.
|
character.
|
||||||
|
|
||||||
\value Unicode_1_1 Version 1.1
|
\value Unicode_1_1 Version 1.1
|
||||||
\value Unicode_2_0 Version 2.0
|
\value Unicode_2_0 Version 2.0
|
||||||
@ -285,7 +285,7 @@ QT_BEGIN_NAMESPACE
|
|||||||
This enum type defines the Unicode script property values.
|
This enum type defines the Unicode script property values.
|
||||||
|
|
||||||
For details about the Unicode script property values see
|
For details about the Unicode script property values see
|
||||||
\l{http://www.unicode.org/reports/tr24/}{Unicode Standard Annex #24}.
|
\l{https://www.unicode.org/reports/tr24/}{Unicode Standard Annex #24}.
|
||||||
|
|
||||||
In order to conform to C/C++ naming conventions "Script_" is prepended
|
In order to conform to C/C++ naming conventions "Script_" is prepended
|
||||||
to the codes used in the Unicode Standard.
|
to the codes used in the Unicode Standard.
|
||||||
@ -462,8 +462,8 @@ QT_BEGIN_NAMESPACE
|
|||||||
\enum QChar::Direction
|
\enum QChar::Direction
|
||||||
|
|
||||||
This enum type defines the Unicode direction attributes. See the
|
This enum type defines the Unicode direction attributes. See the
|
||||||
\l{http://www.unicode.org/reports/tr9/tr9-35.html#Table_Bidirectional_Character_Types}{Unicode Standard} for a description
|
\l{https://www.unicode.org/reports/tr9/tr9-35.html#Table_Bidirectional_Character_Types}{Unicode
|
||||||
of the values.
|
Standard} for a description of the values.
|
||||||
|
|
||||||
In order to conform to C/C++ naming conventions "Dir" is prepended
|
In order to conform to C/C++ naming conventions "Dir" is prepended
|
||||||
to the codes used in the Unicode Standard.
|
to the codes used in the Unicode Standard.
|
||||||
@ -499,8 +499,7 @@ QT_BEGIN_NAMESPACE
|
|||||||
\enum QChar::Decomposition
|
\enum QChar::Decomposition
|
||||||
|
|
||||||
This enum type defines the Unicode decomposition attributes. See
|
This enum type defines the Unicode decomposition attributes. See
|
||||||
the \l{http://www.unicode.org/}{Unicode Standard} for a
|
the \l{Unicode Standard} for a description of the values.
|
||||||
description of the values.
|
|
||||||
|
|
||||||
\value NoDecomposition
|
\value NoDecomposition
|
||||||
\value Canonical
|
\value Canonical
|
||||||
@ -529,7 +528,7 @@ QT_BEGIN_NAMESPACE
|
|||||||
since 5.3
|
since 5.3
|
||||||
|
|
||||||
This enum type defines the Unicode joining type attributes. See the
|
This enum type defines the Unicode joining type attributes. See the
|
||||||
\l{http://www.unicode.org/}{Unicode Standard} for a description of the values.
|
\l{Unicode Standard} for a description of the values.
|
||||||
|
|
||||||
In order to conform to C/C++ naming conventions "Joining_" is prepended
|
In order to conform to C/C++ naming conventions "Joining_" is prepended
|
||||||
to the codes used in the Unicode Standard.
|
to the codes used in the Unicode Standard.
|
||||||
@ -550,8 +549,7 @@ QT_BEGIN_NAMESPACE
|
|||||||
\internal
|
\internal
|
||||||
|
|
||||||
This enum type defines names for some of the Unicode combining
|
This enum type defines names for some of the Unicode combining
|
||||||
classes. See the \l{http://www.unicode.org/}{Unicode Standard}
|
classes. See the \l{Unicode Standard} for a description of the values.
|
||||||
for a description of the values.
|
|
||||||
|
|
||||||
\value Combining_Above
|
\value Combining_Above
|
||||||
\value Combining_AboveAttached
|
\value Combining_AboveAttached
|
||||||
|
@ -245,7 +245,7 @@ bool operator<(const LikelyPair &lhs, const LikelyPair &rhs)
|
|||||||
is no more specific recommendation available.
|
is no more specific recommendation available.
|
||||||
|
|
||||||
For the formal specification, see
|
For the formal specification, see
|
||||||
http://www.unicode.org/reports/tr35/#Likely_Subtags
|
https://www.unicode.org/reports/tr35/#Likely_Subtags
|
||||||
|
|
||||||
\note We also search und_script_region and und_region; they're not mentioned
|
\note We also search und_script_region and und_region; they're not mentioned
|
||||||
in the spec, but the examples clearly presume them and CLDR does provide
|
in the spec, but the examples clearly presume them and CLDR does provide
|
||||||
|
@ -7553,7 +7553,7 @@ QList<QStringView> QStringView::split(const QRegularExpression &re, Qt::SplitBeh
|
|||||||
\value NormalizationForm_KC Compatibility Decomposition followed by Canonical Composition
|
\value NormalizationForm_KC Compatibility Decomposition followed by Canonical Composition
|
||||||
|
|
||||||
\sa normalized(),
|
\sa normalized(),
|
||||||
{http://www.unicode.org/reports/tr15/}{Unicode Standard Annex #15}
|
{https://www.unicode.org/reports/tr15/}{Unicode Standard Annex #15}
|
||||||
*/
|
*/
|
||||||
|
|
||||||
/*!
|
/*!
|
||||||
|
@ -73,8 +73,8 @@ static void init(QTextBoundaryFinder::BoundaryType type, QStringView str, QCharA
|
|||||||
|
|
||||||
QTextBoundaryFinder allows to find Unicode text boundaries in a
|
QTextBoundaryFinder allows to find Unicode text boundaries in a
|
||||||
string, accordingly to the Unicode text boundary specification (see
|
string, accordingly to the Unicode text boundary specification (see
|
||||||
\l{http://www.unicode.org/reports/tr14/}{Unicode Standard Annex #14} and
|
\l{https://www.unicode.org/reports/tr14/}{Unicode Standard Annex #14} and
|
||||||
\l{http://www.unicode.org/reports/tr29/}{Unicode Standard Annex #29}).
|
\l{https://www.unicode.org/reports/tr29/}{Unicode Standard Annex #29}).
|
||||||
|
|
||||||
QTextBoundaryFinder can operate on a QString in four possible
|
QTextBoundaryFinder can operate on a QString in four possible
|
||||||
modes depending on the value of \a BoundaryType.
|
modes depending on the value of \a BoundaryType.
|
||||||
@ -85,17 +85,17 @@ static void init(QTextBoundaryFinder::BoundaryType type, QStringView str, QCharA
|
|||||||
for example form one grapheme cluster as the user thinks of them
|
for example form one grapheme cluster as the user thinks of them
|
||||||
as one character, yet it is in this case represented by two
|
as one character, yet it is in this case represented by two
|
||||||
unicode code points
|
unicode code points
|
||||||
(see \l{http://www.unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries}).
|
(see \l{https://www.unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries}).
|
||||||
|
|
||||||
Word boundaries are there to locate the start and end of what a
|
Word boundaries are there to locate the start and end of what a
|
||||||
language considers to be a word
|
language considers to be a word
|
||||||
(see \l{http://www.unicode.org/reports/tr29/#Word_Boundaries}).
|
(see \l{https://www.unicode.org/reports/tr29/#Word_Boundaries}).
|
||||||
|
|
||||||
Line break boundaries give possible places where a line break
|
Line break boundaries give possible places where a line break
|
||||||
might happen and sentence boundaries will show the beginning and
|
might happen and sentence boundaries will show the beginning and
|
||||||
end of whole sentences
|
end of whole sentences
|
||||||
(see \l{http://www.unicode.org/reports/tr29/#Sentence_Boundaries} and
|
(see \l{https://www.unicode.org/reports/tr29/#Sentence_Boundaries} and
|
||||||
\l{http://www.unicode.org/reports/tr14/}).
|
\l{https://www.unicode.org/reports/tr14/}).
|
||||||
|
|
||||||
The first position in a string is always a valid boundary and
|
The first position in a string is always a valid boundary and
|
||||||
refers to the position before the first character. The last
|
refers to the position before the first character. The last
|
||||||
|
Loading…
Reference in New Issue
Block a user