ge in context:
http://camel.465427.n5.nabble.com/Unicode-characters-not-recognizing-when-reading-file-tp5781028p5781188.html
Sent from the Camel - Users mailing list archive at Nabble.com.
com/file/n5781109/sample_data_export.csv>
--
View this message in context:
http://camel.465427.n5.nabble.com/Unicode-characters-not-recognizing-when-reading-file-tp5781028p5781109.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ontext:
http://camel.465427.n5.nabble.com/Unicode-characters-not-recognizing-when-reading-file-tp5781028p5781038.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ttp://camel.465427.n5.nabble.com/Unicode-characters-not-recognizing-when-reading-file-tp5781028p5781038.html
Sent from the Camel - Users mailing list archive at Nabble.com.
t:
http://camel.465427.n5.nabble.com/Unicode-characters-not-recognizing-when-reading-file-tp5781028p5781036.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Ioannis Mavroukakis <mailto:imavrouka...@gmail.com>
13 April 2016 at 20:15
Are you sure your terminal encoding is UT
I changed my route to
from(file).to("file:/?fileName=out.csv=Append")
It preserved the character.
--
View this message in context:
http://camel.465427.n5.nabble.com/Unicode-characters-not-recognizing-when-reading-file-tp5781028p5781036.html
Sent from the Camel - Users mailing li
in context:
http://camel.465427.n5.nabble.com/Unicode-characters-not-recognizing-when-reading-file-tp5781028p5781032.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I guess my assumption was wrong. I removed tokenizing and its still not
working :(
--
View this message in context:
http://camel.465427.n5.nabble.com/Unicode-characters-not-recognizing-when-reading-file-tp5781028p5781032.html
Sent from the Camel - Users mailing list archive at Nabble.com.
t;UTF-8").split(body().tokenize("\r\n|\n|\r")).streaming()
It's still converting the character to "?". I feel its reading the right
character but its getting corrupted when tokenizing/streaming?
--
View this message in context:
http://camel.465427.n5.nabble.com/Unicode
still converting the character to "?". I feel its reading the right
character but its getting corrupted when tokenizing/streaming?
--
View this message in context:
http://camel.465427.n5.nabble.com/Unicode-characters-not-recognizing-when-reading-file-tp5781028p5781030.html
Sent fro
when the EOL
character is "/r/n" but passes when the EOF character is "/n"
What am I missing?
--
View this message in context:
http://camel.465427.n5.nabble.com/Unicode-characters-not-recognizing-when-reading-file-tp5781028.html
Sent from the Camel - Users mailing list archive at Nabble.com.
F character is "/n"
What am I missing?
--
View this message in context:
http://camel.465427.n5.nabble.com/Unicode-characters-not-recognizing-when-reading-file-tp5781028.html
Sent from the Camel - Users mailing list archive at Nabble.com.
12 matches
Mail list logo