ChristianB Posted April 23, 2021 Share Posted April 23, 2021 Hi! I have an issue with unicode characters in URL schemes. The word I tried is "oče". Even encoded it does not work. accord://research/[All];Unicode?o%C4%8De In a similar URL scheme for iA Writer the query works both with or without encoding. ia-writer://new?text=o%C4%8De ia-writer://new?text=oče What do I have to do to make that work with Accordance? Typing it manually in Accordance works. But no luck with the URL scheme. 1 Link to comment Share on other sites More sharing options...
Silas Marrs Posted April 27, 2021 Share Posted April 27, 2021 (edited) I agree that there's a bug here, but it seems to be specific to the č character for some reason, since other unicode URLs work fine, such as accord://research/[All];Unicode?初 which works to find results in several of our texts: I don't find "oče" in research even when I just type it in. Was there a module you were expecting to find it in? Edited April 27, 2021 by Silas Marrs clarification Link to comment Share on other sites More sharing options...
ChristianB Posted April 27, 2021 Author Share Posted April 27, 2021 Thanks for taking a look. I need the characters čšž for my Slovene user bibles. None of those characters work in the URL Scheme. 1 Link to comment Share on other sites More sharing options...
Silas Marrs Posted May 7, 2021 Share Posted May 7, 2021 I've fixed this bug for the next release. Not certain when that will be. 3 Link to comment Share on other sites More sharing options...
ChristianB Posted May 11, 2021 Author Share Posted May 11, 2021 On 5/7/2021 at 5:20 AM, Silas Marrs said: I've fixed this bug for the next release. Not certain when that will be. Awesome. Thanks! Link to comment Share on other sites More sharing options...
ChristianB Posted July 16, 2021 Author Share Posted July 16, 2021 It's still not working for me in 13.2 Link to comment Share on other sites More sharing options...
ChristianB Posted July 16, 2021 Author Share Posted July 16, 2021 2 hours ago, ChristianB said: It's still not working for me in 13.2 Ok, my bad. It is working now. I forgot to set ";Unicode" in my URL scheme 1 Link to comment Share on other sites More sharing options...
ChristianB Posted September 23, 2021 Author Share Posted September 23, 2021 I noticed that while it works with "research" it does not with "search". I am trying e.g. accord://search/SSP°?hiša#rom … all encoded of course. Link to comment Share on other sites More sharing options...
ChristianB Posted November 22, 2022 Author Share Posted November 22, 2022 On 5/7/2021 at 5:20 AM, Silas Marrs said: I've fixed this bug for the next release. Not certain when that will be. Looks like it broke again in version 14. I also can not open user bibles that include "°" in the name with a uri scheme. Link to comment Share on other sites More sharing options...
Lawrence Posted November 26, 2022 Share Posted November 26, 2022 On 5/7/2021 at 11:20 AM, Silas Marrs said: I've fixed this bug for the next release. Not certain when that will be. Out of professional curiosity - why did the bug manifest only for one character? Link to comment Share on other sites More sharing options...
ChristianB Posted November 27, 2022 Author Share Posted November 27, 2022 On 11/26/2022 at 1:08 PM, Lawrence said: Out of professional curiosity - why did the bug manifest only for one character? In my testing it was not just one character but at least three čžš. Now in version 14 even German Umlaute (öäü) don't work. 1 Link to comment Share on other sites More sharing options...
ChristianB Posted January 22, 2023 Author Share Posted January 22, 2023 14.0.4 seems to have fixed it again. Thanks! 1 Link to comment Share on other sites More sharing options...
ChristianB Posted February 11, 2023 Author Share Posted February 11, 2023 Hi! Me again. I just noticed that I can not open text in a some custom created bible (.acc2 format) via the accord://read/ URL scheme. Regular bibles work but not those. I say "some" because this happens only with custom bibles that have the "°" as part of the name. Encoding that character doesn't help either. 1 Link to comment Share on other sites More sharing options...
Dr. Nathan Parker Posted February 11, 2023 Share Posted February 11, 2023 I’ll re-report this. Thanks! 1 Link to comment Share on other sites More sharing options...
ChristianB Posted February 24, 2023 Author Share Posted February 24, 2023 Thank you Nathan! BTW: I just noticed that NGÜ.atext is also affected by this. Link to comment Share on other sites More sharing options...
Dr. Nathan Parker Posted February 24, 2023 Share Posted February 24, 2023 Thanks for the followup! I’ll see what we need to do to add that to the report. 1 Link to comment Share on other sites More sharing options...
ChristianB Posted June 28, 2023 Author Share Posted June 28, 2023 Just FYI, this is still persistent in 14.0.6 Link to comment Share on other sites More sharing options...
Dr. Nathan Parker Posted June 28, 2023 Share Posted June 28, 2023 Thanks. I'll report this again. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now