Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
  1. 1 About AppStream
  2. 2 Upstream Metadata
  3. 3 Catalog Metadata
  4. 4 Miscellaneous
  5. 5 Metadata Quickstart
  6. 6 Data Validation
  7. 7 Manual pages
      appstreamcli 2012-2024Matthias Klumpp AppStream 26 July,2012 appstreamcli1appstreamcliHandle AppStream metadata formats and query AppStream dataappstreamcliCOMMANDDescription This manual page documents briefly the appstreamcli command. appstreamcli is a small helper tool to work with AppStream metadata and access the AppStream component index from the command-line. The AppStream component index contains a list of all available software components for your distribution, matched to their package names. It is generated using AppStream XML or Debian DEP-11 data, which is provided by your distributor. For more information about the AppStream project and the other components which are part of it, take a look at the AppStream pages at Freedesktop.org. Optionsget IDGet a component from the metadata pool by its identifier.ssearch TERMSearch the AppStream component pool for a given search term.what-provides TYPE TERM Return components which provide a given item. An item type can be specified using the TYPE parameter, a value to search for has to be supplied using the TERM parameter. Examples: Get components which handle the "text/xml" mediatype. appstreamcli what-provides mediatype "text/xml" Get component which provides the "libfoo.so.2" library. appstreamcli what-provides lib libfoo.so.2 refreshrefresh-cache Trigger a database refresh, if necessary. In case you want to force the database to be rebuilt, supply the --force flag. This command must be executed with root permission.status Display various information about the installed metadata and the metadata cache. os-info Show information about the current operating system from the metadata index. This requires the operating system to provide a operating-system component for itself. dump ID Dump the complete XML descriptions of components with the given ID that were found in the metadata pool. validate FILES Validate AppStream XML metadata for compliance with the specification. Both XML metadata types, upstream and distro XML, are handled. The format type which should be validated is determined automatically. The --pedantic flag triggers a more pedantic validation of the file, including minor and style issues in the report. validate-tree DIRECTORY Validate AppStream XML metadata found in a file-tree. This performs a standard validation of all found metadata, but also checks for additional errors, like the presence of .desktop files and validity of other additional metadata. check-license LICENSE Test a license string or license expression for validity and display details about it. This will check whether the license string is considered to be valid for AppStream, and return a non-zero exit code if it is not. The command will also display useful information like the canonical ID of a license, whether it is suitable as license for AppStream metadata, and whether the license is considered to be for Free and Open Source software or proprietary software. AppStream will consider any license as Free and Open Source that is marked as suitable by either the Free Software Foundation (FSF), Open Source Initiative (OSI) or explicit license list of the Debian Free Software Guidelines (DFSG). install ID Install a software component by its ID using the package manager or Flatpak. This resolves the AppStream component ID to an installation candidate and then calls either the native package manager or Flatpak (if available) to install the component. remove ID Uninstall a software component by its ID using the package manager or Flatpak. This will uninstall software matching the selected ID using either the native package manager or Flatpak (if available). put FILE Install a metadata file into the right directory on the current machine. compare-versionsvercmp VER1 [CMP] VER2 Compare two version numbers. If two version numbers are given as parameters, the versions will be compared and the comparison result will be printed to stdout. If a version number, a comparison operator and another version number are passed in as parameter, the result of the comparison operation will be printed to stdout, and appstreamcli will exit with a non-zero exit status in case the comparison failed. The comparison operator can be one of the following: eq - Equal tone - Not equal tolt - Less thangt - Greater thanle - Less than or equal toge - Greater than or equal tonew-template TYPE FILE Create a metainfo file template to be used by software projects. The --from-desktop option can be used to use a .desktop file as template for generating the example file. The generated files contain example entries which need to be filed in with the actual desired values by the project author. The first TYPE parameter is the name of an AppStream component type. For a complete list check out the documentation or the help output of appstreamcli for this subcommand. make-desktop-file MI_FILE DESKTOP_FILE Create a XDG desktop-entry file from a metainfo file. If the desktop-entry file specified in DESKTOP_FILE already exists, it will get extended with the new information extracted from the metainfo file. Otherwise a new file will be created. This command will use the first binary mentioned in a provides tag of the component for the Exec= field of the new desktop-entry file. If this is not the desired behavior, the --exec flag can be used to explicitly define a binary to launch. Other methods of launching the application are currently not supported. In order to generate a proper desktop-entry, this command assumes that not only the minimally required tags for an AppStream component are set, but also that it has an <icon/> tag of type "stock" to describe the stock icon that should be used as well as a <categories/> tag containing the categories the application should be placed in. news-to-metainfo NEWS_FILE MI_FILE [OUT_FILE] This command converts a NEWS file as used by many open source projects into the XML used by AppStream. Since NEWS files are free text, a lot of heuristics will be applied to get reasonable results. The converter can also read a YAML version of the AppStream release description and convert it to XML as well. If the metainfo file MI_FILE already exists, it will be augmented with the new release entries, otherwise the release entries will be written without any wrapping component. If [OUT_FILE] is specified, instead of acting on MI_FILE the changed data will be written to the particular file. If any of the output filenames is set to "-", the output will instead be written to stdout. The --format option can be used to enforce reading the input file in a specific format ("text" or "yaml") in case the format autodetection fails. The --limit option is used to limit the amount of release entries written (the newest entries will always be first). metainfo-to-news MI_FILE NEWS_FILE This command reverses the news-to-metainfo command and writes a NEWS file as text or YAML using the XML contained in a metainfo file. If NEWS_FILE is set to "-", the resulting data will be written to stdout instead of to a file. The --format option can be used to explicitly specify the output format ("yaml" or "text"). If it is not set, appstreamcli will guess which format is most suitable. convert FILE1 FILE1 Converts AppStream XML metadata into its YAML representation and vice versa. compose Composes an AppStream metadata catalog from a directory tree with metainfo files. This command is only available if the org.freedesktop.appstream.compose component is installed. See appstreamcli-compose1 for more information. --detailsPrint out more information about a found component.--no-colorDon't print colored output.--no-netDo not access the network when validating metadata. The same effect can be achieved by setting the AS_VALIDATE_NONET environment variable before running appstreamcli. --versionDisplay the version number of appstreamcliSee Alsopkcon1.AUTHOR This manual page was written by Matthias Klumpp matthias@tenstral.net. appstreamcli compose 2020-2024Matthias Klumpp AppStream 28 Aug,2020 appstreamcli compose1appstreamcli-composeCompose AppStream metadata catalog from directory treesappstreamcli composeCOMMANDDescription This manual page documents briefly the appstreamcli compose command. The appstreamcli compose tool is used to construct AppStream metadata catalogs from directory trees. The tool will also perform many related metadata generation actions, like resizing icons and screenshots and merging in data from referenced desktop-entry files as well as translation status information. Therefore, the tool provides a fast way to test how the final processed metadata for an application that is shipped to users may look like. It also provides a way to easily generate AppStream data for projects which do not need a more complex data generator like appstream-generator. In order for the appstreamcli compose command to be available, you may need to install the optional compose module for appstreamcli first. For more information about the AppStream project and the other components which are part of it, take a look at the AppStream pages at Freedesktop.org. OptionsSOURCE-DIRECTORIES A list of directories to process needs to be provided as positional parameters. Data from all directories will be combined into one output namespace. --origin NAME Set the AppStream data origin identifier. This can be a value like "debian-unstable-main" or "flathub". --result-root DIR Sets the directory where all generated output that is deployed to a user's machine is exported to. If this parameter is not set and we only have one directory to process, we use that directory as default output path. If both --data-dir and --icons-dir are set, --result-root is not necessary and no data will be written to that directory. --data-dir DIR Override the directory where the generated AppStream metadata catalog will be written to. Data will be written directly to this directory, and no supdirectories will be created (unlike when using --result-root to set an output location). --icons-dir DIR Override the directory where the cached icons are exported to. --hints-dir DIR Set a directory where hints reported generated during metadata processing are saved to. If this parameter is not set, no HTML/YAML hint reports will be saved. --media-dir DIR If set, creates a directory with media content (icons, screenshots, ...) that can be served via a webserver. The metadata will be extended to include information about these remote media. --media-baseurl URL The URL under which the contents of a directory set via --media-dir will be served. This value must be set if a media directory is created. --prefix DIR Set the default prefix that is used in the processed directories. If none is set explicitly, /usr is assumed. --print-report MODE Print the issue hints report (that gets exported as HTML and YAML document when --hints-dir was set) to the console in text form. Various print modes are supported: on-error only prints a short report if the run failed (default), short generates an abridged report that is always printed and full results in a detailed report to be printed. --no-partial-urls If set, all URLs in the generated data will be absolute and media_baseurl will not be used. This makes changing the media mirror harder without regenerating all data and is generally not recommended, to increase flexibility. --icon-policy POLICY-STRING Override the existing icon policy with a custom one. The icon policy sets how icons of different sizes should be dealt with. They can be in the icon cache only, be a remote icon in the media location or be both cached and available in the remote location. The icon-policy string is comprised of comma-separated %{size}x%{size}@%{scale}=%{state} statements. The size and scale are that of the respective icon, with the scale being allowed to be omitted if it is 1. The state can be one of remote, cached or cached-remote. By default, a policy of 48x48=cached,48x48@2=cached,64x64=cached,64x64@2=cached,128x128=cached-remote,128x128@2=cached-remote is selected. --allow-custom CUSTOM-KEY-NAMES By default, all custom entries set in MetaInfo input data are removed. This flag allows to whitelist custom keys to be propagated to the final catalog output data. The custom-key names should be provided as a comma-separated list. --components COMPONENT-IDs Set a comma-separated list of AppStream component IDs that should be considered for the generated metadata. All components that exist in the input data but are not mentioned in this list will be ignored for the generated output. --no-colorDon't print colored output.--verboseDisplay extra debugging information--versionDisplay the version number of appstreamcli composeSee Also appstreamcli1, appstream-generator1. AUTHOR This manual page was written by Matthias Klumpp matthias@tenstral.net.
  8. 8 AppStream API Reference
  9. Index

