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.

Sign up for GitHub

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

Jump to bottom

translatable=no support for metainfo files #623

Closed
yakushabb opened this issue Mar 27, 2024 · 5 comments
Closed

translatable=no support for metainfo files #623

yakushabb opened this issue Mar 27, 2024 · 5 comments

Comments

@yakushabb
Copy link
Contributor

I'm not an expert on gettext or GTK-related topics, but I've noticed that several apps use translatable properties to mark UI strings as either translatable or not.

For example:

<property name="tooltip-text" translatable="yes">Copy</property>
<property name="title" translatable="no">PNG</property>

It appears that the metainfo files only support the translate="no" property:

One special case is the description block in MetaInfo files and release metadata. In MetaInfo files, each individual paragraph of a description (or enumerated entry) is translated individually, however, you can only exclude the complete block from being translated by adding translate="no" to the description element.

(Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html)

I believe the usage of <description translatable="no"> is already accepted and used by many projects, as evident from GitHub repositories:

https://github.com/search?q=description+translatable%3D%22no%22+language%3AXML&type=code&l=XML

My assumptions are:

  • The <description translatable="no"> usage is already accepted by many developers.
  • The <description translatable="no"> usage is also well established across UI files.
  • Changing translatable="no" to translate="no" offers no advantage for developers.
  • Changing this usage may require additional changes for developers and translation platforms.

My suggestion:

  • Developers could continue to use translatable="no"."
@ximion
Copy link
Owner

ximion commented Mar 28, 2024

I will not change this. It would be a breaking change, which is absolutely not okay, and supporting both would give us no benefit other than an internal inconsistency in the AppStream specification with confused users as a result, in addition to making the implementation harder as well (as we would have to support both properties everywhere).

There is also no convention or standard for this anywhere.

AppStream uses imperative properties (scale, compare instead of scaling, comparison) for these kinds of things, which is why translate is also named the way it is.

Which leaves the GitHub search, which puzzled me a bit. Looks like that's due to the older appstream-glib project implementing something else, which is a bit unfortunate - but I think adding even more confusion by allowing more stuff in AppStream proper will actually make this situation worse, so I firmly believe it's a bad idea.
(fortunately that search picked up a ton of things that aren't metainfo files, so it's likely not was widespread as it first appears)

@ximion ximion closed this as not planned Won't fix, can't repro, duplicate, stale Mar 28, 2024
@yakushabb
Copy link
Contributor Author

Thanks for answer. I will try to correct some projects that I have relations.

@ximion
Copy link
Owner

ximion commented Mar 28, 2024

Thank you, that would help a lot! Updating xgettext to include the latest metainfo.its from this project would also be useful. I files a PR in the past, but meanwhile years later that one will already be out of date.
I'll have a look into that.
(updating xgettext would mean that this translation works even in appstream is not installed when the strings are extracted/joined).

@yakushabb
Copy link
Contributor Author

Is it possible to include information or warnings about translatable="no" strings in appstreamcli?

Some developers might recognize the problem and fix it before it's reported by translators.

yakushabb added a commit to yakushabb/blanket that referenced this issue Mar 28, 2024
@yakushabb
appdata: translate=no properties
7a6d3d1 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract the
`translatable=no` marked strings as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: ximion/appstream#623

Please test your script or string extraction process
before merging this PR.

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
@yakushabb yakushabb mentioned this issue Mar 28, 2024
Merged
yakushabb added a commit to yakushabb/cartridges that referenced this issue Mar 28, 2024
@yakushabb
appdata: translate=no properties
fe7fe0f 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract the
`translatable=no` marked strings as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: ximion/appstream#623

Please test your script or string extraction process
before merging this PR.

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
@yakushabb yakushabb mentioned this issue Mar 28, 2024
Merged
yakushabb added a commit to yakushabb/dialect that referenced this issue Mar 28, 2024
@yakushabb
appdata: translate=no properties
7888fb1 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract the
`translatable=no` marked strings as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: ximion/appstream#623

Please test your script or string extraction process
before merging this PR.

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
@yakushabb yakushabb mentioned this issue Mar 28, 2024
Merged
yakushabb added a commit to yakushabb/eyedropper that referenced this issue Mar 28, 2024
@yakushabb
appdata: translate=no properties
7a7c9c5 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract the
`translatable=no` marked strings as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: ximion/appstream#623

Please test your script or string extraction process
before merging this PR.

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
@yakushabb yakushabb mentioned this issue Mar 28, 2024
Closed
yakushabb added a commit to yakushabb/forge-sparks that referenced this issue Mar 28, 2024
@yakushabb
appdata: translate=no properties
0ccfed5 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract the
`translatable=no` marked strings as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: ximion/appstream#623

**Please test your script or string extraction process
before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
@yakushabb yakushabb mentioned this issue Mar 28, 2024
Merged
yakushabb added a commit to yakushabb/Mousai that referenced this issue Mar 28, 2024
@yakushabb
appdata: translate=no properties
86b122c 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract the
`translatable=no` marked strings as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: ximion/appstream#623

