Internationalize Strings In Templates

[amjadr360]

Extendable's some templates (404.html, archive.html, index.html, etc) strings are not internationalized, and some string translations are not available at https://translate.wordpress.org/projects/wp-themes/extendable/. We could add translations for these languages, as listed here: languages for now.

Here are some examples of how translation strings appear when WP language setting sets to the Dutch language.

This is only for templates. For template parts such as headers and footers, we will address them in a separate issue, as Extendify might require tweaks for headers and footers.

[clubkert]

@amjadr360 are the translations done? Or is this just set up so that the translations can now be added to .org?

[amjadr360]

This this just set up so that the translations can now be added to .org.

[amjadr360]

On the .org, only the Dutch translation is 100% complete. For a language to receive automatic language pack updates, its translation typically needs to reach at least 95% completion. Currently:

• The Spanish (Spain) translation is at 93%.
• The Swedish translation is also at 93%.
• The Italian translation stands at 27%.

Translations for the remaining languages are yet to be done, and we need to work on them as well.
Of the total strings, about 10 to 20 will appear on the front-end, with the rest being used within the WordPress admin area.

Translating each language could take approximately 20 to 30 minutes, and 15 languages remain based on this list. How should I best prioritize this task?

[clubkert]

Translating each language could take approximately 20 to 30 minutes

20-30 minutes to translate using AI?