Closed AaronVanGeffen closed 2 weeks ago
For details go to Translation Check
-> Details
. Expand Run checks
build stage and use the build-in search to find your language (e.g. pl-PL
)
|
|
|
---|
Other translations
| |Missing
The translation is not added to translation file. (e.g. STR_9999 is in `en-GB` but is not available in given language)Not needed
The translation file contains entries that are not in `en-GB` and should be removed (e.g. STR_9999 exists in given language but is not in `en-GB`)Same
The translation and source string is exactly the same. (e.g. STR_9999 is `Umbrella` in both `en-GB` and given language). This may be desired in some cases (e.g. `April` is the same in English and German)
I want to be able to see if this doesn’t accidentally overwrite any existing translations.
I want to do that as follows:
I can easily do that (jq --sort-keys
) and just regenerate the dumps, if you like.
Yes, please.
For details go to Translation Check
-> Details
. Expand Run checks
build stage and use the build-in search to find your language (e.g. pl-PL
)
|
|
|
---|
Other translations
| |Missing
The translation is not added to translation file. (e.g. STR_9999 is in `en-GB` but is not available in given language)Not needed
The translation file contains entries that are not in `en-GB` and should be removed (e.g. STR_9999 exists in given language but is not in `en-GB`)Same
The translation and source string is exactly the same. (e.g. STR_9999 is `Umbrella` in both `en-GB` and given language). This may be desired in some cases (e.g. `April` is the same in English and German)
For details go to Translation Check
-> Details
. Expand Run checks
build stage and use the build-in search to find your language (e.g. pl-PL
)
|
|
|
---|
Other translations
| |Missing
The translation is not added to translation file. (e.g. STR_9999 is in `en-GB` but is not available in given language)Not needed
The translation file contains entries that are not in `en-GB` and should be removed (e.g. STR_9999 exists in given language but is not in `en-GB`)Same
The translation and source string is exactly the same. (e.g. STR_9999 is `Umbrella` in both `en-GB` and given language). This may be desired in some cases (e.g. `April` is the same in English and German)
Could you re-dump to account for the changed IDs? I already merged the "sort" commit.
For details go to Translation Check
-> Details
. Expand Run checks
build stage and use the build-in search to find your language (e.g. pl-PL
)
|
|
|
---|
Other translations
| |Missing
The translation is not added to translation file. (e.g. STR_9999 is in `en-GB` but is not available in given language)Not needed
The translation file contains entries that are not in `en-GB` and should be removed (e.g. STR_9999 exists in given language but is not in `en-GB`)Same
The translation and source string is exactly the same. (e.g. STR_9999 is `Umbrella` in both `en-GB` and given language). This may be desired in some cases (e.g. `April` is the same in English and German)
For details go to Translation Check
-> Details
. Expand Run checks
build stage and use the build-in search to find your language (e.g. pl-PL
)
|
|
|
---|
Other translations
| |Missing
The translation is not added to translation file. (e.g. STR_9999 is in `en-GB` but is not available in given language)Not needed
The translation file contains entries that are not in `en-GB` and should be removed (e.g. STR_9999 exists in given language but is not in `en-GB`)Same
The translation and source string is exactly the same. (e.g. STR_9999 is `Umbrella` in both `en-GB` and given language). This may be desired in some cases (e.g. `April` is the same in English and German)
For details go to Translation Check
-> Details
. Expand Run checks
build stage and use the build-in search to find your language (e.g. pl-PL
)
|
|
|
---|
Other translations
| |Missing
The translation is not added to translation file. (e.g. STR_9999 is in `en-GB` but is not available in given language)Not needed
The translation file contains entries that are not in `en-GB` and should be removed (e.g. STR_9999 exists in given language but is not in `en-GB`)Same
The translation and source string is exactly the same. (e.g. STR_9999 is `Umbrella` in both `en-GB` and given language). This may be desired in some cases (e.g. `April` is the same in English and German)
Updated the dumps using the branch for https://github.com/OpenRCT2/objects/pull/353, i.e. taking the new Polish translations from #2964 into account. NB: not #2966, so please merge this first.
Apologies, I already merged #2966 before I saw your request.
Thankfully, there doesn't seem to be a conflict. Phew! I'm just glad I don't have to do it over again 😄
For details go to Translation Check
-> Details
. Expand Run checks
build stage and use the build-in search to find your language (e.g. pl-PL
)
|
|
|
---|
Other translations
| |Missing
The translation is not added to translation file. (e.g. STR_9999 is in `en-GB` but is not available in given language)Not needed
The translation file contains entries that are not in `en-GB` and should be removed (e.g. STR_9999 exists in given language but is not in `en-GB`)Same
The translation and source string is exactly the same. (e.g. STR_9999 is `Umbrella` in both `en-GB` and given language). This may be desired in some cases (e.g. `April` is the same in English and German)
For details go to Translation Check
-> Details
. Expand Run checks
build stage and use the build-in search to find your language (e.g. pl-PL
)
|
|
|
---|
Other translations
| |Missing
The translation is not added to translation file. (e.g. STR_9999 is in `en-GB` but is not available in given language)Not needed
The translation file contains entries that are not in `en-GB` and should be removed (e.g. STR_9999 exists in given language but is not in `en-GB`)Same
The translation and source string is exactly the same. (e.g. STR_9999 is `Umbrella` in both `en-GB` and given language). This may be desired in some cases (e.g. `April` is the same in English and German)
With the scenario text PR in, this PR updates the object string dumps for all languages, sorted by object id.
This PR as a whole has a pretty terrible diff, as the previous dump was apparently not ordered by id. The first commit orders the files in-tree by object identifier key, while the second commit brings the dumps up-to-date.