**Please test your script or string extraction process
before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
@yakushabb yakushabb mentioned this issue Mar 28, 2024
Merged
yakushabb added a commit to yakushabb/share-preview that referenced this issue Mar 28, 2024
@yakushabb
appdata: translate=no properties
ffdbe72 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract the
`translatable=no` marked strings as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: ximion/appstream#623

**Please test your script or string extraction process
before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
@yakushabb yakushabb mentioned this issue Mar 28, 2024
Merged
yakushabb added a commit to yakushabb/gnome-pomodoro that referenced this issue Mar 28, 2024
@yakushabb
appdata: translate=no properties
762473c 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract the
`translatable=no` marked strings as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: ximion/appstream#623

**Please test your script or string extraction process
before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
@yakushabb yakushabb mentioned this issue Mar 28, 2024
Merged
3 tasks
yakushabb added a commit to yakushabb/celluloid that referenced this issue Mar 28, 2024
@yakushabb
appdata: translate=no properties
303b203 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract the
`translatable=no` marked strings as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: ximion/appstream#623

**Please test your script or string extraction process
before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
@yakushabb yakushabb mentioned this issue Mar 28, 2024
Closed
yakushabb added a commit to yakushabb/webfont-kit-generator that referenced this issue Mar 28, 2024
@yakushabb
appdata: translate=no properties
f98483b 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract the
`translatable=no` marked strings as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: ximion/appstream#623

**Please test your script or string extraction process
before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
@yakushabb yakushabb mentioned this issue Mar 28, 2024
Merged
yakushabb added a commit to yakushabb/Wike that referenced this issue Mar 28, 2024
@yakushabb
appdata: translate=no properties
bcf29ab 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract the
`translatable=no` marked strings as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: ximion/appstream#623

**Please test your script or string extraction process
before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
@yakushabb yakushabb mentioned this issue Mar 28, 2024
Merged
kamilprusko pushed a commit to gnome-pomodoro/gnome-pomodoro that referenced this issue Mar 28, 2024
@yakushabb @kamilprusko
appdata: translate=no properties
3a13742 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract the
`translatable=no` marked strings as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: ximion/appstream#623

**Please test your script or string extraction process
before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
yakushabb added a commit to yakushabb/Collision that referenced this issue Mar 28, 2024
@yakushabb
appdata: translate=no properties
525606e 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract the
`translatable=no` marked strings as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: ximion/appstream#623

