|
Home > Archive > BizTalk Server General > February 2006 > Foreign characters getting lost
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Foreign characters getting lost
|
|
| Daniel Gelinas 2006-02-21, 5:51 pm |
| Hello,
BizTalk seems to be replacing all my french characters with "?" or just
removing them. I have simplified my solution to its simplest form, and it's
still doing it. I've tried changing the enconding in my (simple) schema from
utf-16 to others, like ISO-8859-1, with no change.
Am I missing something very simple ? At the moment, I have a custom
pipeline with flat-file dissasembler, through a rather simple schema. The
only process is a subscription from a send port, using the passthru send
pipeline.
Any suggestions would be greatly appreciated !
Daniel
| |
| Tomas Restrepo \(MVP\) 2006-02-22, 7:48 am |
| Hi Daniel,
> BizTalk seems to be replacing all my french characters with "?" or just
> removing them. I have simplified my solution to its simplest form, and
> it's
> still doing it. I've tried changing the enconding in my (simple) schema
> from
> utf-16 to others, like ISO-8859-1, with no change.
What's important here is not changing the schema's encoding itself. Instead,
flat file schemas have a Code Page property that is used by the Flat File
disassembler to interpret the incoming message, and that's the one you want
to set.
That said, keep in mind it's very important that the code page you select in
your schema actually matches the encoding your flat file is saved in.
--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
| |
| Daniel Gelinas 2006-02-22, 5:57 pm |
| Thank you, Tomas. It was exactly that. I really appreciate the help !
For the record, I simply changed the codepage proeprty to use
"Western-European (1252)", and left utf-16 as the default encoding for the
schema itself. All my accents are back.
Daniel
"Tomas Restrepo (MVP)" wrote:
> Hi Daniel,
>
>
> What's important here is not changing the schema's encoding itself. Instead,
> flat file schemas have a Code Page property that is used by the Flat File
> disassembler to interpret the incoming message, and that's the one you want
> to set.
>
> That said, keep in mind it's very important that the code page you select in
> your schema actually matches the encoding your flat file is saved in.
>
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/
>
>
>
|
|
|
|
|