Translations by Swann Martinet
Swann Martinet has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
| 1 → 33 of 33 results | First • Previous • Next • Last |
| ~ |
As per AppStream specification, the mentioned tag must only appear once in this context. Having multiple tags of this kind is not valid.
|
|
| 2019-10-14 |
As per AppStream specification, the mentioned tag must only appear once in this context. Having multiple tags of this kind is not valid.
|
|
| 2. |
An utility to work with AppStream metadata
|
|
| 2019-10-14 |
An utility to work with AppStream metadata
|
|
| 192. |
Media types
|
|
| 2019-10-14 |
Media types
|
|
| 197. |
D-Bus System Services
|
|
| 2019-10-14 |
D-Bus System Services
|
|
| 198. |
D-Bus Session Services
|
|
| 2019-10-14 |
D-Bus Session Services
|
|
| 203. |
Tags of this name are not permitted in this section.
|
|
| 2019-10-14 |
Tags of this name are not permitted in this section.
|
|
| 204. |
A <description/> tag must not be localized in metainfo files (upstream metadata). Localize the individual paragraphs instead.
|
|
| 2019-10-14 |
A <description/> tag must not be localised in metainfo files (upstream metadata). Localise the individual paragraphs instead.
|
|
| 206. |
AppStream descriptions support only a limited set of tags to format text: Paragraphs (<p/>) and lists (<ul/>, <ol/>). This description markup contains an invalid XML tag that would not be rendered correctly in applications supporting the metainfo specification.
|
|
| 2019-10-14 |
AppStream descriptions support only a limited set of tags to format text: Paragraphs (<p/>) and lists (<ul/>, <ol/>). This description mark-up contains an invalid XML tag that would not be rendered correctly in applications supporting the metainfo specification.
|
|
| 208. |
Enumerations must only have list items (<li/>) as children.
|
|
| 2019-10-14 |
Enumerations must only have list items (<li/>) as children.
|
|
| 215. |
The component ID is required to follow a reverse domain-name scheme for its name. See the AppStream specification for details.
|
|
| 2019-10-14 |
The component ID is required to follow a reverse domain-name scheme for its name. See the AppStream specification for details.
|
|
| 216. |
The component ID is not a reverse domain-name. Please update the ID to avoid future issues and be compatible with all AppStream implementations.
You may also consider to update the name of the accompanying .desktop file to follow the latest version of the Desktop-Entry specification and use a rDNS name for it as well. In any case, do not forget to mention the new desktop-entry in a <launchable/> tag for this component to keep the application launchable from software centers and the .desktop file data associated with the metainfo data.
|
|
| 2019-10-14 |
The component ID is not a reverse domain-name. Please update the ID to avoid future issues and be compatible with all AppStream implementations.
You may also consider to update the name of the accompanying .desktop file to follow the latest version of the Desktop-Entry specification and use a rDNS name for it as well. In any case, do not forget to mention the new desktop-entry in a <launchable/> tag for this component to keep the application launchable from software centers and the .desktop file data associated with the metainfo data.
|
|
| 218. |
The component ID contains an invalid character. Only ASCII characters, dots and numbers are permitted.
|
|
| 2019-10-14 |
The component ID contains an invalid character. Only ASCII characters, dots and numbers are permitted.
|
|
| 221. |
The component ID contains a segment starting with a number. Starting a segment of the reverse-DNS ID with a number is strongly discouraged, to keep interoperability with other tools such as D-Bus. Ideally, prefix these segments with an underscore.
|
|
| 2019-10-14 |
The component ID contains a segment starting with a number. Starting a segment of the reverse-DNS ID with a number is strongly discouraged, to keep interoperability with other tools such as D-Bus. Ideally, prefix these segments with an underscore.
|
|
| 227. |
The SPDX license expression is invalid and could not be parsed.
|
|
| 2019-10-14 |
The SPDX licence expression is invalid and could not be parsed.
|
|
| 234. |
Consider using a secure (HTTPS) URL to reference this screenshot image or video.
|
|
| 2019-10-14 |
Consider using a secure (HTTPS) URL to reference this screenshot image or video.
|
|
| 235. |
A screenshot must contain at least one image or video in order to be useful. Please add an <image/> to it.
|
|
| 2019-10-14 |
A screenshot must contain at least one image or video in order to be useful. Please add an <image/> to it.
|
|
| 236. |
A screenshot must contain either images or videos, but not both at the same time. Please use this screenshot exclusively for either static images or for videos.
|
|
| 2019-10-14 |
A screenshot must contain either images or videos, but not both at the same time. Please use this screenshot exclusively for either static images or for videos.
|
|
| 242. |
For videos, only the WebM and Matroska (.mkv) container formats are currently supported. The file extension of the referenced video does not belong to either of these formats.
|
|
| 2019-10-14 |
For videos, only the WebM and Matroska (.mkv) container formats are currently supported. The file extension of the referenced video does not belong to either of these formats.
|
|
| 244. |
Found an unknown tag in a requires/recommends group. This is likely an error, because a component relation of this type is unknown.
|
|
| 2019-10-14 |
Found an unknown tag in a requires/recommends group. This is likely an error, because a component relation of this type is unknown.
|
|
| 276. |
Consider using a secure (HTTPS) URL for the remote icon link.
|
|
| 2019-10-14 |
Consider using a secure (HTTPS) URL for the remote icon link.
|
|
| 280. |
Consider using a secure (HTTPS) URL for this web link.
|
|
| 2019-10-14 |
Consider using a secure (HTTPS) URL for this web link.
|
|
| 284. |
The <developer_name/> can not contain a hyperlink.
|
|
| 2019-10-14 |
The <developer_name/> cannot contain a hyperlink.
|
|
| 293. |
It would be useful to add a long description to this font to present it better to users.
|
|
| 2019-10-14 |
It would be useful to add a long description to this font to present it better to users.
|
|
| 294. |
It is recommended to add a long description to this component to present it better to users.
|
|
| 2019-10-14 |
It is recommended to add a long description to this component to present it better to users.
|
|
| 310. |
The category name is not valid. Refer to the XDG Menu Specification for a list of valid category names.
|
|
| 2019-10-14 |
The category name is not valid. Refer to the XDG Menu Specification for a list of valid category names.
|
|
| 314. |
The XML of this file is malformed.
|
|
| 2019-10-14 |
The XML of this file is malformed.
|
|
| 327. |
No AppStream metadata was found in this directory or directory tree.
|
|
| 2019-10-14 |
No AppStream metadata was found in this directory or directory tree.
|
|
| 328. |
No XDG applications directory found.
|
|
| 2019-10-14 |
No XDG applications directory found.
|
|
| 346. |
The AppStream specification requires a complete, ISO 8601 date string with at least day-granularity to denote dates. Please ensure the date string is valid.
|
|
| 2019-10-14 |
The AppStream specification requires a complete, ISO 8601 date string with at least day-granularity to denote dates. Please ensure the date string is valid.
|
|
| 364. |
Found: %s - Allowed: %s
|
|
| 2019-10-14 |
Found: %s – Allowed: %s
|
|
| 404. |
Print detailed explanation for found issues.
|
|
| 2019-10-14 |
Print detailed output about found components.
|
|
| 407. |
Format of the generated report (valid values are 'text' and 'yaml').
|
|
| 2019-10-14 |
Format of the generated report (valid values are 'text' and 'yaml').
|
|
| 526. |
File '%s' does not exist.
|
|
| 2019-10-14 |
File '%s' does not exist.
|
|
