Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

<description> has no translations #2

Closed
ignatenkobrain opened this issue Jun 13, 2014 · 0 comments
Closed

<description> has no translations #2

ignatenkobrain opened this issue Jun 13, 2014 · 0 comments

Comments

@ignatenkobrain
Copy link
Collaborator

$ appstream-util validate-strict ../claws-mail.appdata.xml.in 
../claws-mail.appdata.xml.in: 
translations-required   <description> has no translations
Validation failed
<?xml version="1.0" encoding="UTF-8"?>
<!-- Copyright 2014 Colin Leroy <colin@colino.net> and the Claws Mail team -->
<application>
  <id type="desktop">claws-mail.desktop</id>
  <metadata_license>CC-BY-SA-3.0</metadata_license>
  <project_license>GPL-3.0+</project_license>
  <description>
    <_p>
      Claws Mail is a fast, powerful and very extensible email client.
    </_p>
    <_p>
      It is highly configurable and handles hundreds of thousands of emails
      easily. Messages are managed in an open format, and are easy to interact
      with.
    </_p>
    <_p>
      Lots of extra functionality is provided by plugins, such as PGP signatures
      and encryption, an RSS aggregator, a calendar, powerful spam filtering,
      Perl and Python interactions, HTML and PDF rendering, and more.
    </_p>
  </description>
  <screenshots>
    <screenshot type="default" width="928" height="522">http://www.claws-mail.org/appdata/claws-main.png</screenshot>
    <screenshot width="928" height="522">http://www.claws-mail.org/appdata/claws-setup.png</screenshot>
  </screenshots>
  <url type="homepage">http://www.claws-mail.org/</url>
  <updatecontact>devel@lists.claws-mail.org</updatecontact>
</application>

I've translated description per tags. I think appstream-glib should handle all tags inside desctiption and if they're translated - not throw error.

hughsie added a commit that referenced this issue Jun 13, 2014
In this mode, treat translatable tags like <_name> as an indication the tag is
already translated.

Fixes: #2
@hughsie hughsie closed this as completed Jun 13, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants