ProPeler
Home
Console
Upload
information
Create File
Create Folder
About
Tools
:
/
usr
/
share
/
locale-langpack
/
en_GB
/
LC_MESSAGES
/
Filename :
appstream.mo
back
Copy
�� * l ; � � } � ' - M h � � � � � � N � , ( 2 U l � x � ? n l � ) � E ( � 2 W @ ` � W � � Q � / K - u y : � > * U i m � I - Q w M � d ( | � � z R ^ � V , � � } w � � < V � ^ N [ - � 1 � ? � J ? � l & ) � � � ( \ 2 � Y �! b " Y u" � �" �# K �$ { % < % @ �% W �% q U& O �& U ' S m' h �' ( *( � S) ~ * ` * Z �* ) ' % * $ ! & ( # " A <description/> tag must not be localized in metainfo files (upstream metadata). Localize the individual paragraphs instead. 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. Category of AddonsLocalization Category of EducationMath Category of ScienceMath Category of UtilityFile System Don't show colored output. Found: %s - Allowed: %s License Licenses for 'runtime' components are usually too complex to reflect them in a simple SPDX expression. Consider using a `LicenseRef` and a web URL as value for this component's 'project_license'. E.g. `LicenseRef-free=https://example.com/licenses.html` Many components have been recognized as invalid. See debug output for details. Print detailed explanation for found issues. The <developer_name/> can not contain a hyperlink. The AppStream system cache was updated, but problems were found which resulted in metadata being ignored: %s The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information. The SPDX license expression is invalid and could not be parsed. The essential tag 'metadata_license' is missing. A license for the metadata itself always has to be defined. The first 'description/p' paragraph of this component might be too short (< 80 characters). Please consider starting with a longer paragraph to improve how the description looks like in software centers and to provide more detailed information on this component immediately in the first paragraph. The license ID was not found in the SPDX database. Please check that the license ID is written in an SPDX-conformant way and is a valid free software license. The metadata itself does not seem to be licensed under a permissive license. Please license the data under a permissive license, like FSFAP, CC0-1.0 or 0BSD to allow distributors to include it in mixed data collections without the risk of license violations due to mutually incompatible licenses. The metadata itself seems to be licensed under a complex collection of licenses. Please license the data under a simple permissive license, like FSFAP, MIT or CC0-1.0 to allow distributors to include it in mixed data collections without the risk of license violations due to mutually incompatible licenses. The metainfo file is stored in a legacy path. Please place it in '/usr/share/metainfo'. The screenshot video does not specify which container format was used in a 'container' property. The screenshot video does not specify which video codec was used in a 'codec' property. The selected video codec is not supported by AppStream and software centers may not be able to play the video. Only the AV1 and VP9 codecs are currently supported, using 'av1' and 'vp9' as values for the 'codec' property. The selected video container format is not supported by AppStream and software centers may not be able to play the video. Only the WebM and Matroska video containers are currently supported, using 'webm' and 'mkv' as values for the 'container' property. The set component type is not a recognized, valid AppStream component type. The update-contact does not appear to be a valid email address (escaping of '@' is only allowed as '_at_' or '_AT_'). This 'bundle' tag has an unknown type and can not be used. This 'launchable' tag has an unknown type and can not be used. This 'localization' component does not define any languages this localization is for. This 'localization' component is missing an 'extends' tag, to specify the components it adds localization to. This 'service' component is missing a 'launchable' tag of type 'service'. This 'web-application' component is missing a 'icon' tag to specify a valid icon. This 'web-application' component is missing a 'launchable' tag of type 'url'. This 'web-application' component is missing categorizations. A 'categories' block is likely missing. This element (paragraph, list, etc.) of a <description/> tag must not be localized individually in collection metadata. Localize the whole <description/> tag instead. The AppStream collection metadata generator (e.g. `appstream-generator`) will already do the right thing when compiling the data. This tag is a GNOME-specific extension to AppStream and not part of the official specification. Do not expect it to work in all implementations and in all software centers. Type 'console-application' component, but no information about binaries in $PATH was provided via a 'provides/binary' tag. Type 'driver' component, but no modalias information was provided via a provides/modalias tag. Type 'font' component, but no font information was provided via a 'provides/font' tag. Project-Id-Version: AppStream Report-Msgid-Bugs-To: appstream@lists.freedesktop.org PO-Revision-Date: 2020-04-04 15:54+0000 Last-Translator: Swann Martinet <Unknown> Language-Team: English (United Kingdom) <https://hosted.weblate.org/projects/appstream/translations/en_GB/> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Launchpad-Export-Date: 2022-08-18 13:52+0000 X-Generator: Launchpad (build 87919ae1fbf1142b0e02b80650e6ccf3e775beb3) Language: en_GB A <description/> tag must not be localised in metainfo files (upstream metadata). Localise the individual paragraphs instead. 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. Localisation Maths Maths Filesystem Don't show coloured output. Found: %s – Allowed: %s Licence Licences for 'runtime' components are usually too complex to reflect them in a simple SPDX expression. Consider using a `LicenseRef` and a web URL as value for this component's 'project_license'. E.g. `LicenseRef-free=https://example.com/licenses.html` Many components have been recognised as invalid. See debug output for details. Print detailed output about found components. The <developer_name/> cannot contain a hyperlink. AppStream system cache was updated, but problems were found: %s The AppStream system cache was updated, but some errors were detected, which might lead to missing metadata. Refer to the verbose log for more information. The SPDX licence expression is invalid and could not be parsed. The essential tag 'metadata_license' is missing. A licence for the metadata itself always has to be defined. The first >description/p< paragraph of this component might be too short (< 80 characters). Please consider starting with a longer paragraph to improve how the description looks like in software centers and to provide more detailed information on this component immediately in the first paragraph. The licence ID was not found in the SPDX database. Please check that the licence ID is written in an SPDX-conformant way and is a valid free software licence. The metadata itself does not seem to be licensed under a permissive licence. Please licence the data under a permissive licence, like FSFAP, CC0-1.0 or 0BSD to allow distributors to include it in mixed data collections without the risk of licence violations due to mutually incompatible licences. The metadata itself seems to be licensed under a complex collection of licences. Please license the data under a simple permissive licence, like FSFAP, MIT or CC0-1.0 to allow distributors to include it in mixed data collections without the risk of licence violations due to mutually incompatible licences. The metainfo file is stored in a legacy path. Please place it in >>/usr/share/metainfo<<. The screenshot video does not specify which container format was used in a >>container<< property. The screenshot video does not specify which video codec was used in a >>codec<< property. The selected video codec is not supported by AppStream and software centers may not be able to play the video. Only the AV1 and VP9 codecs are currently supported, using >>av1<< and >>vp9<< as values for the >>codec<< property. The selected video container format is not supported by AppStream and software centers may not be able to play the video. Only the WebM and Matroska video containers are currently supported, using >>webm<< and >>mkv<< as values for the >>container<< property. The set component type is not a recognised, valid AppStream component type. The update-contact does not appear to be a valid email address (escaping of >>@<< is only allowed as >>_at_<< or >>_AT_<<). This >>bundle<< tag has an unknown type and can not be used. This >>launchable<< tag has an unknown type and can not be used. This >>localisation<< component does not define any languages this localisation is for. This >>localisation<< component is missing an >>extends<< tag, to specify the components it adds localisation to. This >>service<< component is missing a >>launchable<< tag of type >>service<<. This >>web-application<< component is missing a >>icon<< tag to specify a valid icon. This >>web-application<< component is missing a >>launchable<< tag of type >>url<<. This >>web-application<< component is missing categorisations. A >>categories<< block is likely missing. This element (paragraph, list, etc.) of a <description/> tag must not be localised individually in collection metadata. Localise the whole <description/> tag instead. The AppStream collection metadata generator (e.g. `appstream-generator`) will already do the right thing when compiling the data. This tag is a GNOME-specific extension to AppStream and not part of the official specification. Do not expect it to work in all implementations and in all software centres. Type >>console-application<< component, but no information about binaries in $PATH was provided via a >>provides/binary<< tag. Type >>driver<< component, but no modalias information was provided via a provides/modalias tag. Type >>font<< component, but no font information was provided via a >>provides/font<< tag.