Review Request 117609: Add AppStream AppData for Ark

[Matthias Klumpp]

> On April 17, 2014, 2:50 p.m., David Edmundson wrote:
> > app/ark.appdata.xml.cmake, line 10
> > <https://git.reviewboard.kde.org/r/117609/diff/1/?file=266519#file266519line10>
> >
> >     Nice to see this being used.
> >     
> >     This needs to be translatable. See http://people.freedesktop.org/~hughsient/appdata/ under "Questions". I'm not sure how that ties in with KDE's i18n mechanisms.
> >     
> >     Appdata came up on the KDE Devel ML once, the thread is huge and not entirely constructive (http://lists.kde.org/?t=138338458100001&r=1&w=2)
> >     
> >     At that time I wrote a tool to make .appdata.xml files automatically from the same data that creates http://www.kde.org/applications/utilities/ark/. I extracted everything into 
> >      http://static.davidedmundson.co.uk/kde_appdata.zip from http://static.davidedmundson.co.uk/appdata_generator.txt as a proof of concept, it would be good to see this developed into a full blown script that does everything that all KDE apps can run automatically when deploying we have all the relevant data scattered across various locations already.

Yes, the translation issue has already been discussed and we found a solution :-)
Unfortunately, it is difficult for me to implement the needed parts in Scripty, because I don't use it normally and it's structure doesn't make much sense for me. So I created a few scripts to extract a pot file from AppStream XML and to merge translations back into the XML. I will send them for review later, as soon as they received some more testing, so the people who actually know Scripty can make it call them at the appropriate places.
My current plan is the following:
 1) Finish the MetaInfo spec information at the Techbase Wiki
 2) Write a mail to the ML and ask people to comment on that, make necessary changes
 3) Complete translation stuff, ask Scripty-people to help with the integration
 4) Meanwhile, write metadata for KDE apps
As for your script, that's pretty cool! We should make it use the 0.6-style spec though. Unfortunately, it can't possible know about provided interfaces, urls, screenshots etc. So maybe long-term we could go the other way round and create the website entries from AppData. But that would be ML content :-)


- Matthias


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117609/#review55960
-----------------------------------------------------------


On April 17, 2014, 2:18 p.m., Matthias Klumpp wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/117609/
> -----------------------------------------------------------
> 
> (Updated April 17, 2014, 2:18 p.m.)
> 
> 
> Review request for KDE Utils.
> 
> 
> Repository: ark
> 
> 
> Description
> -------
> 
> This commit will add AppData to Ark so it can show up in modern AppStream-aware software-centers.
> For more information on AppData, check out the wiki page I am currently working on: http://techbase.kde.org/MetaInfo/DesktopApps
> In case there are no objections or changes wanted, I would commit this to the Ark repository.
> 
> 
> Diffs
> -----
> 
>   app/CMakeLists.txt ebe2ce0 
>   app/ark.appdata.xml PRE-CREATION 
> 
> Diff: https://git.reviewboard.kde.org/r/117609/diff/
> 
> 
> Testing
> -------
> 
> Ark compiles and installs the Appdata file into the right location. AppData parsers are able to process the metadata.
> 
> 
> Thanks,
> 
> Matthias Klumpp
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-utils-devel/attachments/20140417/11965623/attachment.html>