Jump to content

Unicode characters in URL schemes


ChristianB

Recommended Posts

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. 

  • Like 1
Link to comment
Share on other sites

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:

image.png.a93aad8b41aaa430bff13249c2f0de17.png

 

 

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 by Silas Marrs
clarification
Link to comment
Share on other sites

Thanks for taking a look. I need the characters čšž for my Slovene user bibles. None of those characters work in the URL Scheme. 

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...

I've fixed this bug for the next release.  Not certain when that will be.

  • Like 3
Link to comment
Share on other sites

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

  • 2 months later...
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 

  • Like 1
Link to comment
Share on other sites

  • 2 months later...

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

  • 1 year later...
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

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

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. 

  • Sad 1
Link to comment
Share on other sites

  • 1 month later...
  • 3 weeks later...

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. 

  • Like 1
Link to comment
Share on other sites

I’ll re-report this. Thanks!

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...

Thank you Nathan! BTW: I just noticed that NGÜ.atext is also affected by this.

Link to comment
Share on other sites

Thanks for the followup! I’ll see what we need to do to add that to the report.

  • Like 1
Link to comment
Share on other sites

  • 4 months later...

Just FYI, this is still persistent in 14.0.6

Link to comment
Share on other sites

Thanks. I'll report this again.

  • Like 1
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...