You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Idea is to mark somehow (some identifier into notes to string perhaps? As is done for .vue files) these strings, found in info.xml, during scrapping from source code for source strings to Transifex and then write their translation during sync from Transifex to app repo not (only) into .js .json files in l10n dir, but instead to (or at least also) into appinfo/info.xml (as in mentioned example).
This way translations of name, summary and description will be used at all in app store and apps.nextcloud.com (as is in mentioned example with app Money Buster). Translations are log time already done, so effect on user experience would be intermediate...
Thanks :-)
The text was updated successfully, but these errors were encountered:
(logical continuation of #93)
It is exactly, as former dev is stating there: nextcloud/appstore#691 (comment)
Result should be as can be seen for example in info.xml file from this file:
https://github.com/julien-nc/cospend-nc/releases/download/v1.5.8/cospend-1.5.8.tar.gz
(no link to git repo, because in this case is file created during release trough script https://github.com/julien-nc/cospend-nc/blob/main/l10n/descriptions/gen_info.xml.sh - probably due different translation platform used)
Idea is to mark somehow (some identifier into notes to string perhaps? As is done for .vue files) these strings, found in info.xml, during scrapping from source code for source strings to Transifex and then write their translation during sync from Transifex to app repo not (only) into .js .json files in l10n dir, but instead to (or at least also) into appinfo/info.xml (as in mentioned example).
This way translations of name, summary and description will be used at all in app store and apps.nextcloud.com (as is in mentioned example with app Money Buster). Translations are log time already done, so effect on user experience would be intermediate...
Thanks :-)
The text was updated successfully, but these errors were encountered: