antp.be forum

Posted: **2026-01-24 10:44:34**

EricTraveling wrote: 2026-01-24 10:24:20 But I suspect this is a Windows issue, I see also the UI of AMC with some wrong character.

So the locales of Windows 10 for "non unicode programs" is set to English (USA). This may be the root issue.

I have same in my Win10, it's set to English (USA). At the same place, there is "Beta: Use Unicode UTF-8 for worldwide language support" box - it's not selected.
Post what you are doing, so I can try to reproduce it.
Did you tested "Les Misérables"?

Posted: **2026-01-24 11:09:40**

Munkey wrote: 2026-01-24 05:15:10 I don't think that it affects anything. I created new catalog with that encoding, it shows those names properly there.

Indeed the encoding in catalog properties has no effect on the program, it is used only if you store the catalog in XML and want to re-used the file elsewhere.

Munkey wrote: 2026-01-24 10:44:34At the same place, there is "Beta: Use Unicode UTF-8 for worldwide language support" box - it's not selected.

Indeed, that option must not be checked:

Accent problems are often due to that option being enabled, or by incoherent setting between the locale for non-unicode programs and the generale locale of Windows.
Some else recently had the same issue (bad decode in script, and some wrong ones in UI), and it was solved by putting the same region for both settings, see screenshot here:
viewtopic.php?p=93797#p93797

Posted: **2026-01-24 12:54:15**

thanks for the link!
Same cause, same consequences: as duncan, I am in Switzerland with Windows in English.
I had "English (Switzerland)" as region.
I set "English (United Kingdom)" in admin part 30 min, nothing changed. But now set "English (United Kingdom)" as region, and this is fixing the issue!

It seems the region "English (Switzerland)" is half broken at Microsoft...

Posted: **2026-01-24 13:13:20**

now that my "out of topic" issue is fixed, I have another one, actually 2.
Exactly on "Les Misérables", the script does not find anything because of the ''é". If I look for "miserables", the movie is found on IMDB.

Which brings me to the 2nd point: the script can search either per name or per url.
since the search by url is much more reliable, I would suggest to adjust the script to FIRST search by url (if set) and then by name.

I.e. when I start the script AND the web address is already set, I wish the script will read that url (and then start the search) instead of taking the name.

What do you think about this improvement?

Posted: **2026-01-24 13:36:53**

EricTraveling wrote: 2026-01-24 13:13:20 Exactly on "Les Misérables", the script does not find anything because of the ''é". If I look for "miserables", the movie is found on IMDB.

Strange, for me "Les Misérables" works without problem:

EricTraveling wrote: 2026-01-24 13:13:20 since the search by url is much more reliable, I would suggest to adjust the script to FIRST search by url (if set) and then by name.

But the script is already doing that.

Posted: **2026-01-24 15:00:24**

Hi, Munkey!

First, thank you for this script. I love its speed.

I was wondering, however, if there's any chance it could do the following:

