Anyone recognise this coding scheme?

[Rob]

I've trying to import a CSV file exported from another application but it
uses some encoding scheme I've not seen before:

19/02/2007,106478,Bob Elder,Sinking Ship,Macclesfie ld,Cheshire,8," Mike\'s
\Rude Awakening\"""""

The \' sequence is a single quote but that \Rude Awakening\"""" is a little
strange. I think it means take Rude Awakening and prefix it by the next
character after the final "\" but that's a guess.

Anyone recognise this encoding scheme?

Thanks, Rob.

PS. I've asked if we can find out from the original application authors but
they've not responded yet.

[Cor Ligthert[MVP]]

Rob,

This will be not the only CSV file build on some own ideas

Cor

[Stephany Young]

Is there, in fact a line break between "Mike\'s and \Rude Awakening\"""""
or is it, in fact, "Mike\'s \Rude Awakening\"""""

It might sound like a moot point but it could have an impact on how you
interpret it.

I don't think that it is an 'encoding scheme' perse, rather, it looks to
me like an 'escaping scheme' of some description.

In some escaping schemes a \ followed by another character acts as a
signal.

For example, in C# the escape sequence \r means a carriage return and the
escape sequence \n means a line feed. Often you see them together as
carriage return/line feed pair as in \r\n.

Another example, is where you are building a SQL string and you want an
apostrophe to be preserved in a name rather than being treated as a string
delimiter. For this one would code, in VB.Net, " ...'O''Brien'.. ." but, in
C# one would code " ...'O\'Brien' ...".

Again in C#, the sequence \" serves to imbed a quote in a string to give
the same effect as specifing the quote charracter twice in VB.Net.

In the example data you have given, only the \' makes any sense, and so I
suspect that the escaping scheme is bespoke and only the author will be
able to tell you how to interpret the escaped characters.
"Rob" <rob_nicholson@ nospam_unforget table.comwrote in message
news:kI******** **********@news fe4-gui.ntli.net...

I've trying to import a CSV file exported from another application but it
uses some encoding scheme I've not seen before:

19/02/2007,106478,Bob Elder,Sinking Ship,Macclesfie ld,Cheshire,8," Mike\'s
\Rude Awakening\"""""

The \' sequence is a single quote but that \Rude Awakening\"""" is a
little strange. I think it means take Rude Awakening and prefix it by the
next character after the final "\" but that's a guess.

Anyone recognise this encoding scheme?

Thanks, Rob.

PS. I've asked if we can find out from the original application authors
but they've not responded yet.

[Guru]

"Stephany Young" <noone@localhos twrote in message
news:es******** ******@TK2MSFTN GP03.phx.gbl...

Is there, in fact a line break between "Mike\'s and \Rude Awakening\"""""
or is it, in fact, "Mike\'s \Rude Awakening\"""""

HAHAHAHA... RFC 4180 specifies breaks using the Augmented Backus-Naur Form.
If there were a line break there you'd see it.

It might sound like a moot point but it could have an impact on how you
interpret it.

I don't think that it is an 'encoding scheme' perse, rather, it looks to
me like an 'escaping scheme' of some description.

In some escaping schemes a \ followed by another character acts as a
signal.

For example, in C# the escape sequence \r means a carriage return and the
escape sequence \n means a line feed. Often you see them together as
carriage return/line feed pair as in \r\n.

Another example, is where you are building a SQL string and you want an
apostrophe to be preserved in a name rather than being treated as a string
delimiter. For this one would code, in VB.Net, " ...'O''Brien'.. ." but, in
C# one would code " ...'O\'Brien' ...".

Again in C#, the sequence \" serves to imbed a quote in a string to give
the same effect as specifing the quote charracter twice in VB.Net.

In the example data you have given, only the \' makes any sense,

LMAO

and so I
suspect that the escaping scheme is bespoke and only the author will be
able to tell you how to interpret the escaped characters.

LMAO - you're blubbering and babbling incoherently just so you can post and
gain the power of the illusion of puffing up your horribly sunken chest, you
less than witless cretin.

RFC 4180 explictly states that literal double quotes that are not delimiters
must be escaped so that they can be distinguished from delimiters that are
also double quotes.

If double-quotes are used to enclose fields, then a double-quote
appearing inside a field must be escaped by preceding it with
another double quote.

[Rob]

I don't think that it is an 'encoding scheme' perse, rather, it looks to

me like an 'escaping scheme' of some description.

I think you are correct and actually I think the enclosing is broken. I've
now got a way to reach the developers. Consider this string:

Taylor's "Old Head"

The encoding should replace single quote with \' and double quote with \""
which makes sense.

However, what it's doing is shuffling the double quotes to the end so you
get:

Taylor\'s \Old Head\""""

It should be:

Taylor\'s \""Old Head\""

I think it's a bug...

Rob.

[=?Utf-8?B?U3VydHVyWg==?=]

That flame was totally uncalled for.

