It’s a JavaScript/JScript/JS… dialect, similar to JSON. Even if you change ‘name =’ to ‘“name”:’, JSON parsers will complain (unless they are buggy) about trailing commas like in ‘WatermarkTextColor = {1,1,1,}’. If you have Windows and notepad++, you can use the FSTool plugin and its JSFormat tool for a more friendly display.
1 Like
I have written a parser for DOP files. As far as I can tell, the syntax is DxO’s own. It might look like all sorts of things, but I don’t know that it is. Simplistic parsers will fail. There are at least two different quoted string formats, one with double quotes and one with double square brackets, that you have to be careful with. JSON would interpret double square brackets as nested arrays, and I don’t think that’s correct.
My parser is written in PHP and I’m happy to share the code with anyone who wants it. As I had to reverse-engineer the syntax from my DOP files, there may be constructs that don’t show up in my DOP files that my parser will fail on. Caveat emptor. My parser reports a syntax error when it encounters something it doesn’t know about, and then I fix it.
If all you want to do is look at a DOP file, there are lots of ways to do that.
1 Like
I’d love to test it out on my Mac.
I need a few questions answered first so that I can make sure you will be able to use the code.
- Are you a programmer?
- Are you familiar with PHP?
- Do you have PHP installed on your Mac?
- Are you familiar with parsers?
- Do you know how a recursive descent parser works?
I can give you the code regardless of your answers, but, for example, if you are not a programmer, it won’t do you much good.
you forgot to ask him SSN# & DOB …
Thank you for share with us.
My code won’t do anyone any good without some help. Please answer the questions listed in response # 85 above. The code is PHP code, and the parser won’t do anything on its own, so its not very useful to non-programmers.