GLEP 31 applies to both package and category metadata. Instead of referencing it in the "Category Metadata" subsection, reference it at the beginning of the section.
Signed-off-by: Göktürk Yüksek <[email protected]> --- ebuild-writing/misc-files/metadata/text.xml | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/ebuild-writing/misc-files/metadata/text.xml b/ebuild-writing/misc-files/metadata/text.xml index 12a9dc1..a0946e8 100644 --- a/ebuild-writing/misc-files/metadata/text.xml +++ b/ebuild-writing/misc-files/metadata/text.xml @@ -16,7 +16,8 @@ package or category. <p> A metadata file follows the syntax defined in <uri link="https://wiki.gentoo.org/wiki/GLEP:68";> -GLEP 68</uri>. +GLEP 68</uri>. The character set <b>must</b> be UTF-8 as specified by +<uri link="https://wiki.gentoo.org/wiki/GLEP:31";>GLEP 31</uri>. </p> <p> @@ -602,9 +603,7 @@ part of the QA reports. For categories, <c>metadata.xml</c> specifies a long description (in English and optionally in other languages). The format is specified formally in <uri link="https://wiki.gentoo.org/wiki/GLEP:34";> -GLEP 34</uri>, and the character set <b>must</b> be UTF-8 as specified -by <uri link="https://wiki.gentoo.org/wiki/GLEP:31";>GLEP -31</uri>. A typical example: +GLEP 34</uri>. A typical example: </p> <codesample lang="sgml"> -- 2.7.3
