Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] Changing the code page from the default 437 to 1252

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] Changing the code page from the default 437 to 1252
 Login/Join
 
Michael L Meagher
Platinum Member
posted
IBI has suggested we change our code page from 437 to 1252 to resolve an issue with special characters not outputting correctly in XLSX format. Are any of you using code page 1252? Did it break any of your reports when you changed over?

This message has been edited. Last edited by: Michael L Meagher,


WebFOCUS 8.2.03 - Production
WebFOCUS 8.2.04 - Sand Box
Windows 2012 R2 Server
HTML, PDF, Excel
In FOCUS since 1980
 
Posts: 115 | Location: Seattle, WA | Registered: April 07, 2015Report This Post
MattC
Guru
posted Hide Post
We had similar issues with outputting reports to Excel. We changed from 437 to 137 without an issue. I am not sure I would go from US English to Windows Latin 1.

Good luck.


WebFOCUS 8.1.05
 
Posts: 496 | Registered: January 04, 2008Report This Post
Michael L Meagher
Platinum Member
posted Hide Post
Thank you.
This what IBI said about the code pages in another site's case:
"Code pages 137 and 1252 are
similar and extend code page 437. For this case code page 1252 resolved the
issue."
I will let you know what happens.


WebFOCUS 8.2.03 - Production
WebFOCUS 8.2.04 - Sand Box
Windows 2012 R2 Server
HTML, PDF, Excel
In FOCUS since 1980
 
Posts: 115 | Location: Seattle, WA | Registered: April 07, 2015Report This Post
<Emily McAllister>
posted
Hello,

There is always a slight risk of problems when switching codepages, but 437 and 1252 are the same byte size and most commonly used characters are in the same place. You may want to look at the codepage character list to check for characters you are using:

Codepage OEM 437

Codepage Windows 1252

Please let us know how it goes.

Emily McAllister
Focal Point Moderator
 
Report This Post
Michael L Meagher
Platinum Member
posted Hide Post
We ended up using code page 1252. There were a couple of characters in the 220 and up range that were not outputting correctly with code page 137. I also had to trap 4,9, 27, and 129 and blank them out.


WebFOCUS 8.2.03 - Production
WebFOCUS 8.2.04 - Sand Box
Windows 2012 R2 Server
HTML, PDF, Excel
In FOCUS since 1980
 
Posts: 115 | Location: Seattle, WA | Registered: April 07, 2015Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] Changing the code page from the default 437 to 1252

Copyright © 1996-2020 Information Builders