Error: Text value unmappable in the current server locale
Locked
Error: Text value unmappable in the current server locale
 
|
|
Re: Error: Text value unmappable in the current server locale
|
|
What's the context? Saving or opening a
data source?
This can happen when the data file is in a different encoding than the current locale encoding that Statistics is running in, particularly in code page mode. For example, opening a file with Japanese encoding when running Statistics in an English locale, or saving a Unicode file that contains various text values in different languages and then saving the file as a text file in a code page encoding. Rick Oliver Senior Information Developer IBM Business Analytics (SPSS) E-mail: [hidden email] From: Bob Walker <[hidden email]> To: [hidden email], Date: 11/04/2013 03:18 PM Subject: Error: Text value unmappable in the current server locale Sent by: "SPSSX(r) Discussion" <[hidden email]> Means…? Regards, Bob Walker Surveys & Forecasts, LLC www.safllc.com |
Re: Error: Text value unmappable in the current server locale
|
|
Thanks Rick, Context: I have been writing out text files to be pulled into an Oracle data warehouse, and Unicode / byte order marked files cannot (according to my client) be read in. I
was attempting to open and run *.sav files using locale encoding, and that is when the error message appeared. I think that the solution is to run in ‘standard’ Unicode mode, except for the last block of my code, which WRITEs out various files. I think using PRESERVE and RESTORE for
that one block may be the solution in this situation. Bob Walker Surveys & Forecasts, LLC From: Rick Oliver [mailto:[hidden email]]
What's the context? Saving or opening a data source?
|
Re: Error: Text value unmappable in the current server locale
|
|
For what it's worth, In release 22, you
can write out Unicode text data files without a BOM. The SAVE TRANSLATE
and WRITE commands both have a keyword BOM=YES|NO on the ENCODING subcommand.
Rick Oliver Senior Information Developer IBM Business Analytics (SPSS) E-mail: [hidden email] From: Bob Walker <[hidden email]> To: Rick Oliver/Chicago/IBM@IBMUS, Cc: "[hidden email]" <[hidden email]> Date: 11/04/2013 04:24 PM Subject: RE: Error: Text value unmappable in the current server locale Thanks Rick, Context: I have been writing out text files to be pulled into an Oracle data warehouse, and Unicode / byte order marked files cannot (according to my client) be read in. I was attempting to open and run *.sav files using locale encoding, and that is when the error message appeared. I think that the solution is to run in ‘standard’ Unicode mode, except for the last block of my code, which WRITEs out various files. I think using PRESERVE and RESTORE for that one block may be the solution in this situation. Bob Walker Surveys & Forecasts, LLC www.safllc.com From: Rick Oliver [mailto:oliverr@...] Sent: Monday, November 04, 2013 4:44 PM To: Bob Walker Cc: [hidden email] Subject: Re: Error: Text value unmappable in the current server locale What's the context? Saving or opening a data source? This can happen when the data file is in a different encoding than the current locale encoding that Statistics is running in, particularly in code page mode. For example, opening a file with Japanese encoding when running Statistics in an English locale, or saving a Unicode file that contains various text values in different languages and then saving the file as a text file in a code page encoding. Rick Oliver Senior Information Developer IBM Business Analytics (SPSS) E-mail: oliverr@... From: Bob Walker <rww@...> To: [hidden email], Date: 11/04/2013 03:18 PM Subject: Error: Text value unmappable in the current server locale Sent by: "SPSSX(r) Discussion" <[hidden email]> Means…? Regards, Bob Walker Surveys & Forecasts, LLC www.safllc.com |
Re: Error: Text value unmappable in the current server locale
|
|
Um, yeah, that’s important – thank you! Bob Walker Surveys & Forecasts, LLC From: Rick Oliver [mailto:[hidden email]]
For what it's worth, In release 22, you can write out Unicode text data files without a BOM. The SAVE TRANSLATE and WRITE commands both have a keyword BOM=YES|NO on the ENCODING
subcommand.
|
Re: Error: Text value unmappable in the current server locale
|
|
In reply to this post by Robert Walker
This means that the current character encoding
you are using is not available on the platform you are using. For
example, in code page mode running in an English locale, you might have
data encoded in Japanese code page 932. If you are moving data between,
say Mac and Windows, the code page definitions are slightly different,
so you might get this warning, but in that situation you can almost always
ignore the warning.
If you see question marks in places where there are extended characters, then there is a serious mismatch between the encodings. In general, using Unicode mode if you have data that might have encoding problems is the way to go. Jon Peck (no "h") aka Kim Senior Software Engineer, IBM [hidden email] phone: 720-342-5621 From: Bob Walker <[hidden email]> To: [hidden email], Date: 11/04/2013 01:08 PM Subject: [SPSSX-L] Error: Text value unmappable in the current server locale Sent by: "SPSSX(r) Discussion" <[hidden email]> Means…? Regards, Bob Walker Surveys & Forecasts, LLC www.safllc.com |
| Free forum by Nabble | Edit this page |