3.2 AppStream Catalog YAML

3.2.1 Introduction

DEP-11 is a YAML implementation of the AppStream catalog specification, which is primarily used by Debian and its derivatives. This document describes the DEP-11 YAML. All AppStream support libraries available today are able to read both the YAML and the XML specification.


If you want to use AppStream in your distribution, and are not based on Debian, please use the XML specification (unless you have strong reasons for preferring YAML). XML is the official format for AppStream catalog metadata.

Fields not mentioned in this document are not recognized by DEP-11 YAML parsers.

3.2.2 File naming and location

Take a look at Section 3.1.2, “File naming and location” for AppStream XML files for reference. While the XML data belongs into the xml subdirectory in /usr/share/swcatalog (or /var/(lib|cache)/swcatalog), the YAML data is stored in the yaml subdirectory. All other rules affecting the XML apply the DEP-11 YAML as well, including the recommendation to compress the files with gzip and the icon search logic.

3.2.3 General DEP-11 YAML structure

Each YAML file starts with a header document, which defines the basic properties of the metadata, which is followed by the actual metadata in form of one YAML document per AppStream component.

The header document contains the following fields, all of them are required or at least strongly recommended.


This field identifies the file as DEP-11 file. Its value is always DEP-11.

Field info: value-type:strrequired:yes


