11.. _specification :
22
33===============================
4- ABOUT File Specification v3.2.3
4+ ABOUT File Specification v3.3.0
55===============================
66
77Purpose
@@ -57,8 +57,7 @@ The meaning of this ABOUT file is:
5757Specification
5858=============
5959
60- An ABOUT file is an ASCII YAML formatted text file. Note that while Unicode characters
61- are not supported in an ABOUT file proper, external files can contain UTF-8 Unicode.
60+ An ABOUT file is an YAML formatted text file.
6261The key for the licenses field and the license_expression are dejacode license key.
6362
6463ABOUT file name
@@ -67,11 +66,9 @@ ABOUT file name
6766An ABOUT file name can use a limited set of characters and is suffixed with a
6867".ABOUT" extension using any combination of uppercase and lowercase characters.
6968
70- A file name can contain only these US-ASCII characters :
69+ A file name can contain any characters and digits with the following exception and condition :
7170
72- - digits from 0 to 9
73- - uppercase and lowercase letters from A to Z
74- - the following symbols: ``"_", "-", "+", ".", "(", ")", "~", "[", "]", "{", "}", "@", "%" ``
71+ - the following symbols are not supported: ``", #, &, ', *, \, :, ;, <, >, =, ?, /, ^, `, | ``
7572- The case of a file name is not significant. On case-sensitive file systems
7673 (such as on Linux), a tool must report an error if two ABOUT files stored in the same
7774 directory have the same lowercase file name. This is to ensure that ABOUT files can be
@@ -81,7 +78,7 @@ A file name can contain only these US-ASCII characters:
8178Lines of text
8279-------------
8380
84- An ABOUT file contains lines of US-ASCII text. Lines contain field names/values pairs.
81+ An ABOUT file contains lines of text. Lines contain field names/values pairs.
8582The standard line ending is the LF character. The line ending characters can be any LF,
8683CR or CR/LF and tools must normalize line endings to LF when processing an ABOUT file.
8784Empty lines and lines containing only white spaces that are not part of a field value
@@ -109,7 +106,7 @@ The field value is separated from the field name by a ":" colon. The ":" colon
109106can be followed by one or more spaces that must be ignored. This also applies
110107to trailing white spaces: they must be ignored.
111108
112- The field value is composed of one or more lines of plain US-ASCII printable text.
109+ The field value is composed of one or more lines of plain printable text.
113110
114111When a field value is a long string, additional continuation lines must start with
115112at least one space. In this case, the first space of an additional continuation
@@ -169,9 +166,7 @@ for long texts or to reference a common text in multiple ABOUT files such as a
169166common license text. In this case the field name is suffixed with "_file" and the
170167field value must be a path pointing to the file that contains the actual value of the
171168field. This path must be a POSIX path relative to the path of the ABOUT file. The file
172- content must be UTF-8-encoded text. This is in contrast with field values contained
173- directly in an ABOUT file that must be US-ASCII- encoded text and allows to support
174- non-ASCII text content.
169+ content must be UTF-8-encoded text.
175170
176171For example, the full license text for a component is often stored in a separate file named COPYING:
177172
0 commit comments