**Please test your script or string extraction process
before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
@yakushabb yakushabb mentioned this issue Mar 28, 2024
Merged
yakushabb referenced this issue in yakushabb/Setzer Apr 9, 2024
@yakushabb
appdata: translate=no properties
29e6a29 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
@yakushabb yakushabb mentioned this issue Apr 9, 2024
Open
yakushabb referenced this issue in yakushabb/Norka Apr 9, 2024
@yakushabb
appdata: translate=no properties
7054794 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
@yakushabb yakushabb mentioned this issue Apr 9, 2024
Merged
yakushabb referenced this issue in yakushabb/AdwSteamGtk Apr 9, 2024
@yakushabb
appdata: translate=no properties
5e6dc5b 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
@yakushabb yakushabb mentioned this issue Apr 9, 2024
Merged
yakushabb referenced this issue in yakushabb/alexkdeveloper-predictor Apr 9, 2024
@yakushabb
appdata: translate=no properties
74282ae 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
@yakushabb yakushabb mentioned this issue Apr 9, 2024
Merged
yakushabb referenced this issue in yakushabb/StreamController Apr 9, 2024
@yakushabb
appdata: translate=no properties
0bbf8bd 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
yakushabb referenced this issue in yakushabb/fwupd Apr 9, 2024
@yakushabb
appdata: translate=no properties
a38f9a3 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
@yakushabb yakushabb mentioned this issue Apr 9, 2024
Merged
1 task
superm1 referenced this issue in fwupd/fwupd Apr 9, 2024
@yakushabb @superm1
appdata: translate=no properties
add36a2 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
Davidoc26 referenced this issue in Davidoc26/wallpaper-selector Apr 10, 2024
@yakushabb
Appdata related changes (#17)
ff1e1df 
* appdata: `translate=no` properties

It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html

* appdata: Add developer ID

Flathub requires a developer tag and developer ID. Also Appstream decided to use rdns structure for developer ID.

It allows reverse-dns IDs like sh.cozy, de.geigi or Fediverse handle (like @user@example.org)

> A developer tag with a name child tag must be present.
> Only one developer tag is allowed and the name tag also must be present only once in untranslated form.

```
<developer id="tld.vendor">
  <name>Developer name</name>
</developer>
```
Source: https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines/#name-summary-and-developer-name

> The element should have a id property, containing a unique ID to identify the component developer / development team. It is recommended to use a reverse-DNS name, like org.gnome or io.github.ximion, or a Fediverse handle (like @user@example.org) as ID to achieve a higher chance of uniqueness.

Source: https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-developer
hughsie referenced this issue in fwupd/fwupd Apr 12, 2024
@yakushabb @hughsie
appdata: translate=no properties
de35c82 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
superm1 referenced this issue in fwupd/fwupd Apr 12, 2024
@yakushabb @superm1
appdata: translate=no properties
6a250f5 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
yakushabb referenced this issue in yakushabb/Spedread Apr 12, 2024
@yakushabb
appdata: translate=no properties
eb64421 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
yakushabb referenced this issue in yakushabb/Memorado Apr 13, 2024
@yakushabb
appdata: translate=no properties
26af7a0 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
yakushabb referenced this issue in yakushabb/Memorado Apr 13, 2024
@yakushabb
appdata: translate=no properties
f0d2787 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
yakushabb added a commit to yakushabb/ticketbooth that referenced this issue Apr 17, 2024
@yakushabb
appdata: translate=no properties
dbf3035 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `ximion/appstream#623

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
Foldex referenced this issue in Foldex/AdwSteamGtk Apr 20, 2024
@yakushabb @Foldex
appdata: translate=no properties
1fb2cce 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
tijder referenced this issue in tijder/girens Apr 23, 2024
@yakushabb
appdata: translate=no properties
b2be318 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
dyegoaurelio referenced this issue in dyegoaurelio/simple-wireplumber-gui Apr 26, 2024
@yakushabb
Appdata related changes (#7)
6cc6b1e 
* appdata: `translate=no` properties

It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html

* appdata: Add developer ID

Flathub requires a developer tag and developer ID. Also Appstream decided to use rdns structure for developer ID.

It allows reverse-dns IDs like sh.cozy, de.geigi or Fediverse handle (like @user@example.org)

> A developer tag with a name child tag must be present.
> Only one developer tag is allowed and the name tag also must be present only once in untranslated form.

```
<developer id="tld.vendor">
  <name>Developer name</name>
</developer>
```
Source: https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines/#name-summary-and-developer-name

> The element should have a id property, containing a unique ID to identify the component developer / development team. It is recommended to use a reverse-DNS name, like org.gnome or io.github.ximion, or a Fediverse handle (like @user@example.org) as ID to achieve a higher chance of uniqueness.

Source: https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-developer

* appdata: Add vcs-browser and translate URLs

Add vcs-browser and translate URLs to show source code and translation repositories.
mufeedali referenced this issue in mufeedali/Wordbook Apr 28, 2024
@yakushabb @mufeedali
appdata: translate=no properties
5b6dfde 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
chenhn123 referenced this issue in chenhn123/fwupd May 21, 2024
@yakushabb
appdata: translate=no properties
1204e63 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
AaronErhardt pushed a commit to Relm4/relm4-template that referenced this issue Jul 11, 2024
@yakushabb
Appdata related changes
432ee17 
### Use `translate` tag in metainfo files

> Appstream project no longer supports `translatable=no` properties

Source: ximion/appstream#623

### Add vcs-browser and translate URLs

> At minimum url `type="homepage"` tag must be present to pass validation but it is best to include other links too.

Source: https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines/#url

### Add branding colors

> Applications should set a brand color in both light and dark variants. This is used by Flathub and native app store clients on banners, app pages, etc.

Source: https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines/#brand-color
SantiagoSalazarDavid referenced this issue in SantiagoSalazarDavid/video-downloader Aug 23, 2024
@SantiagoSalazarDavid
appdata: translate=no properties
7f1c4b4 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract them as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
SeaDve pushed a commit to SeaDve/Mousai that referenced this issue Sep 26, 2024
@yakushabb
appdata: translate=no properties (#131)
da14b4c 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract the
`translatable=no` marked strings as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: ximion/appstream#623

**Please test your script or string extraction process
before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
SeaDve referenced this issue in SeaDve/Kooha Sep 26, 2024
@yakushabb @SeaDve
appdata: translate=no properties
537d050 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract the
`translatable=no` marked strings as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
SeaDve referenced this issue in SeaDve/Breathing Sep 26, 2024
@yakushabb @SeaDve
appdata: translate=no properties
2b22d3a 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract the
`translatable=no` marked strings as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: `https://github.com/ximion/appstream/issues/623`

**Please test your script or string extraction process before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
A6GibKm pushed a commit to A6GibKm/decibels that referenced this issue Dec 24, 2024
@yakushabb
appdata: translate=no properties
30edb22 
It appears that the appstream project no longer supports
`translatable=no` properties, and gettext extract the
`translatable=no` marked strings as translatable.

I opened an issue to inform about the situation, but `translatable=no`
properties are not accepted by developers. You can find the issue
here: ximion/appstream#623

**Please test your script or string extraction process
before merging this PR.**

> In MetaInfo files, each individual paragraph of a description
> (or enumerated entry) is translated individually, however,
> you can only exclude the complete block from being translated
> by adding `translate="no"` to the description element.

Source: https://freedesktop.org/software/appstream/docs/sect-Quickstart-Translation.html
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ximion @yakushabb