home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Quality Assurance
Bugreports
MatroskaTagInfo uses the wrong casing for tags
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="doskabouter" data-source="post: 1264847" data-attributes="member: 98267"><p>Any more opinions on this? </p><p>there are 3 choices:</p><p></p><p>1: Create separate a tool that fixes the xmlfiles, and have it run at install/update</p><p>2: When MP encounters a wrong-cased xmlfile fix it and save it</p><p>3: Support both wrong-cased and correctly-cased xmlfiles</p><p></p><p>In my opinion option 1 is the best one, and reduces the legacy stuff we have to maintain in mediaportal</p><p></p><p>It's also the hardest one to integrate in the update process.</p><p>Options 1 and 2 also make it impossible to downgrade Mediaportal.</p><p></p><p>So I guess we'll end up with option 3 and have another piece of legacy we have to maintain, test and keep working,,,</p><p>Unless ofcourse someone has a brilliant option 4 or a strong opinion on options 1 or 2</p></blockquote><p></p>
[QUOTE="doskabouter, post: 1264847, member: 98267"] Any more opinions on this? there are 3 choices: 1: Create separate a tool that fixes the xmlfiles, and have it run at install/update 2: When MP encounters a wrong-cased xmlfile fix it and save it 3: Support both wrong-cased and correctly-cased xmlfiles In my opinion option 1 is the best one, and reduces the legacy stuff we have to maintain in mediaportal It's also the hardest one to integrate in the update process. Options 1 and 2 also make it impossible to downgrade Mediaportal. So I guess we'll end up with option 3 and have another piece of legacy we have to maintain, test and keep working,,, Unless ofcourse someone has a brilliant option 4 or a strong opinion on options 1 or 2 [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Quality Assurance
Bugreports
MatroskaTagInfo uses the wrong casing for tags
Contact us
RSS
Top
Bottom