On 6 January 2017 at 19:26, Matthias Klumpp wrote:
> Oh, really? Because the spec says the name/summary is taken from the
> .desktop file if the metainfo doesn't contain it, which IMHO was a bad
> idea (while reducing the amount of metadata one needed to write, it
> also made metainfo files less u
On 4 January 2017 at 16:55, Matthias Klumpp wrote:
> @hughsie: I am wondering for some time now whether we should make the name
> and summary tags essential for desktop-application type components in
> metainfo files as well.
For appstream-glib, it is.
>This would make validation a bit more fail
On 4 January 2017 at 15:48, Luigi Toscano wrote:
> I understand that the applications checked are "the current set part of Fedora
> 25", but given that we will have few updates soon for example for KDE
> Applications, would it be possible to list also the version of the package
> that was analyzed
Hi all,
We've been looking at the AppStream extractor issues in Fedora 25, and
we've come across quite a few broken KDE applications. Broken apps are
not visible in the Ubuntu, Fedora or OpenSUSE application installers.
The apps include:
* Kjots
* braindump
* choqok
* kgraphviewer
* konquero
On 31 March 2016 at 12:43, Luigi Toscano wrote:
> AppStream metadata are already decentralized, and you don't want a sysadmin
> ticket for each change to one of them. Let's have them in the hands of each
> project manager. So I strongly disagree with moving from the current status.
Agreed. You al
On 25 January 2016 at 22:45, Albert Astals Cid wrote:
> That assumes a single .mo per application that is most of the cases the wrong
> assumption, no?
Most of the tie a single app has only one gettext domain, but you're
right, applications (or bundles) can have more than one domain and for
this
On 25 January 2016 at 22:29, Albert Astals Cid wrote:
> tl;dr: Please read the translated version from the xml file for apps developed
> by KDE.
Sorry, I don't understand, can you provide an example please.
Richard.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
tl;dr: Please add your_gettext_domain_here to your AppData
files.
Longer version:
When users are searching for software it is very important to answer
the the question "Is this localized in my language?" The way we
calculate this in the AppStream builder is to look at the compiled .mo
files, brea
Hi,
The following apps changed their desktop name (and not updated the
AppData file at the same time) in the last few weeks:
* ark -> org.kde.ark
* dolphin -> org.kde.dolphin
* dragonplayer -> org.kde.dragonplayer
* kig -> org.kde.kig
* kiriki -> org.kde.kiriki
* kshisen -> org.kde.kshisen
Hi all,
I've noticed a few projects have renamed thier .desktop files
recently, i.e. from foo.desktop to an org.kde.foo namespace. If you do
change your application-id, please update both the filename of the
AppData file to match the basename of the new .desktop file, AND
change the inside the .a
Hi all,
19% of applications in Fedora use "Keywords" in the desktop files,
some of which appear in multiple languages. This is awesome, as it
allows applications like apper and gnome-software to match search
queries on the keyword and not just the name, e.g. matching "excel"
for LibreOffice Calc.
On 19 December 2014 at 10:56, Kevin Funk wrote:
> Would be nice to get details about each validation result as well, if it's
> easy enough.
Sure, all the logs are here: https://github.com/hughsie/createrepo_as_logs/
> FYI: Just tried to validate kdevelop's appdata file on that page, but
> http:/
Hi all,
My name is Richard Hughes, and I'm one of the guys behind the
AppData/AppStream initiative. I've uploaded a page with the current
AppStream metadata status for Fedora 22 -- quite a few KDE
applications are missing easy-to-add things like desktop comments and
keywords and some
13 matches
Mail list logo