| Author |
 Topic  |
|
|
Borsti300378
Starting Member
1 Posts |
 Posted - 27 May 2006 : 17:01:52
|
I look for the Script "DVD Shop.ch" or other German Scripte for the version 5. Can someone help me there?
das ganze nochmal auf deutsch, da mein englisch eher scheiße ist und diesen Text ein Programm überstetzt hat.
Ich suche für die Version 5 das Script "DVD-Shop.ch" oder andere deutsche Scripte.
Kann mir da jemand helfen? |
|
|
avi
Starting Member
Germany
37 Posts |
Posted - 30 May 2006 : 00:58:57
|
hi,
german scripts included are:
ofdb.de, cover-paradies.de, filmposter-archiv.de.
i use ofdb for info and filmposter-archiv for the picture - this combination has everything i need.
for actor´s info i use filmup.com (there is still no german script for actors).
hope this is a little help for you what to try.
wenn du willst kann ich dir das auch nochmal in deutsch schreiben. also meine empfehlung ist eine verkettung von ofdb-script mit dem filmposter-archiv script. wenn du ein script für den dvd-shop.ch möchtest kannst Du ja mal rumfragen ob einer der script-profis hier eins für den dvd-shop.ch erstellen mag.
ansonsten kann ich auch gern mal für Dich übersetzen wenn Du ne längere Frage hast oder einen Verbesserungsvorschlag machen willst.
kind regards / viele grüße
avi |
 |
