| Author |
 Topic  |
|
|
apd
Junior Member
Greece
378 Posts |
 Posted - 03 Jun 2016 : 08:51:15
|
First of all, I'm glad for this update, I want it so much to work.
At first glance:
1. Installing v9 messed up my XMM v7 installation. I now get the error "XMM has stopped working - Close the program", no other info. Note that I installed in a separate folder and did not import the db. (I had no problem testing v8 in parallel with v7.)
2. XMM9 won't authenticate.
3. The main problem I had with v8 is still here; tried to import from IMDB two french movies Mesrine, parts I & II. My system is Greek locale. Here's the import window for part I:
After importing both films, here's XMM's response. The greek title in both the list and the web page is messed up. Film ID no 24, imported with IMDB Complete truncates the Director's name at "c,", whereas ID25, imported with IMDB Fastest does a little better, but still not good.
|
Edited by - apd on 03 Jun 2016 09:11:08 |
|
|
Alessio Viti
Forum Admin
Italy
9171 Posts |
|
|
JDommi
Administrator
Germany
4656 Posts |
Posted - 03 Jun 2016 : 10:16:20
|
Hi apd!
At first: I can still use V7, V8 AND V9.
The authentication: This time I didn't had any problems with it. But I still start XMM with admin rights.
Your 3rd problem: Is it a problem of the script(s) or of XMM itself? When I have a look at id 22 XMM seems to show the chars correctly.
So is it the import itself or the interface between script engine and main program? |
In order to achieve what is possible, you have to try the impossible over and over again.
Hermann Hesse |
 |
|
|
apd
Junior Member
Greece
378 Posts |
Posted - 03 Jun 2016 : 12:05:36
|
| Yes, the demo films appear correctly as you said, but the new imports are messed. Therefore I suppose the bug is either in the scripts (they behave differently, as I showed in the director example) or in the Magic script engine itself. Please note that the system locale is Greek, I don't know how that may affect v9, but in v7 updating films worked reasonably ok (some wrong chars, but readable). |
|
|
|
apd
Junior Member
Greece
378 Posts |
Posted - 03 Jun 2016 : 15:43:07
|
re issue 2, reinstalled and authenticated correctly.
re issue 1, I seem to have a problem with .net framework, maybe it's related to that.
re issue 3, any help welcome. This looks certainly like a wrong codepage problem. |
Edited by - apd on 03 Jun 2016 15:44:37 |
|
|
|
JDommi
Administrator
Germany
4656 Posts |
Posted - 03 Jun 2016 : 16:17:00
|
| Ale will have a look at it. For me personally I would add those wrong transitions to the script. But with different codespages directly - I'm not the fittest in that... |
In order to achieve what is possible, you have to try the impossible over and over again.
Hermann Hesse |
|
|
|
apd
Junior Member
Greece
378 Posts |
Posted - 03 Jun 2016 : 16:54:40
|
The first image above shows that the Script engine itself reads IMDB incorrectly; the imdb info is presented using the codepage "Greek (ISO)" or "Greek (Windows)", when in fact it's Unicode. I tried looking at the script, but I can't find where I could change the codepage.
Besides, the two IMDB scripts behave differently: "Complete" interprets "c," as an escape char and truncates the rest; "Fastest" just reads it wrong. I don't care about the title to appear in greek, but I do want the "c," to show correctly.
|
Edited by - apd on 03 Jun 2016 16:54:59 |
|
|
|
JDommi
Administrator
Germany
4656 Posts |
Posted - 03 Jun 2016 : 17:29:09
|
The codepage itself you can't change. Only at the end there is a conversion table. Just have a look, please.
I can't do it myself at the moment as I'm @work. |
In order to achieve what is possible, you have to try the impossible over and over again.
Hermann Hesse |
|
|
|
apd
Junior Member
Greece
378 Posts |
Posted - 03 Jun 2016 : 18:36:56
|
I've tried a few more scripts and each one returns a different result. It seems the Engine has a default codepage and does not respect the info provided by each site. As is, it's unsusable.
I also took a look at the conversion table; I have no idea how to change what with what. And it seems unreasonable to do so for every script I might use. |
|
|
|
JDommi
Administrator
Germany
4656 Posts |
Posted - 04 Jun 2016 : 01:12:50
|
You're right, unicode is still not supported.
Therefor you have to convert the char codes by the needed one.
If the V7 conversion is better than the new one then just copy the whole block from one script to another. And if there still are wrong signs visible: add #SUBSTITUTEWORD#='wrong char combination'='correct char'
As example for german ä: #SUBSTITUTEWORD#=ä=ä
How far this will work for greek I can't say, just try it... |
In order to achieve what is possible, you have to try the impossible over and over again.
Hermann Hesse |
|
|
|
apd
Junior Member
Greece
378 Posts |
Posted - 04 Jun 2016 : 10:48:20
|
So you verify there's still no unicode? Too bad.
As I said, could do without greek, though I certainly want the latin chars to appear correctly, for example the french "c," - but I don't know neither how to edit the script, nor how to declare (write down or whatever you call it) the wrong character to be replaced. Besides, XMM is supposed to offer working scripts and none of these are working properly. |
|
|
| |
Topic |
|
v9 problems
