Skip to content

Add-on store: support localisation for installed add-ons#15137

Merged
seanbudd merged 6 commits into
masterfrom
fixupTranslationSupport
Jul 14, 2023
Merged

Add-on store: support localisation for installed add-ons#15137
seanbudd merged 6 commits into
masterfrom
fixupTranslationSupport

Conversation

@seanbudd

@seanbudd seanbudd commented Jul 13, 2023

Copy link
Copy Markdown
Member

Link to issue number:

Part of #14973

Summary of the issue:

Installed add-ons do not have their display name and description localised, even if localised manifests exist for the installed add-on.

Description of user facing changes

Reinstate localisation for installed add-ons of the display name and description

Description of development approach

Fetch translated strings from the localised manifests

Testing strategy:

Ensure add-on with localisations is correctly displayed in the installed add-ons tab of the store.
Available and updatable add-ons rely on the strings to be translated when fetching from the store.

Known issues with pull request:

Available add-ons are not localised:
This should be fixed by nvaccess/addon-datastore#1095

Change log entries:

N/A

Code Review Checklist:

  • Pull Request description:
    • description is up to date
    • change log entries
  • Testing:
    • Unit tests
    • System (end to end) tests
    • Manual testing
  • API is compatible with existing add-ons.
  • Documentation:
    • User Documentation
    • Developer / Technical Documentation
    • Context sensitive help for GUI changes
  • UX of all users considered:
    • Speech
    • Braille
    • Low Vision
    • Different web browsers
    • Localization in other languages / culture than English
  • Security precautions taken.

@seanbudd seanbudd requested a review from a team as a code owner July 13, 2023 07:07
@seanbudd seanbudd requested a review from michaelDCurran July 13, 2023 07:07
@seanbudd seanbudd changed the title Add-on store: support cached translations Add-on store: support localisation for installed add-ons Jul 13, 2023
@seanbudd seanbudd marked this pull request as draft July 13, 2023 07:12
@seanbudd seanbudd marked this pull request as ready for review July 14, 2023 04:39
@seanbudd seanbudd marked this pull request as draft July 14, 2023 05:35
@seanbudd seanbudd marked this pull request as ready for review July 14, 2023 05:53
@seanbudd seanbudd requested a review from michaelDCurran July 14, 2023 06:14
@seanbudd seanbudd merged commit 435f540 into master Jul 14, 2023
@seanbudd seanbudd deleted the fixupTranslationSupport branch July 14, 2023 07:02
@nvaccessAuto nvaccessAuto added this to the 2023.2 milestone Jul 14, 2023
@nvdaes

nvdaes commented Jul 16, 2023

Copy link
Copy Markdown
Collaborator

Testing strategy:
Ensure add-on with localisations is correctly displayed in the installed add-ons tab of the store.
Available and updatable add-ons rely on the strings to be translated when fetching from the store.

In the installed add-ons tab, for example clipContentsDesigner 27.0.0 is not shown in Spanish, though a translated manifest.ini with a description in Spanish exists in the add-on.

seanbudd added a commit that referenced this pull request Jul 17, 2023
#15152)

Closes #14973

Summary of the issue:
Add-ons installed from the add-on store used the untranslated add-on store JSON strings.
As of #15137, only add-ons that were installed from an external source had translated strings.

Description of user facing changes
Add-ons installed from the add-on store will have translated strings.

Description of development approach
Create a separate model for add-ons fetched from the add-on store, and add-ons cached after being installed from the add-on store.
Data fetched from the add-on store should be translated. Installed cached data for an add-on will be whatever language is used when the fetched add-on store data is cached. As such, we should defer to the translated manifests for installed add-ons.
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

Successfully merging this pull request may close these issues.

4 participants