- retain actor tags like 'voice' and 'uncredited' (providing they're included in the API response, obviously);
- allow the user to use '/' as a delimiter in Country and Category;
- retrieve Trivia.

Thank you for your answer.

Posted: **2026-01-24 16:03:44**

antp wrote: 2026-01-24 11:09:40

What PostPage3() does with unicode characters in query?

Posted: **2026-01-24 16:38:32**

Munkey wrote: 2026-01-24 13:36:53 Strange, for me "Les Misérables" works without problem:

The script is calling some API on IMDB. Could it be that the script response differs depending on which country we send the request from?

Munkey wrote: 2026-01-24 13:36:53
EricTraveling wrote: 2026-01-24 13:13:20 since the search by url is much more reliable, I would suggest to adjust the script to FIRST search by url (if set) and then by name.
But the script is already doing that.

Not on my side apparently, from Switzerland.
Let's keep on our example "Les Misérables".
the related link is https://www.imdb.com/title/tt1707386
I create a new entry with only 2 fields set:
- title: Les Misérables
- web address: https://www.imdb.com/title/tt1707386
I call the script IMDB (API). It is opening a text box filled with "Les Misérables", and find nothing!
with my proposition, I would expect to see the text box filled with https://www.imdb.com/title/tt1707386 and therefore receive the respective results.

Posted: **2026-01-24 17:58:08**

EricTraveling wrote: 2026-01-24 16:38:32 The script is calling some API on IMDB. Could it be that the script response differs depending on which country we send the request from?

I don't think so. I switched VPN to Switzerland - got same response.
I think the issue is in how PostPage3() sends requests with unicode in query, maybe antp will tell us how it works.

EricTraveling wrote: 2026-01-24 16:38:32 Not on my side apparently... It is opening a text box filled with...

That functionality is in BatchMode 3.

Posted: **2026-01-25 08:01:12**

EricTraveling wrote: 2026-01-24 13:13:20 the script does not find anything because of the ''é".

I reproduced the issue with "ö" (I didn't have any problems with ''é"). The issue should be fixed in v1.4.0:

Code: Select all

1.4.0 - (2026/01/25) - Fixed: Issues passing unicode chars in query with PostPage3() [returns nothing in normal search]
                              Solution: Fix the titles with UTF8EncodeToUnicodeEscapes()
                              The title examples to test:
                              "Schönberg" (www.imdb.com/title/tt0100560)
                              "Les Misérables" (www.imdb.com/title/tt1707386) [user report, but worked for me]

Posted: **2026-01-25 08:53:29**

humungus wrote: 2026-01-24 15:00:24 Hi, Munkey!

First, thank you for this script. I love its speed.

I was wondering, however, if there's any chance it could do the following:

- retain actor tags like 'voice' and 'uncredited' (providing they're included in the API response, obviously);
- allow the user to use '/' as a delimiter in Country and Category;
- retrieve Trivia.

Hi, you're welcome!

1) I'll check.
2) What's wrong with a comma?

3) There is no field for Trivia, where it should be placed?

Posted: **2026-01-25 08:56:37**

Munkey wrote: 2026-01-24 16:03:44
antp wrote: 2026-01-24 11:09:40
What PostPage3() does with unicode characters in query?

Good question... As AMC does not support unicode, technically for it there is no unicode character in the query, just ANSI (locale codepage). But the server is expecting unicode.
The only way to handle unicode is using UTF8, as long as the server accepts it (which is the most common encoding nowadays, I assume).
So like using UTF8Decode to process retrieved data, I assume that UTF8Encode may be needed to make a post with a accentuated parameter string.

I see that you fixed it by "manually" encoding and escaping the characters, I suppose it is good too if it works

Thanks for the update.

Posted: **2026-01-25 09:57:03**

antp wrote: 2026-01-25 08:56:37 I assume that UTF8Encode may be needed to make a post with a accentuated parameter string.

I don't know what form UTF8Encode converts to, but it didn't work for requests. I had to write my own utf8 encoder to unicode escapes.

Posted: **2026-01-25 11:55:24**

Munkey wrote: 2026-01-25 08:53:29
humungus wrote: 2026-01-24 15:00:24 Hi, Munkey!

First, thank you for this script. I love its speed.

I was wondering, however, if there's any chance it could do the following:

- retain actor tags like 'voice' and 'uncredited' (providing they're included in the API response, obviously);
- allow the user to use '/' as a delimiter in Country and Category;
- retrieve Trivia.
Hi, you're welcome!

1) I'll check.
2) What's wrong with a comma?
3) There is no field for Trivia, where it should be placed?

There's nothing wrong with a comma, it's just that I've been using '/' as a delimiter for so long (the main IMDb script has always had that option) I can't even remember why I liked it better than the comma, and I have way too many movies with it to switch to a comma. Of course, I can always replace it manually (it's really a bother only when IMDb decides to list umpteen genres), but I suppose you can tell the main script spoiled me.

As for Trivia, the main script offers options to import or append it to either "Description" or "Comments" field. The option to append is obviously there to accommodate users who use the fields for their original purposes. I'm not one of those users, however, as I have no interest in IMDb descriptions and comments and don't import them at all, but I do like the Trivia and I use the "Comments" field for it. I find it a good fit.

antp.be forum

[REL] IMDB ( via API )

Re: [REL] IMDB ( via API )

Re: [REL] IMDB ( via API )

Re: [REL] IMDB ( via API )

Re: [REL] IMDB ( via API )

Re: [REL] IMDB ( via API )

Re: [REL] IMDB ( via API )

Re: [REL] IMDB ( via API )

Re: [REL] IMDB ( via API )

Re: [REL] IMDB ( via API )

Re: [REL] IMDB ( via API )

Re: [REL] IMDB ( via API )

Re: [REL] IMDB ( via API )

Re: [REL] IMDB ( via API )

Re: [REL] IMDB ( via API )