If you think that every CSV file in the world follows RFC 4180 you are sadly
mistaken.

--
David Streeter
Synchrotech Software
Sydney Australia
"Guru" wrote:

>
"Stephany Young" <noone@localhos twrote in message
news:es******** ******@TK2MSFTN GP03.phx.gbl...

Is there, in fact a line break between "Mike\'s and \Rude Awakening\"""""
or is it, in fact, "Mike\'s \Rude Awakening\"""""

HAHAHAHA... RFC 4180 specifies breaks using the Augmented Backus-Naur Form.
If there were a line break there you'd see it.

It might sound like a moot point but it could have an impact on how you
interpret it.

I don't think that it is an 'encoding scheme' perse, rather, it looks to
me like an 'escaping scheme' of some description.

In some escaping schemes a \ followed by another character acts as a
signal.

For example, in C# the escape sequence \r means a carriage return and the
escape sequence \n means a line feed. Often you see them together as
carriage return/line feed pair as in \r\n.

Another example, is where you are building a SQL string and you want an
apostrophe to be preserved in a name rather than being treated as a string
delimiter. For this one would code, in VB.Net, " ...'O''Brien'.. ." but, in
C# one would code " ...'O\'Brien' ...".

Again in C#, the sequence \" serves to imbed a quote in a string to give
the same effect as specifing the quote charracter twice in VB.Net.

In the example data you have given, only the \' makes any sense,

LMAO

and so I
suspect that the escaping scheme is bespoke and only the author will be
able to tell you how to interpret the escaped characters.

LMAO - you're blubbering and babbling incoherently just so you can post and
gain the power of the illusion of puffing up your horribly sunken chest, you
less than witless cretin.

RFC 4180 explictly states that literal double quotes that are not delimiters
must be escaped so that they can be distinguished from delimiters that are
also double quotes.

If double-quotes are used to enclose fields, then a double-quote
appearing inside a field must be escaped by preceding it with
another double quote.

[=?Utf-8?B?U3VydHVyWg==?=]

HAHAHAHA... RFC 4180 specifies breaks using the Augmented Backus-Naur Form.

If there were a line break there you'd see it.

Re-reading your reply, could you explain what you mean by the above comment?

Because either you don't know what BNF is used for, or you were unable to
adequately communicate your meaning.

BNF is a human readable language used to present the grammar of a file
format. Computers don't use it.

And in any case, according to http://www.rfc-editor.org/rfc/rfc4180.txt,
RFC4180 specifies line breaks that occur inside an "escaped" field are
represented by ASCII &H0A or &H0D, which last time I looked were
non-printing. So you wouldn't see them.

You, sir, appear to have no idea what you are talking about.
--
David Streeter
Synchrotech Software
Sydney Australia
"Guru" wrote:

>
"Stephany Young" <noone@localhos twrote in message
news:es******** ******@TK2MSFTN GP03.phx.gbl...

Is there, in fact a line break between "Mike\'s and \Rude Awakening\"""""
or is it, in fact, "Mike\'s \Rude Awakening\"""""

HAHAHAHA... RFC 4180 specifies breaks using the Augmented Backus-Naur Form.
If there were a line break there you'd see it.

It might sound like a moot point but it could have an impact on how you
interpret it.

I don't think that it is an 'encoding scheme' perse, rather, it looks to
me like an 'escaping scheme' of some description.

In some escaping schemes a \ followed by another character acts as a
signal.

For example, in C# the escape sequence \r means a carriage return and the
escape sequence \n means a line feed. Often you see them together as
carriage return/line feed pair as in \r\n.

Another example, is where you are building a SQL string and you want an
apostrophe to be preserved in a name rather than being treated as a string
delimiter. For this one would code, in VB.Net, " ...'O''Brien'.. ." but, in
C# one would code " ...'O\'Brien' ...".

Again in C#, the sequence \" serves to imbed a quote in a string to give
the same effect as specifing the quote charracter twice in VB.Net.

In the example data you have given, only the \' makes any sense,

LMAO

and so I
suspect that the escaping scheme is bespoke and only the author will be
able to tell you how to interpret the escaped characters.

LMAO - you're blubbering and babbling incoherently just so you can post and
gain the power of the illusion of puffing up your horribly sunken chest, you
less than witless cretin.

RFC 4180 explictly states that literal double quotes that are not delimiters
must be escaped so that they can be distinguished from delimiters that are
also double quotes.

If double-quotes are used to enclose fields, then a double-quote
appearing inside a field must be escaped by preceding it with
another double quote.

[Guru]

"SurturZ" <su*****@newsgr oup.nospamwrote in message
news:BF******** *************** ***********@mic rosoft.com...

That flame was totally uncalled for.

If you think that every CSV file in the world follows RFC 4180 you are
sadly
mistaken.

Please show where I echoed any thoughts of that kind. Failure to put up will
be taken as proof that you attempted to create an argument based on a wholly
imaginary event that never took place.

So, how long have you suffered delusions?