|
 |
| | | Author: | ramicio2  | | Posted: | May 27, 2022 16:06 | | Subject: | It's not liking my XML file | | Viewed: | 97 times | | Topic: | Technical Issues | |
|
| Please see screen shot. I'm really not understanding what's wrong here.
That's a valid part number. Looks exactly the same as the example XML from
the help article. Formatting (EOL character, UTF-8, etc.) shouldn't matter,
as it's just copied and pasted.
|
|
|
| | | | | |
| | | | | Author: | SylvainLS | | Posted: | May 27, 2022 16:22 | | Subject: | Re: It's not liking my XML file | | Viewed: | 29 times | | Topic: | Technical Issues | |
|
| In Technical Issues, ramicio2 writes:
| | Please see screen shot. I'm really not understanding what's wrong here.
That's a valid part number. Looks exactly the same as the example XML from
the help article. Formatting (EOL character, UTF-8, etc.) shouldn't matter,
as it's just copied and pasted.
|
I don’t see anything wrong with it….
How did you generate the file?
|
|
| | | | | | | | | |
| | | | | | | Author: | ramicio2 | | Posted: | May 27, 2022 16:28 | | Subject: | Re: It's not liking my XML file | | Viewed: | 39 times | | Topic: | Technical Issues | |
|
| In Technical Issues, SylvainLS writes:
| | In Technical Issues, ramicio2 writes:
| | Please see screen shot. I'm really not understanding what's wrong here.
That's a valid part number. Looks exactly the same as the example XML from
the help article. Formatting (EOL character, UTF-8, etc.) shouldn't matter,
as it's just copied and pasted.
|
I don’t see anything wrong with it….
How did you generate the file?
|
Looked at an instruction manual in PDF and typed into Excel all the parts manually.
Then exported to a CSV. Then used a perl script I quick made to go line by line
to spit out the XML.
|
|
| | | | | | | | | | | | | |
| | | | | | | | | Author: | SylvainLS | | Posted: | May 27, 2022 17:59 | | Subject: | Re: It's not liking my XML file | | Viewed: | 34 times | | Topic: | Technical Issues | |
|
| In Technical Issues, ramicio2 writes:
| | […]
| | I don’t see anything wrong with it….
How did you generate the file?
|
Looked at an instruction manual in PDF and typed into Excel all the parts manually.
Then exported to a CSV. Then used a perl script I quick made to go line by line
to spit out the XML.
|
Hmm, weird.
Are you sure there’s no special (invisible) character around 3704?
Have you tried without that item? If it blocks on the next item… and the next
and the next, then something is wrong with the formatting. If the others pass,
then it’s just that item.
(BTW, 3704 is the old (and expensive) version, maybe prefer 32062 instead.)
|
|
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | Author: | Bond | | Posted: | May 27, 2022 18:27 | | Subject: | Re: It's not liking my XML file | | Viewed: | 32 times | | Topic: | Technical Issues | |
|
| In Technical Issues, SylvainLS writes:
| | In Technical Issues, ramicio2 writes:
| | […]
| | I don’t see anything wrong with it….
How did you generate the file?
|
Looked at an instruction manual in PDF and typed into Excel all the parts manually.
Then exported to a CSV. Then used a perl script I quick made to go line by line
to spit out the XML.
|
Hmm, weird.
Are you sure there’s no special (invisible) character around 3704?
Have you tried without that item? If it blocks on the next item… and the next
and the next, then something is wrong with the formatting. If the others pass,
then it’s just that item.
(BTW, 3704 is the old (and expensive) version, maybe prefer 32062 instead.)
|
That was going to be my suggestion; make sure there are hard returns between
each line. Then again, if the XML was written with a simple text editor such
as Notepad, I can't see how formatting would be an issue.
- Pat
|
|
|
| | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | Author: | SylvainLS | | Posted: | May 27, 2022 18:45 | | Subject: | Re: It's not liking my XML file | | Viewed: | 30 times | | Topic: | Technical Issues | |
|
| In Technical Issues, Bond writes:
| | […]
That was going to be my suggestion; make sure there are hard returns between
each line. Then again, if the XML was written with a simple text editor such
as Notepad, I can't see how formatting would be an issue.
- Pat
|
Simple whitespace should not be a problem between tags (space, tab, linefeed,
return).
And the error messages are better now: they tell you when there’s a syntax error
(missing closing tag…).
The message OP has is really about not finding ‘3704’ in the catalogue.
That’s why I think maybe Excel added something (fine space?) around or inside
it and Perl just copied it.
BTW, ramicio2, your Perl script could check for the presence of non-pure ASCII
characters (ord 127).
(AFAIK, the WL can have unicode characters in the remarks field… but you don’t
use them  )
|
|
|
| | | | | | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | Author: | ramicio2 | | Posted: | May 28, 2022 12:25 | | Subject: | Re: It's not liking my XML file | | Viewed: | 28 times | | Topic: | Technical Issues | |
|
| In Technical Issues, SylvainLS writes:
| | In Technical Issues, Bond writes:
| | […]
That was going to be my suggestion; make sure there are hard returns between
each line. Then again, if the XML was written with a simple text editor such
as Notepad, I can't see how formatting would be an issue.
- Pat
|
Simple whitespace should not be a problem between tags (space, tab, linefeed,
return).
And the error messages are better now: they tell you when there’s a syntax error
(missing closing tag…).
The message OP has is really about not finding ‘3704’ in the catalogue.
That’s why I think maybe Excel added something (fine space?) around or inside
it and Perl just copied it.
BTW, ramicio2, your Perl script could check for the presence of non-pure ASCII
characters (ord 127).
(AFAIK, the WL can have unicode characters in the remarks field… but you don’t
use them )
|
I use Notepad++. Toggling the option to show literally all characters, there
is nothing inside the data of the CSV spat out by Excel. Same with the XML that
Perl generated. Luckily I had a model of what I needed, and I can also import
an io file, and did so. I'm not privy to all the new software that's
out for Lego stuff. Thank you.
|
|
|
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | Author: | 1001bricks | | Posted: | May 28, 2022 12:39 | | Subject: | Re: It's not liking my XML file | | Viewed: | 37 times | | Topic: | Technical Issues | |
|
| | | I use Notepad++. Toggling the option to show literally all characters, there
is nothing inside the data of the CSV spat out by Excel. Same with the XML that
Perl generated. Luckily I had a model of what I needed, and I can also import
an io file, and did so. I'm not privy to all the new software that's
out for Lego stuff. Thank you.
|
Note that BrickStore does all this freely and open-source (create list, import
list, import studio... then export xml, wanted-list, bsx...)
And you don't have to fix anything
Created in 2006 by a German developper - rewritten in 2021: free and open source.
https://github.com/rgriebl/brickstore/releases
To update to the latest build (recommended), use the very last one here:
https://github.com/rgriebl/brickstore/actions
You found a bug? It may be already signaled, and it's fixed quickly, here:
https://github.com/rgriebl/brickstore/issues
Sylvain
|
|
|
| | | | | | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | Author: | WoutR | | Posted: | May 28, 2022 13:25 | | Subject: | Re: It's not liking my XML file | | Viewed: | 25 times | | Topic: | Technical Issues | |
|
| In Technical Issues, SylvainLS writes:
| | In Technical Issues, Bond writes:
| | […]
That was going to be my suggestion; make sure there are hard returns between
each line. Then again, if the XML was written with a simple text editor such
as Notepad, I can't see how formatting would be an issue.
- Pat
|
Simple whitespace should not be a problem between tags (space, tab, linefeed,
return).
|
I recently had a file that kept crashing until I removed all spaces.
| | And the error messages are better now: they tell you when there’s a syntax error
(missing closing tag…).
The message OP has is really about not finding ‘3704’ in the catalogue.
That’s why I think maybe Excel added something (fine space?) around or inside
it and Perl just copied it.
BTW, ramicio2, your Perl script could check for the presence of non-pure ASCII
characters (ord 127).
(AFAIK, the WL can have unicode characters in the remarks field… but you don’t
use them )
|
|
|
|
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | Author: | SylvainLS | | Posted: | May 28, 2022 14:28 | | Subject: | Re: It's not liking my XML file | | Viewed: | 24 times | | Topic: | Technical Issues | |
|
| In Technical Issues, WoutR writes:
| | […]
| | Simple whitespace should not be a problem between tags (space, tab, linefeed,
return).
|
I recently had a file that kept crashing until I removed all spaces.
|
Spaces around the elements?
I mean, not inside some field-tags:
— [ITEMID]3001[/ITEMID] = okay
— [ITEMID] 3001 [/ITEMID] = k.o.
Hmm, just did a small test:
— spaces inside itemid = error on the ID (it doesn’t remove the spaces),
— spaces inside color = color N/A (it doesn’t remove the spaces, and transforming
a space into an integer gives 0),
— space at the beginning of itemtype = error on the item ID,
— space at the end of itemtype = it works.
Well, anyway, the parser is not robust enough, it should at least strip the texts
for all the fields before converting & using their values (well, debatable for
remarks: some people might use spaces for a reason…).
And I still don’t get why WL XML files can’t be uploaded like the other file
types (= you need to copy-paste).
|
|
|
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | | Author: | WoutR | | Posted: | May 28, 2022 15:14 | | Subject: | Re: It's not liking my XML file | | Viewed: | 29 times | | Topic: | Technical Issues | |
|
| In Technical Issues, SylvainLS writes:
| | In Technical Issues, WoutR writes:
| | […]
| | Simple whitespace should not be a problem between tags (space, tab, linefeed,
return).
|
I recently had a file that kept crashing until I removed all spaces.
|
Spaces around the elements?
I mean, not inside some field-tags:
— [ITEMID]3001[/ITEMID] = okay
— [ITEMID] 3001 [/ITEMID] = k.o.
Hmm, just did a small test:
— spaces inside itemid = error on the ID (it doesn’t remove the spaces),
— spaces inside color = color N/A (it doesn’t remove the spaces, and transforming
a space into an integer gives 0),
— space at the beginning of itemtype = error on the item ID,
— space at the end of itemtype = it works.
Well, anyway, the parser is not robust enough, it should at least strip the texts
for all the fields before converting & using their values (well, debatable for
remarks: some people might use spaces for a reason…).
And I still don’t get why WL XML files can’t be uploaded like the other file
types (= you need to copy-paste).
|
I think that spaces within Remarks were also an issue...
|
|
|
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | | | | Author: | SylvainLS | | Posted: | May 28, 2022 16:14 | | Subject: | Re: It's not liking my XML file | | Viewed: | 33 times | | Topic: | Technical Issues | |
|
| In Technical Issues, WoutR writes:
| | […]
I think that spaces within Remarks were also an issue...
|
Weird.
|
|
| | | | | |
| | | | | Author: | peregrinator | | Posted: | May 27, 2022 22:47 | | Subject: | Re: It's not liking my XML file | | Viewed: | 36 times | | Topic: | Technical Issues | |
|
| In Technical Issues, ramicio2 writes:
| | Please see screen shot. I'm really not understanding what's wrong here.
That's a valid part number. Looks exactly the same as the example XML from
the help article. Formatting (EOL character, UTF-8, etc.) shouldn't matter,
as it's just copied and pasted.
|
What happens when you remove the block referring to that part?
|
|
|
|
|
USA, Pennsylvania
France, Nouvelle-Aquitaine
Netherlands, Zuid-Holland