The version of the AppStream specification this file was built for.

Field info: value-type:strrequired:yes


Defines the repository-id this file belongs to. This usually matches the filename without extension. On Debian systems, it is the <suite>-<component> combination, e.g.



Field info: value-type:strrequired:yes


The base URL for media (screenshots, icons, ...) referenced in the metadata file. If this is set, all urls in the document referencing media will be treated relative to the base url.

Field info: value-type:strrequired:no


Defines the architecture this data belongs to. This information is useful to resolve AppStream-ID conflicts on multiarch systems, which appear if the user has metadata for two architectures installed.

Field info: value-type:strrequired:no


The priorization of this metadata file over other metadata.

Field info: value-type:intrequired:no

3.2.4 Translated fields

Fields with translated values follow the following conventions:

  1. They are of type dict

  2. They must contain a key C, with the untranslated string as value

  3. All languages are represented with their locale name as key in the dict and the translated content as value (which is of type str, unless explicitly stated otherwise)

In this document, the type localized is used to indicate that the field contains translated values following this schema.

Example for a translated Name field:

  C: I am the untranslated string.
  be@latin: Redaktar naładaŭ
  bg: Настройки на програмите
  pl: Edytor konfiguracji

3.2.5 Valid fields

This document describes all valid fields in the DEP-11 YAML specification. The requirements for the values are exactly the same as in the XML specification, and each field links to its correspondent XML tag for reference.


The ID field is a short unique and usually lower-cases identifier for the component. Depending on the component's type, different naming conventions apply.

See <id/>.

Field info: value-type:strrequired:yes


The Priority field sets the priority this component's metadata should have over other meadata in the pool. Data with a higher priority replaces data with a lower priority.

See Section 3.1.4, “Valid tags for all component types”.

Field info: value-type:intrequired:no


The type of this component. Allowed values are:

Field info: value-type:strrequired:yes