|
|
Butze2000
Starting Member
Germany
15 Posts |
Posted - 01 Jun 2006 : 09:55:07
|
non-german readers please see below!
Hallo,
leider ist die Benutzung der Scripte momentan nur eingeschränkt möglich. Denn es gibt Probleme wenn ein Filmtitel deutsche Sonderzeichen (ä,ö,ü,ß) enthält. Dann werden von den deutschen Scripten nämlich keine Einträge gefunden obwohl die Filme in der jeweiligen Datenbank der zugehörigen Internetseite vorhanden sind. Da dieses Problem mit allen (deutschsprachigen) Scripten auftaucht liegt der Fehler meiner Meinung nach auch definitiv im XMM und nicht in den Scripten. Habe dieses Problem auch schon als Bug gemeldet (http://www.binaryworks.it/forum/topic.asp?TOPIC_ID=1520) aber leider fehlte Alessio wohl bisher die Zeit um daran zu arbeiten.
und jetzt noch mal der Versuch es auf englisch zu beschreiben:
Hey,
unfortunately the usability of all the german scripts is restricted. Because there are problems if a movietitle includes special german characters (like ä,ö,ü or ß), for example "Bärenbrüder" (in english "Brother Bear"). In this case a search with any german script (ofdb.de, filmposter-archiv.de or coverparadies) gets no result even though the movie is included in the associated database. I mentioned this problem a few weeks ago (http://www.binaryworks.it/forum/topic.asp?TOPIC_ID=1520) but I worry that Alessio hasn't the time yet to investigate in this problem.
See you
Butze2000 |
|
|
|
Custler
Starting Member
Russia
44 Posts |
Posted - 01 Jun 2006 : 11:27:08
|
IT IS NOT A SCRIPT PROBLEM.
The problem is in HTTP GET request which EMM send to site.
As I understand in .NET default encoding is UNICODE.
If title has a charachter from upper part of current codepage, the .NET convert it to UTF-32 automatically. In this case your query to website will look like:
GET /index.php?level=7&from=forma&result=adv&m_act%5Bfrom%5D=forma&m_act%5Bwhat%5D=content&m_act%5Bfind%5D=%D0%92%D0%BE%D0%BA%D1%80%D1%83%D0%B3%20%D0%A1%D0%B2%D0%B5%D1%82%D0%B0%20%D0%B7%D0%B0%2080%20%D0%B4%D0%BD%D0%B5%D0%B9&m_act%5Bcountry%5D=
Of course, website cannot understand your query.
If title has only low carachters (with codes 0x21 - 0x7E) which has same codes as in UNICODE, it is not converted and your query to website will look like:
GET /index.php?level=7&from=forma&result=adv&m_act%5Bfrom%5D=forma&m_act%5Bwhat%5D=content&m_act%5Bfind%5D=Around%20the%20World%20in%2080%20Days&m_act%5Bcountry%5D=
And you receive predictable answer. |
Edited by - Custler on 02 Jun 2006 18:13:15 |
|
|
|
Gandalf
Starting Member
Germany
28 Posts |
Posted - 02 Jun 2006 : 15:15:16
|
Hi,
If just test the OFDB Script running with German Char.
IT WORKS !!!! But u have translate the Special Char to %252% for (ü)
How hard is the work to find a Character with in the title and translate.
The Characters and Numbers are here
Ä = 196 (C4)
Ö = 214 (D6)
Ü = 220 (DC)
ß = 223 (DF)
ä = 228 (E4)
ö = 246 (F6)
ü = 252 (FC)
This is only for German special letters but if you translat every Char above (hex80) to the Val (%128%) it should work on every Char-set.
regards
Gandalf
If life get's boring, risk it |
Edited by - Gandalf on 02 Jun 2006 15:18:35 |
|
|
|
Alessio Viti
Forum Admin
Italy
9171 Posts |
Posted - 02 Jun 2006 : 15:54:15
|
Hi Guys,
Maybe I can make a function for automatically make this "translation".
I will take a look...
Thank you!
Alessio |
|
|
|
Custler
Starting Member
Russia
44 Posts |
Posted - 02 Jun 2006 : 18:18:16
|
The problem (misunderstanding) comes from access database.
QUOTE from MS ACCESS HELP:
About compressing the data in a Text, Memo, or Hyperlink field (MDB)Note The information in this topic applies only to a Microsoft Access database (.mdb).
Microsoft Access 2000 or later uses the Unicode character-encoding scheme to represent the data in a Text, Memo, or Hyperlink field. Unicode represents each character as two bytes, so the data in a Text, Memo, or Hyperlink field requires more storage space than it did in Access 97 or earlier, where each character is represented as one byte.
To offset this effect of Unicode character representation and to ensure optimal performance, the default value of the Unicode Compression property for a Text, Memo, or Hyperlink field is Yes. When a field's Unicode Compression property is set to Yes, any character whose first byte is 0 is compressed when it is stored and uncompressed when it is retrieved. Because the first byte of a Latin character— a character of a Western European language such as English, Spanish, or German— is 0, Unicode character representation does not affect how much storage space is required for compressed data that consists entirely of Latin characters.
In a single field, you can store any combination of characters that Unicode supports. However, if the first byte of a particular character is not 0, that character is not compressed.
Data in a Memo field is not compressed unless it requires 4,096 bytes or less of storage space after compression. As a result, the contents of a Memo field might be compressed in one record, but might not be compressed in another record.
|
|
|
|
Custler
Starting Member
Russia
44 Posts |
Posted - 02 Jun 2006 : 19:29:33
|
So (as I see in mdb), when you take value of Title field from mdb record and put it to script webquery string, you don't know is it unicode or not. Test for 0 in first byte is not correct, because first byte for for cyrillic is 04, for Greek - 03, for Hebrew - 05, etc.
I think you to forcibly convert Title string to unicode before put it to database, and when you take it from mdb, you convert it back to current windows codepage before insert it to webquery string. |
Edited by - Custler on 02 Jun 2006 19:30:17 |
|
|
|
carsten
Starting Member
44 Posts |
Posted - 25 Jun 2006 : 11:05:00
|
When will this bug get fixed ?
In 5.2.7 it's still not working for german umlauts. |
|
|
|
Custler
Starting Member
Russia
44 Posts |
Posted - 05 Aug 2006 : 18:15:53
|
This bug still present in 5.3.1.
So, Nobody has idea for solution? |
|
|
|
Alessio Viti
Forum Admin
Italy
9171 Posts |
Posted - 07 Aug 2006 : 10:56:15
|
Sorry guys, I haven0t find a solution yet...
Alessio |
|
|
|
Custler
Starting Member
Russia
44 Posts |
Posted - 05 Sep 2006 : 13:00:51
|
Just for remind.
We are waiting solution... |
|
|
| |
Topic |
|
Suche Deutsche Scripte?!?!