Well, I didn't spot the problem - lasconic did :-)

"Bad format" is, I guess, a type of corruption too, but not one that is
normally ever seen except when testing broken code :-).  Or, I guess,
sometimes if trying to take a file created in one build and opening it an
an earlier build that lacks the necessary support for the new construct you
are testing.  We normally use file version numbers to keep this from being
an issue with actual releases - rather than reporting "bad format",
MuseScore will simply detect the file is created with a too-new version of
MuseScore.  So if you make a change that will cause older versions of
MuseScore to not be able to read the file any more, you are supposed to
bump the version number.

The one type of "bad format" errors we do occasionally see in real life has
to do with unescaped "&" characters in strings.  There are periodically
bugs where "&" in an instrument name or whatever will get written to the
file as a literal rather than as an XML entity, and this will result in a
file that can't be laoded unless you hand-edit the file.  One such bug in
2.0 was just reported and subsequently fixed within the past week -
https://musescore.org/en/node/57861.

Marc

On Sun, May 3, 2015 at 1:10 PM, Jim Newton <[email protected]> wrote:

> thanks for clearing up the terminology.
> What do you call it when the file is such that when I try to open it in
> musescore I get a popup saying:
> "Cannot read file … bad format"?
> That is what I was seeing.  And yes, you are right.  There was a “<"
> missing in the xml file.
> It is no doubt my fault.  I undoubtedly deleted when I was looking at the
> file with my editor.
>
> You have a clever eye that you can see that so fast.
>
> Thanks for the help.
>
>
>
> > On 03 May 2015, at 19:01, Marc Sabatella [via MuseScore Developer] <
> [email protected]> wrote:
> >
> > To be clear, we normally use the word "corruption" to indicate a measure
> woith the improper number of beats, particularly in voice 1.  Something
> that you can see when you load the score and count the beats.  Not sure how
> running "diff" would be involved; you seem to be referring to something
> very different from "corruption" in the normal sense.  But when I run it,
> all it shows me it what you just described - you chznged some things in
> your score.  What about that are you consider "corruption"?  It won't load
> because the syntax error in your ornamentStyle tags - I assume that's a
> result of your experimental code.  But if I fix that syntax error in a text
> editor, it loads just fine, no corruption reported or apparent.
> >
> >
> ------------------------------------------------------------------------------
> > One dashboard for servers and applications across Physical-Virtual-Cloud
> > Widest out-of-the-box monitoring support with 50+ applications
> > Performance metrics, stats and reports that give you Actionable Insights
> > Deep dive visibility with transaction tracing using APM Insight.
> > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y <
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y>
> > _______________________________________________
> > Mscore-developer mailing list
> > [hidden email] <x-msg://6/user/SendEmail.jtp?type=node&node=7579283&i=0>
> > https://lists.sourceforge.net/lists/listinfo/mscore-developer <
> https://lists.sourceforge.net/lists/listinfo/mscore-developer>
> >
> >
> > If you reply to this email, your message will be added to the discussion
> below:
> > http://dev-list.musescore.org/ISO-user-save-hook-tp7579238p7579283.html
> <http://dev-list.musescore.org/ISO-user-save-hook-tp7579238p7579283.html>
> > To unsubscribe from ISO user save hook, click here <
> http://dev-list.musescore.org/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7579238&code=amlta2EuaXNzeUBnbWFpbC5jb218NzU3OTIzOHwxMTEzNjI0NTI5
> >.
> > NAML <
> http://dev-list.musescore.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
>
>
>
>
> --
> View this message in context:
> http://dev-list.musescore.org/ISO-user-save-hook-tp7579238p7579285.html
> Sent from the MuseScore Developer mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Mscore-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>



-- 
Marc Sabatella
[email protected]
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Mscore-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mscore-developer

Reply via email to