The optional Merge field describes the merge strategy that should be applied when merging data of this component into its base. It may assume the values append, replace or remove-component.

See Section 3.1.4, “Valid tags for all component types” for a description on how merging works.

Field info: value-type:strrequired:no


The name of the package which needs to be installed in order to make this component available on the system.

See <pkgname/>.

Field info: value-type:strrequired:yes


See <source_pkgname/>.

Field info: value-type:str


See <name/>.

Field info: value-type:localizedrequired:yes


See <summary/>.

Field info: value-type:localizedrequired:yes


See <project_license/>.

Field info: value-type:str


See <description/>.

The markup for the description is the same as in the XML specification, so it can be read by anything parsing basic HTML markup.

Field info: value-type:localized


See <url/>.

The Url field contains the different url types as keys in its dict. Valid url types are defined in the main AppStream XML specification. All URL types must be lowercased.


  homepage: https://example.org
  faq: https://example.org/faq
  bugtracker: https://bugs.example.org/report-issue

Field info: value-type:dict


See <project_group/>.

Field info: value-type:str


See <icon/>.

The Icon field has the different icon types as keys for its dict.


Contains the stock icon name.

Field info: value-type:str


Contains a list of dictionaries with the keys width and height of type int specifying the dimensions of the icon, as well as the key name of type str specifying the name of the icon in the cache.

Field info: value-type:list ➟ dict


Contains a list of dictionaries with the keys width and height of type int specifying the dimensions of the icon, as well as the key name of type str specifying the absolute filename pointing to the right icon.

Field info: value-type:list ➟ dict


Contains a list of dictionaries with the keys width and height of type int specifying the dimensions of the icon, as well as the key url of type str which contains a HTTP(S) or FTP URL to the icon.

Field info: value-type:list ➟ dict

Field info: value-type:dict


See <categories/>.

This field follows its XML counterpart in almost all regards. The different XDG menu category names are encoded in the list, and are of type str.


  - Network
  - Telephony

Field info: value-type:list


See <keywords/>.

This field contains the keywords for this component. The keys define the locales for the respective language, the values are of type list and contain the list of keywords for the respective language. An unlocalized C key must be present.


    - IDE
    - development
    - programming
    - IDE
    - entwicklung
    - programmierung

Field info: value-type:translated(list)


See <screenshots/>.

The Screenshots field contains a list of screenshots. A screenshot is of type dict and contains the following keys:


If default is true, the screenshot is selected as default screenshot. There has to be at least one screenshot which is marked as default.

Field info: value-type:bool


Describes the source image for this screenshot. If this field is present, videos must not be present as well. The field valus is a dictionary with the following keys:

  • height

    The image height (value-type:int)

  • width

    The image width (value-type:int)

  • url

    The full image url, or the url component added to MediaBaseUrl, if defined (value-type:str).

  • lang

    The language this screenshot image is translated in. The value is a locale string. (value-type:str, required:no)

Field info: value-type:dictrequired:conditional


A list of an arbitrary number of screenshots. All screenshots are of type dict and must contain the same keys as described for source-image. This key must not be present if videos is present.

Field info: value-type:listrequired:no


Contains a list of video dicts for this screenshot. If this field is present, source-image must not be present as well. The field valus is a dictionary with the following keys:

  • container

    The video container format (value-type:str, values as described in the XML specification)

  • codec

    The video codec format (value-type:str, values as described in the XML specification)

  • height

    The video height (value-type:int)

  • width

    The video width (value-type:int)

  • url

    The full video url, or the url component added to MediaBaseUrl, if defined (value-type:str).

  • lang

    The language this screenshot video is translated in. The value is a locale string. (value-type:str, required:no)

Field info: value-type:list(dict)required:conditional


A caption for this screenshot.

Field info: value-type:localized

Example for a Screenshots field containing one screenshot:

  - default: true
      C: Foobar showing kitchen-sink functionality
      si: Foobar shoeewing kischän-sünk funzionality
      height: 800
      url: https://www.example.org/en_US/main.png
      width: 600
      - height: 423
        width: 752
        url: https://www.example.org/en_US/main-large.png
      - height: 63
        width: 112
        url: https://www.example.org/en_US/main-small.png
  - source-video:
      container: matroska
      codec: av1
      height: 900
      url: https://www.example.org/en_US/screencast.mkv
      width: 1600

Field info: value-type:list


See <compulsory_for_desktop/>.

Field info: value-type:str


See <provides/>.

