-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
I used MS Edge (recently updated) on MS Windows v10.
Meta:
- I tried searching for existing tickets, but none seemed relevant.
- I wasn't sure which (other) project to categorise this ticket under (none seemed applicable). I'm a relative newbie on MetaBrainz. If this “Other” project is incorrect, then I welcome admins/devs moving the ticket to the correct one.
I wished to contribute in the [Forums|http://community.metabrainz.org/}. I already had a MusicBrainz account, and was offered the possibility of using my existing MusicBrainz account via OAuth, which seemed sensible.
After completing the process, I discovered that, somehow, my username on the forums site had become “Lee_CarrÔ
I have *not* encountered such mojibake:
- within (the) MusicBrainz (website) itself.
- Nor when using OAuth for other software (Picard).
- The equivalent process on this Jira ticketing system (evidently) yielded the expected results,
- Same success on [BookBrainz]https://bookbrainz.org/editor/3757].
The mojibake seems to be only with the forums system. Yet, having used the same software on other sites, I know that it can handle non-ASCII. Hence my suspicion of the OAuth process.
Interestingly, under my MusicBrainz account's authorised applications, while others are listed, the forums are not.
My intention/hopes from this ticket:
- for the root causal problem of mishandling of Unicode/non-ASCII to be identified and resolved, to prevent recurrence
- if possible, for my forum account username to be remedied, but my account to otherwise be preserved (since I've already used it a little). Else, I'm open to discussion of what would work.
My guess, from experience of similar in the past, elsewhere, is that some string-parser is treating UTF-8 as if it were ISO 8859-1, or similar (I've not definitely confirmed that this is the specific encoding mismatch).
Given that MetaBrainz, rightly, targets an international cohort of users/contributors, this seems a silly problem to have.
Mojibake of username via OAuth on community.metabrainz.org
-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
I used MS Edge (recently updated) on MS Windows v10.
Meta:
- I tried searching for existing tickets, but none seemed relevant.
- I wasn't sure which (other) project to categorise this ticket under (none seemed applicable). I'm a relative newbie on MetaBrainz. If this “Other” project is incorrect, then I welcome admins/devs moving the ticket to the correct one.
I wished to contribute in the [Forums|http://community.metabrainz.org/}. I already had a MusicBrainz account, and was offered the possibility of using my existing MusicBrainz account via OAuth, which seemed sensible.
After completing the process, I discovered that, somehow, my username on the forums site had become “Lee_CarrÔ
I have *not* encountered such mojibake:
- within (the) MusicBrainz (website) itself.
- Nor when using OAuth for other software (Picard).
- The equivalent process on this Jira ticketing system (evidently) yielded the expected results,
- Same success on [BookBrainz]https://bookbrainz.org/editor/3757].
The mojibake seems to be only with the forums system. Yet, having used the same software on other sites, I know that it can handle non-ASCII. Hence my suspicion of the OAuth process.
Interestingly, under my MusicBrainz account's authorised applications, while others are listed, the forums are not.
My intention/hopes from this ticket:
- for the root causal problem of mishandling of Unicode/non-ASCII to be identified and resolved, to prevent recurrence
- if possible, for my forum account username to be remedied, but my account to otherwise be preserved (since I've already used it a little). Else, I'm open to discussion of what would work.
My guess, from experience of similar in the past, elsewhere, is that some string-parser is treating UTF-8 as if it were ISO 8859-1, or similar (I've not definitely confirmed that this is the specific encoding mismatch).
Given that MetaBrainz, rightly, targets an international cohort of users/contributors, this seems a silly problem to have.