Dataverse: Problem with "language" in Citation

[youssefOuahalou]

@BPeuch and I noticed a problem with our language display
. We had this problem when updating from 4.18.1 to 4.19. Do you have solutions to resolve this?

[djbrooke]

Hey @youssefOuahalou, I'm not seeing this on Harvard Dataverse or Demo Dataverse, both running 4.19. Strange.

@jggautier any ideas?

[djbrooke]

@youssefOuahalou - one more question, can you let us know the browser that you're using (including version)? Thanks!

[mheppler]

@youssefOuahalou, this is strange. I do not see this issue on our Demo Dataverse (https://demo.dataverse.org/) installation, running v. 4.19 build 331-affbf4f.

The source file, src/main/java/propertyFiles/citation.properties that is delivering those language controlled vocabulary values has not changed since 4.13. Based on what I am seeing in your screenshot, I wonder if that file was corrupted somehow and needs to be updated, and redeployed. It does seem to be tripping over the special character in controlledvocabulary.language.guarani=Guaraní, which appears to be the first instance of a special character in that document.

[youssefOuahalou]

@djbrooke I do not think it is because of the browser, because I have try on all browsers.
@mheppler I also checked the properties file and there were unrecognized characters, when I modify the file it appears as a duplicate now

[poikilotherm]

Sorry to bother, but could this be related to or even a dup of #6675?

I see the same issues in Jülich DATA, looking just the same as the ones I described back then.

[youssefOuahalou]

@poikilotherm Yes exactly,we have the same problem

[juancorr]

@poikilotherm and Ouahalou,

We are migrating to Dataverse v4.19 and we have seen that next files have
encoding problems:

en_US/astrophysics.properties
en_US/citation.properties
en_US/customDigaai.properties
en_US/geospatial.properties
fr_CA/Bundle_fr.properties
fr_CA/journal_fr.properties
fr_CA/BuiltInRoles_fr.properties
fr_CA/astrophysics_fr.properties
fr_CA/socialscience_fr.properties
fr_CA/ValidationMessages_fr.properties
fr_CA/MimeTypeDisplay_fr.properties
fr_CA/geospatial_fr.properties
fr_CA/citation_fr.properties
fr_CA/biomedical_fr.properties
fr_CA/MimeTypeFacets_fr.properties
pt_BR/citation_br.properties
pt_BR/BuiltInRoles_br.properties
pt_BR/Bundle_br.properties

Can I fix this codification issues?

Should I open another pull request to join the Spanish translation of
Dataverse v4.19?

Juan Corrales

El mié., 4 mar. 2020 a las 13:13, Ouahalou Youssef (<
[email protected]>) escribió:

@poikilotherm https://github.com/poikilotherm Yes exactly,we have the
same problem

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/IQSS/dataverse/issues/6717?email_source=notifications&email_token=AACPSCEQCU7HVGGK2PIHIA3RFZAVLA5CNFSM4LAOGMWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENXSBWI#issuecomment-594485465,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACPSCD2V2Y77YYTOXZ3PXLRFZAVLANCNFSM4LAOGMWA
.

[mheppler]

@juancorr, you will need to submit your pull request for the Spanish translation to the GDCC (Global Dataverse Community Consortium) repo for the language packs.

In the 4.13 release (#5721), we moved the language bundles out of the Dataverse source code, to the new language pack repo in an effort to make it easier for both developers to contribute translations, as well as installations to configure languages.

[juancorr]

Thanks @mheppler , I have not seen that this issue is related to Dataverse and not Dataverse-Language-Packs. "Guaraní" codification and other codification issues should be changed in the GDCC report too.

I have opened the pull request for the Spanish translation in the GDCC repo and I will open other for the codification issues too.