The Provides field is of type dict and can have the following keys set with the described allowed values:


A list of provided library names.

Field info: value-type:list(str)


A list of provided binaries in PATH.

Field info: value-type:list(str)


A list of provided fonts. Each font entry is of type dict and has a name key.

Field info: value-type:list(dict)


A list of modalias globs representing the hardware types this component handles.

Field info: value-type:list(str)


A list of media types (MIME types) this component can handle.

Field info: value-type:list(str)


A list of provided firmware. Each firmware entry is of type dict and has a type key, which has either runtime or flashed as value. Firmware of type flashed has a guid key, containing the GUID of the device the firmware is flashed on, while firmware of type runtime has a file key, containing the firmware filename which the kernel is looking for.

Field info: value-type:list(dict)


A list of Python 3 modules this component provides.

Field info: value-type:list(str)


A list of provided DBus services. Each service entry in the list is of type dict and has a type key, which has either system or user as value. user means the DBus service name is for a user/session service, while system means it describes a system service. The service key contains the name of the DBus service file. All dict values are of type str.

Field info: value-type:list(dict)


A list of component-IDs that this component is able to provide all functionality of.

Field info: value-type:list(str)

Field info: value-type:dict


See <developer/>.

Field info: value-type:dict


See <launchable/>.

A dictionary containing the launchable-type as key, and a list of IDs used for launching the application as value.


    - org.gnome.Sysprof2.desktop

Field info: value-type:dict(list)


See <releases/>.

The Releases contains a list of releases sorted latest-to-oldest, where each list items contains the following fields/keys:


The version number of this release.

Field info: value-type:strrequired:yes


The release type. Allowed values are:

  • stable

  • development

By default, if no release type is defined, stable is assumed.

Field info: value-type:strrequired:no


How important it is to install the new release as an update. Allowed values are:

  • low

  • medium

  • high

  • critical

If no urgency is defined, a medium urgency is implicitly assumed.

Field info: value-type:strrequired:no


The UNIX timestamp of when this software was released.

One of the unix-timestamp or date fields must be present.

Field info: value-type:intrequired:maybe


