| Author |
 Topic  |
|
|
prosperus
Starting Member
1 Posts |
 Posted - 18 Dec 2011 : 21:19:52
|
Hi there, hi Alessio,
there is a serious problem when exporting via Database | Plugin -> movies.zip -> into Movielicious (from Netwalk).
XMM Version 7.2.0.3 writes the following lines into the xml-file, here an excerpt:
<Movie>
<MovieID>1</MovieID>
<Title>100&&#35;160;Jahre&&#35;160;E03&&#35;160;-&&#35;160;Verr&&#35;252;ckte&&#35;160;Jahre&&#35;160;1920-1932&&#35;160;(mp4)</Title>
<Media>MPEG-4V</Media>
<Genre></Genre>
<Year></Year>
<Status>0</Status>
<Length>107</Length>
<Plot></Plot>
<PersonalRating>0</PersonalRating>
<URL></URL>
<Purchase>yyyyMMddThh:mm:ss</Purchase>
<Actors>
</Actors>
<Director></Director>
<Position>0784</Position>
<Seen>0</Seen>
</Movie>
Because the title consists of "&"-statements, this movie is going to have the title "00&&#35;160;Jahre& ..." in Movielicious. (Same with the field "plot")
The correct title should be:
"100 Jahre E03 - Verrückte Jahre 1920-1932 (mp4)"
How can the export/import be fixed? Is there a switch to strip the unwanted characters?
Version of Movielicious btw is 1.5.3.
Thanks in advance.
Chris.
XMM is great! |
|
|
claes
Starting Member
Belgium
1 Posts |
Posted - 20 Dec 2011 : 15:18:30
|
Hi Chris, Alessio,
I'm the developer of Movielicious for Android. I investigated this and the problem with Chris's XML file is that all non-alphanumeric characters in the file had been encoded to XML entities 4 (!) times after each other. It should only have been done once.
This is how I cleaned up the XML file:
1. Using an XML-capable text editor, I decoded all XML entities 4 times after each other until there was just XML tags and normal text in the file.
2. I saved the file using UTF-8 encoding.
3. Zipped it up in movies.zip.
4. Imported movies.zip in Movielicious. All movie titles looked fine.
The result looks like this:
<Title>100 Jahre E03 - Verrückte Jahre 1920-1932 (mp4)</Title>
Movielicious (for Android, not sure about the iOS version) doesn't require that special characters are encoded as XML entities at all, as long as the XML file is saved using UTF-8 encoding. Actually, it takes longer to import an XML file on Android if it contains a lot of XML entities.
Best regards,
Claes Buckwalter
|
 |
|
|
ComZiz
Junior Member
Turkey
282 Posts |
Posted - 16 Jun 2012 : 07:02:24
|
Sir I have a Samsung Galaxy S2 Android smartphone. In the market you're application doesn't seem to be working on my phone?
quote:
Originally posted by claes
Hi Chris, Alessio,
I'm the developer of Movielicious for Android. I investigated this and the problem with Chris's XML file is that all non-alphanumeric characters in the file had been encoded to XML entities 4 (!) times after each other. It should only have been done once.
This is how I cleaned up the XML file:
1. Using an XML-capable text editor, I decoded all XML entities 4 times after each other until there was just XML tags and normal text in the file.
2. I saved the file using UTF-8 encoding.
3. Zipped it up in movies.zip.
4. Imported movies.zip in Movielicious. All movie titles looked fine.
The result looks like this:
<Title>100 Jahre E03 - Verrückte Jahre 1920-1932 (mp4)</Title>
Movielicious (for Android, not sure about the iOS version) doesn't require that special characters are encoded as XML entities at all, as long as the XML file is saved using UTF-8 encoding. Actually, it takes longer to import an XML file on Android if it contains a lot of XML entities.
Best regards,
Claes Buckwalter
|
|
|
|
maxn1
Starting Member
32 Posts |
Posted - 17 Jun 2012 : 10:43:00
|
| On Samsung Galaxy S2 Android smartphone works excellently. |
|
|
| |
Topic |
|
|
|
Plugin Export to Android (Movielicious)