Page 1 of 2

not well-formed (invalid token) at line 393

Posted: Mon Jun 20, 2011 9:41 am
by bmord1
Hello I hope you can understand what I want (I am from Slovenia),
I have a problem with opening a file. I have worked (Audacity 1.3.12-beta (ANSI) on this file a lot of hours and know I cant open it. If I want to open the file there comes always the mistake "fehler: not well-formed (invalid token) at line 393" - (original_David1.aup) and second project "fehler: not well-formed (invalid token) at line 2018" - (Greva_gor_v_hribe_inst..aup)
please what can I do to safe the file.
help urgent

thanks

Re: not well-formed (invalid token) at line 393

Posted: Mon Jun 20, 2011 4:37 pm
by billw58
Here is the problem in the first file:

ZvoËna sled

This string occurs 4 times in the file

Audacity (ANSI) is cannot deal with the accented character. Open the .aup file in a plain text editor, find that character and change it to an unaccented one. Save changes without changing the file extension.

Search the second file for "wavetrack name=" in a plain text editor. Change any accented characters in those lines to unaccented characters.

Perhaps one the the Windows experts on this forum can say whether or not the Unicode version of Audacity would deal with these characters correctly.

-- Bill

Re: not well-formed (invalid token) at line 393

Posted: Wed Jun 22, 2011 8:31 am
by bmord1
I have new problem.
Now problem at line 823.
please what can I do to safe the file.
help urgent

Re: not well-formed (invalid token) at line 393

Posted: Wed Jun 22, 2011 7:59 pm
by steve
Lines 823 and 896 <wavetrack name="Zvoèna sled
changed to: <wavetrack name="Zvoena sled"

To correct these sort of problems you need to use a text editor that can show line numbers.
For Windows, try Notepad++ http://notepad-plus-plus.org/

Re: not well-formed (invalid token) at line 393

Posted: Wed Jun 22, 2011 8:19 pm
by waxcylinder
billw58 wrote:Perhaps one the the Windows experts on this forum can say whether or not the Unicode version of Audacity would deal with these characters correctly.
<touching wood - he says> seems to ...

I have been using various Unicode Betas and Alphas from the 1.3 series and they seem to have been accepting accented characters perfectly well. A lot of my classical LP transcriptions have French, German and Eastern European composers/conductors/performers with accented characters in their names and I don't recall having a problem with these on Windows XP.

WC

Re: not well-formed (invalid token) at line 393

Posted: Wed Jun 22, 2011 8:39 pm
by billw58
bmord1 wrote:I have new problem.
Now problem at line 823.
Note that I said
ZvoËna sled. This string occurs 4 times in the file
You need to fix all occurrences of accented characters.

-- Bill

Re: not well-formed (invalid token) at line 393

Posted: Wed Jun 22, 2011 9:17 pm
by steve
The current Unicode version of Audacity is able to handle these characters, but only if the project file was made by a Unicode version of Audacity. If the original project file was made with an ANSI version, then the character encoding will be wrong for the Unicode version and the problem will still occur.

Re: not well-formed (invalid token) at line 393

Posted: Wed Jun 22, 2011 10:11 pm
by billw58
So, in future, if you are using the ANSI version of Audacity, do not use accented characters in track names, and, before saving the project, open the metadata editor and remove any accented characters from there as well.

-- Bill

Re: not well-formed (invalid token) at line 393

Posted: Thu Jun 23, 2011 3:36 am
by bmord1
billw58 wrote:So, in future, if you are using the ANSI version of Audacity, do not use accented characters in track names, and, before saving the project, open the metadata editor and remove any accented characters from there as well.

-- Bill
Hi
I try not to go, open the missing track, see Fig.
Please help, urgently.
We you can change that this project will open without problems?
Thank you
Bojan

Re: not well-formed (invalid token) at line 393

Posted: Thu Jun 23, 2011 6:56 am
by Gale Andrews
steve wrote:The current Unicode version of Audacity is able to handle these characters, but only if the project file was made by a Unicode version of Audacity. If the original project file was made with an ANSI version of Audacity, then the character encoding will be wrong for the Unicode version and the problem will still occur.
Once again, that isn't what I found when I tested this recently with German and East Asian characters on English Windows - if the file was made with the ANSI version of Audacity, it opens without error but with the Unicode characters incorrectly displayed.

The problem is the same as we've seen before - somehow the .aup file written by the ANSI version stores the accented character so that it appears in the file as it really is "è" when it should appear as "&#x00e8;" - if it appeared so, it would not prevent opening the file.

@bmord1, are you on Windows Vista or 7 as it appears? If so, why use the ANSI version of Audacity which is marked for Windows 98/ME? If you are on Windows 2000 or later, *please* download the Unicode version of Audacity which can handle accented characters:
http://audacity.googlecode.com/files/au ... 1.3.13.exe

And can you tell me how you entered the characters in the name of the Audacity track? Did you type them with a keyboard? What keys did you press to enter the è character?

As for your latest problem it says you have 108 missing audio blockfiles - hence silent audio. I suggest you choose the option you have selected now "Close project immediately with no further changes", then open this project in 1.3.13 Beta Unicode. If you open it in 1.3.13 Unicode, the dialogue for missing blockfiles has a button "Show Log". Click that button then the log will show you the files that are missing and the folder Audacity expects them to be in. You can then search your computer for those files.




Gale