The ISO 8601 (https://en.wikipedia.org/wiki/ISO_8601) complete date of when this software was released.

One of the unix-timestamp or date fields must be present.

Field info: value-type:strrequired:maybe


A description of this release. May contain allowed HTML markup.

Field info: value-type:localized


A list of dictionaries describing the issues resolved by this release. The dictionaries contain a id key for the value of an issue as described in the XML specification, as well as a type and url key for the tag properties of the same name described in the XML AppStream specification.

Field info: value-type:list(dict)


A list of dictionaries describing the artifacts published for this release. Refer to the XML specification for details, which is mapped to YAML following the usual scheme.

Field info: value-type:list(dict)

It is recommended to order this list starting with the latest timestamp to the oldest one.


  - version: '1.8'
    unix-timestamp: 1424116753
      C: |
        <p>This stable release fixes the following bug:</p>
          <li>CPU no longer overheats when you hold down spacebar</li>
  - version: '1.2'
    unix-timestamp: 1397253600
  - version: '1.0'
    unix-timestamp: 1345932000

Field info: value-type:list(dict)


See <languages/>.

The languages list is a list of dictionaries. They must contain a percentage key, indicating the completion of translation for this language, and a locale key, with the locale string as value.


  - locale: gu
    percentage: 96
  - locale: ca@valencia
    percentage: 94
  - locale: de
    percentage: 91
  - locale: eo
    percentage: 93

Field info: value-type:list(dict)


See <bundle/>.

The Bundles contains a list of dictionaries with the keys type, having the ID for a specific bundling system (e.g. flatpak or limba) as value, and id for the associated bundle-id. See the XML tag description for information on all valid bundling systems.


  - type: limba
    id: foobar-1.0.2

Field info: value-type:list


See <extends/>.

Contains a list of AppStream IDs of the other component extended by the described component. This field may only be used with component-type addon.

Field info: value-type:list(str)


See <suggests/>.

A list of dictionaries containing suggested software components. The dictionaries must have a type key with the string value upstream or heuristic depending on where the suggestion originates from. The also must have a ids key containing a list of component-ids of the suggested software.


  - type: upstream
      - org.example.Awesome
  - type: heuristic
      - org.example.Test1
      - org.example.Test2

Field info: value-type:list(dict)


See <content_rating/>.

A dictionary containing the rating system as key, and a dictionary of rating-values as value. The value-dictionary itself has the content rating IDs as keys and the intensity values as values. The intensity values as well as IDs and rating system names match the values from the XML exactly.


    drugs-alcohol: moderate
    language-humor: mild

Field info: value-type:dict(dict)

Requires, Recommends & Supports 

See <requires/>, <recommends/> & <supports/>.

A list of dictionaries containing the referenced items. The dictionaries in the list must have one key denoting the item type, which has the respective item value as value. Refer to the XML description for a list of possible types.

Each dictionary may have a version field with contains a version comparison string. The first two characters denote the version comparison operation, and are followed by the version number to be compared with. The comparison operation may be one of:

  • == - Equal to

  • != - Not equal to

  • << - Less than

  • >> - Greater than

  • <= - Less than or equal to

  • >= - Greater than or equal to


- memory: '2500'
- modalias: usb:v1130p0202d*
- kernel: Linux
  version: '>= 4.15'
- id: org.example.TestDependency
  version: == 1.2

Field info: value-type:list(dict)


See <agreement/>.

A list containing the agreements as dictionaries, with a sections key containing a list of sections. All dict values are the same as the respective XML tag values / properties.


- type: eula
  version_id: 1.2.3a
  - type: intro
      C: Intro\n"
      C: >-
        <p>If it breaks, you get to keep both pieces.</p>

Field info: value-type:list(dict)


See <tags/>.

Field info: value-type:list(dict)


- namespace: lvfs
  tag: vendor-2021q1
- namespace: plasma
  tag: featured

See <references/>.

Field info: value-type:list(dict)


- type: doi
  value: 10.1000/182
- type: citation_cff
  value: https://example.org/CITATION.cff
- type: registry
  value: SCR_000000
  registry: SciCrunch

See <custom/>.

Field info: value-type:list(dict)

3.2.6 Example YAML file

This is an example AppStream DEP-11 metadata file:

File: DEP-11
Version: '0.8'
Origin: chromodoris-main
MediaBaseUrl: https://metadata.tanglu.org/appstream/media/
Type: desktop-application
ID: gconf-editor.desktop
  cached: gconf-editor_gconf-editor.png
  C: Configuration Editor
  be@latin: Redaktar naładaŭ
  bg: Настройки на програмите
  pl: Edytor konfiguracji
Package: gconf-editor
  C: Directly edit your entire configuration database
  ar: حرّر مباشرة كامل قاعدة بيانات الإعدادات.
  de: Direkten Zugriff auf Ihre gesamte Konfigurationsdatenbank erlangen
  - GTK
  - System
Type: desktop-application
ID: kmplayer.desktop
  cached: kmplayer_kmplayer.png
  C: KMPlayer
  hi: केएम-प्लेयर
  hne: केएम-प्लेयर
  ku: KMLêdar
  pa: KM-ਪਲੇਅਰ
  sr: КМ‑плејер
  sr@ijekavian: КМ‑плејер
  sv: Kmplayer
Package: kmplayer
  C: KDE interface for MPlayer
  - Qt
  - KDE
  - AudioVideo
  - Player
    - application/ogg
    - application/smil
    - application/vnd.ms-asf
    - application/vnd.rn-realmedia
    - application/x-kmplayer
    - video/webm
    - video/x-avi
ID: texstudio.desktop
Type: desktop-application
Package: texstudio
  C: TeXstudio
  C: LaTeX development environment
  fr: Environnement de développement LaTeX
  C: <p>TeXstudio is an integrated writing environment for creating LaTeX documents. It integrates editing,
    building and viewing into a single frontend.</p><p>Our goal is to make writing LaTeX as easy and comfortable
    as possible. This is achieved through a rich feature set including:</p>
  cached: texstudio_texstudio.png
    - editor
    - latex
    - pdflatex
    - xelatex
    - lualatex
    - context
    - bibtex
ProjectLicense: GPL-2.0
  homepage: https://texstudio.sourceforge.net/
  - Office
  - Publishing
    - text/x-tex
  - default: true
      height: 756
      url: texstudio_2.8.4+debian-3_amd64/screenshots/source/screenshot-1.png
      width: 1344
      - height: 423
        url: texstudio_2.8.4+debian-3_amd64/screenshots/752x423/screenshot-1.png
        width: 752
      - height: 351
        url: texstudio_2.8.4+debian-3_amd64/screenshots/624x351/screenshot-1.png
        width: 624
      - height: 63
        url: texstudio_2.8.4+debian-3_amd64/screenshots/112x63/screenshot-1.png
        width: 112