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
During the export of the XMLs originally used for the APIS import some (not all) special characters got lost. This problem does not exist anymore in the current exports (whether Verlag dump, or GIDEON export). In order to get resolve the special character issue we should find the correct "Haupttext" and "Kurzinfo" in the XMLs, compare it with the APIS text and copy it over in case the len(text_XML) == len(text_APIS). Like that we can be certain all the special characters are in the new version.
Example from the link above: CVŠT (APIS) vs. ČVŠT (XML)
The text was updated successfully, but these errors were encountered:
Can you please describe the issue you are referring to? I don't know what the described solutions tries to fix and if we revisit this issue in a couple of weeks we save a lot of time if we don't have to find out what this could have meant
see eg this history
During the export of the XMLs originally used for the APIS import some (not all) special characters got lost. This problem does not exist anymore in the current exports (whether Verlag dump, or GIDEON export). In order to get resolve the special character issue we should find the correct "Haupttext" and "Kurzinfo" in the XMLs, compare it with the APIS text and copy it over in case the
len(text_XML) == len(text_APIS)
. Like that we can be certain all the special characters are in the new version.Example from the link above: CVŠT (APIS) vs. ČVŠT (XML)
The text was updated successfully, but these errors were encountered: