Special slovenian char - č,Č

Hi everyone!
I've got a problem. When i want to distribute report into PDF, some chars become strange.
Char 'č' in report becomes 'è' in PDF.
NLS_LANG is sets to SLOVENIAN_SLOVENIA.EE8MSWIN1250
Code in AFTER PARAMETER FORM trigger:
:destype:='File';
:desformat:='PDF';
:desname:='c:\test.pdf';
Does anybody knows the solution of that kind of problem?

Thanks for reply.
I installed Bodoni Book BT (TrueType) and inserted code to UIFONT.ALI:
[ PDF ]
"Times New Roman" = "Bodoni Book BT"
"Times New Roman CE" = "Bodoni Book BT"
"Arial CE"= "Bodoni Book BT"
"Arial" = "Bodoni Book BT"
"Courier New" = "Bodoni Book BT"
But that does not work. Then i try this code:
[ PDF ]
"Times New Roman" = "Bodoni Book BT (TrueType)"
"Times New Roman CE" = "Bodoni Book BT (TrueType)"
"Arial CE"= "Bodoni Book BT (TrueType)"
"Arial" = "Bodoni Book BT (TrueType)"
"Courier New" = "Bodoni Book BT (TrueType)"
...and still does not work.
What could be wrong?

Similar Messages

Special HTML Characters

Hi,
I encountered a problem with regards to the display of special HTML characters(chr 155). Crystal was not able to correctly display the cahracters. Instead a blank space was displayed. In addition to, when the report is exported to PDF, it is displayed as boxes.
Is there a way to handle display of special HTML chars in crystal?
Thanks

Crystal HTML interpreter is very limited and has been same for years, so it seems unlikley it will chnage any time soon.
As its a specific character that is failing use a replace formul to remove the long dash html and replace with a short dash html which I guess Crystal will recognise.
Replace(yourfield, 'longdashhtml', 'shortdashhtml')
Ian

Problem inserting text with special Hungarian characters into MySQL database

When I insert text into my MySQL db the special Hungarian
characters (ő,ű) they change into "?".
When I check the
<cfoutput>#FORM.special_character#</cfoutput> it gives
me the correct text, things go wrong just when writing it into the
db. My hosting provider said the following: "please try to
evidently specify "latin2" charset with "latin2_hungarian_ci"
collation when performing any operations with tables. It is
supported by the server but not used by default." At my former
hosting provider I had no such problem. Anyway how could I do what
my hosting provider has suggested. I read a PHP related article
that said use "SET NAMES latin2". How could I do such thing in
ColdFusion? Any suggestion? Besides I've tried to use UTF8 and
Latin2 character encoding both on my pages and in the db but with
not much success.
I've also read a French language message here in this forum
that suggested to use:
<cfscript>
setEncoding("form", "utf-8");
setEncoding("url", "utf-8");
</cfscript>
<cfcontent type="text/html; charset=utf-8">
I' ve changed the utf-8 to latin2 and even to iso-8859-2 but
didn't help.
Thanks, Aron

I read that it would be the most straightforward way to do
everything in UTF-8 because it handles well special characters so
I've tried to set up a simple testing environment. Besides I use CF
MX7 and my hosting provider creates the dsn for me so I think the
db driver is JDBC but not sure.
1.) In Dreamweaver I created a page with UTF-8 encoding set
the Unicode Normalization Form to "C" and checked the include
unicode signature (BOM) checkbox. This created a page with the meta
tag: <meta http-equiv="Content-Type" content="text/html;
charset=utf-8" />. I've checked the HTTP header with an online
utility at delorie.com and it gave me the following info:
HTTP/1.1, Content-Type: text/html; charset=utf-8, Server:
Microsoft-IIS/6.0
2.) Then I put the following codes into the top of my page
before everything:
<cfprocessingdirective pageEncoding = "utf-8">
<cfset setEncoding("URL", "utf-8")>
<cfset setEncoding("FORM", "utf-8")>
<cfcontent type="text/html; charset=utf-8">
3.) I wrote some special Hungarian chars
(őű) into the page and they displayed
well all the time.
4.) I've created a simple MySQL db (MySQL Community Edition
5.0.27-community-nt) on my shared hosting server with phpMyAdmin
with default charset of UTF-8 and choosing utf8_hungarian_ci as
default collation. Then I creted a MyISAM table and the collation
was automatically applied to my varchar field into wich I stored
data with special chars. I've checked the properties of the MySQL
server in MySQL-Front prog and found the following settings under
the Variables tab: character_set_client: utf8,
character_set_connection: utf8, character_set_database: latin1,
character_set_results: utf8, character_set_server: latin1,
character_set_system: utf8, collation_connection: utf8_general_ci,
collation_database: latin1_swedish_ci, collation_server:
latin1_swedish_ci.
5.) I wrote a simple insert form into my page and tried it
using both the content of the form field and a hardcoded string
value and even tried to read back the value of the
#FORM.special_char# variable. In each cases the special Hungarian
chars changed to "q" or "p" letters.
Can anybody see something wrong in the above mentioned or
have an idea to test something else?
I am thinking about to try this same page against a db on my
other hosting providers MySQL server.
Here is the to the form:
http://209.85.117.174/pages/proba/chartest/utf8_1/form.cfm
Thanks, Aron

Problem inserting special Hungarian characters into db

Hi,
I've posted this question in the database connection forum
but put it here too because I don't know where to fit better.
I read that it would be the most straightforward way to do
everything in UTF-8 because it handles well special characters so
I've tried to set up a simple testing environment. Besides I use CF
MX7 and my hosting provider creates the dsn for me so I think the
db driver is JDBC but not sure.
1.) In Dreamweaver I created a page with UTF-8 encoding set
the Unicode Normalization Form to "C" and checked the include
unicode signature (BOM) checkbox. This created a page with the meta
tag: <meta http-equiv="Content-Type" content="text/html;
charset=utf-8" />. I've checked the HTTP header with an online
utility at delorie.com and it gave me the following info:
HTTP/1.1, Content-Type: text/html; charset=utf-8, Server:
Microsoft-IIS/6.0
2.) Then I put the following codes into the top of my page
before everything:
<cfprocessingdirective pageEncoding = "utf-8">
<cfset setEncoding("URL", "utf-8")>
<cfset setEncoding("FORM", "utf-8")>
<cfcontent type="text/html; charset=utf-8">
3.) I wrote some special Hungarian chars
(őű) into the page and they displayed
well all the time.
4.) I've created a simple MySQL db (MySQL Community Edition
5.0.27-community-nt) on my shared hosting server with phpMyAdmin
with default charset of UTF-8 and choosing utf8_hungarian_ci as
default collation. Then I creted a MyISAM table and the collation
was automatically applied to my varchar field into wich I stored
data with special chars. I've checked the properties of the MySQL
server in MySQL-Front prog and found the following settings under
the Variables tab: character_set_client: utf8,
character_set_connection: utf8, character_set_database: latin1,
character_set_results: utf8, character_set_server: latin1,
character_set_system: utf8, collation_connection: utf8_general_ci,
collation_database: latin1_swedish_ci, collation_server:
latin1_swedish_ci.
5.) I wrote a simple insert form into my page and tried it
using both the content of the form field and a hardcoded string
value and even tried to read back the value of the
#FORM.special_char# variable. In each cases the special Hungarian
chars changed to "q" or "p" letters.
Can anybody see something wrong in the above mentioned or
have an idea to test something else?
I am thinking about to try this same page against a db on my
other hosting providers MySQL server.
Here is the to the form:
http://209.85.117.174/pages/proba/chartest/utf8_1/form.cfm
Thanks, Aron

Some new info about the advancements in my project:
I've tried to make the insertion at a third hosting
provider's MySQL server with my 'everything is UTF-8' test case and
IT'S DONE! There are my lovely spec chars :-)
Then I've checked the char encoding according -Per's tip in
all of my so far used test MySQL dbs and it reported that
'CHARSET=utf8 COLLATE=utf8_hungarian_ci' so this part seems to me
OK.
I asked my hosting provider where my production app should
run about the db driver and they told it's JDBC (what version of
Jconnect still donno') and they are ready to append
&characterSetResults=UTF-8 to the JDBC url connection string
(somebody told this tip also as a possible soultion) but they asked
me to provide the complete connection string to be used for my
datasource. I've tried to compose it in my localhost development
environment in ColdFusion Admin but it gave me a Connection
verification failed error. So I think I did something wrong and
need help to write the correct connection string that can be passed
to the hosting provider. So the connection string structure I tried
to use in the JDBC URL field of the datasource area of CFAdmin is
something like this:
jdbc:mysql://someipaddresshere/mydbname&characterSetResults=UTF-8
How can it be corrected?
Thanks, Aron

How Create New Folder in KM with Name having Special Character

Hi,
How to create new Folder in KM with name having special character in it.
Right now its not allowing me to create folder when i have Colon( as one of the character in name of the folder.
Is there a way to change this validate?
Any help is appriciated.
Thanks

Hi DK,
I'm not sure about special chars such as ":" but ifyou need to have your folders displaying special language chars (like german chars), have a look into the below link.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30deb229-d570-2910-4aaf-8858e0660f05
Hope that helps.
Ray

Error in parsing special characters

We are getting the following error when we parse a clob with special characters like \226(- special dash char), \231(the "TM"-Trademark logo), \256(the "R"-Registered logo )
"Invalid char in text" when the parser is loaded in the db.
But when we tried to parse this xml file as a file input (parser is now outside the db), it parses the file fine and inserts the data into the db.
We are wondering if there is a difference in parser parsing special characters between inside and outside the db.
We are running xml parser version 2.0.2.7 and if this is a bug and being fixed in later version, is there a workaround for this version

Please try our latest 9.0.1 version

How to escape special xml characters in ALSB

Hi
Can some one tell me how to replace special xml characters < ,> with < and >
I have xml node like below
<payload>
<RatingDetails>
<Action>Add</Action>
</payload>
Using fn-bea:serialize i got xml string as
<payload><RatingDetails><Action>Add</Action></payload>
I want output as below
<payload><RatingDetails><Action>Add</Action></payload>
Appreciate your help
Thanks in Advance

when i use fn-bea:serialize my request xml node converted to xml string.To that string i had escaped special xml characters.
Original request:
<abc>
<a1 >123</a1>
<payload>
<d>345</d>
<e><678></e>
</payload>
</abc>
After using serialize it became as below (everything in one line)
<abc><a1>123</a1><payload><d>345</d><e><678></e></payload></abc>
then i used java callout for replacing special xml chars in payload element,
now my request is
<abc><a1>123</a1><payload><![CDATA[& lt;d& gt;345& lt;/d& gt;& lt;e& gt;& lt;678& gt;& lt;/e& gt;]]></payload></abc>
i dont want my payload data to be enclosed within CDATA but by default i am getting it when i run my xquery for generating request.
This might be because & will not get parsed in xml parser so enclosing evrything in CDATA.
Need solution to remove CDATA and send the payload data as it is..

Time Characteristics not become active gives error in BW 7.4

Hi Experts
We have imported IO's in BW 7.4. Some info Objects are active but some are not getting active specially Time Char.
It gives error while activating. I am attaching the error image. I am looking forward experts input how these Time Info objects can activate.
Thanks
Sweta

There may be inconsistencies with table entries for table 'RSDCHATHJ'. Please check them.
Regards,
Jagan

Save As PDF bugs

Hi All,
In the past, I've always printed to PS via the Distiller instance, but now we have new branding with spot colors used in the FM templates, so now Save As PDF is a must.
I am finding what I think to be a bug, because it is consistently reproducible. When I Save As PDF choosing Page Range: All, I can get all of the pages printed with spot colors and working hyperlinks, BUT the leftmost cell of the first row of every single table is empty, even though the FM screen itself displays the row's contents.
Here's the PDF outcome — please note the first body cell of the table is empty:
All tables in the document have the same issue. I tried opening other documents, they all have the same behavior. I tried importing formats from other tables, creating new table formats, etc., and the same issue persists, even when I copy-special the char formatting of a cell that does print and paste it to the non-printing cell.
Here's what the same section looks like in the FM window:
However, when I Save As PDF choosing Page Range: 1 to [last number], the contents of the first cell in the first column of the first body row of the table displays perfectly fine, but of course none of the hyperlinks work. Here's that outcome:
If that cell didn't print in any table of any output, it would likely be some kind of formatting issue, but that's not what's happening. The cell prints anytime that I do NOT Save As PDF for ALL pages (which leaves the less-than-satisfactory options of either no working hyperlinks, or pgf/char/tbl format colors generating RGB while the imported graphics on the ref pages retain a different color output that's nearer the spot color).
It's annoying to have to choose pages 1 through (whatever is last) to get all of the rows of all of the tables to properly display, but I would do that as a work around if the hyperlinks worked. However, having to choose between either getting all the tables' body rows complete, or having all the hyperlinks working, or getting both of those but no spot color (which is what happens when I print to PS, yielding inconsistent color issues) is making me choose between lose, lose, or lose.
Is there a patch or work around for this issue, or am I going to need to either convince Marketing that branding guidelines for color in their tech doc suite doesn't matter, or pay USD$2000 to get a PDF processor that links everything on the backend just to get all the content and colors right, and add the links post-PDF creation...? Perilous choices. (You can choose to lose your eye, lose your ear, or lose your arm, but you cannot keep all three. Choose. 'Tis but a flesh wound. Monty Python must have written the script.) I'm sorry, I don't mean to sound exasperated (or exaggerated, as you wish); I have never had this kind of issue with FrameMaker before, and I did a lot of talking around here to convince them to buy the new TCS5 as the best solution for their PDF and online help deliverable needs.
Maybe I'm idealistic, but it doesn't seem too much to expect a program as mature as FM to create PDF output that supports hyperlinks, retains spot color, and actually displays all the text relatively WYSIWIG to the FM interface... Surely I'm missing something, or this is a bug with a work-around, right...?
Any insight would be greatly appreciated.
Rene

Thanks for chiming in.
We've got Pantone 307 CVC as the spot color on H2 text and table header backgrounds, as well as several character formats (bullets, hyperlinks, etc.).
In FM, Help > About shows version as 12.0.1.331. Is there a newer patch?
The PDFs are multi-use, because some customers use them as print material, while others use the PDF directly in electronic format. (Audience is international: UK, EU, all over the Americas, as well as some in east Asia and Russia. Yes we have more issues to address than this, but that's another topic for another post at another forum.)
Marketing doesn't like how green the Pantone 307 CVC renders in the PDF when we use the PS>PDF option, so that's why we started using CMYK output = Save As PDF. ("Whether it's in the PDF or printed, it's supposed to be consistent with the blue in the logo, not a teal color.")
I wonder if the better solution might be to find an RGB visual equivalent...
Row background colors alternate 3% and 10% every other row. I have the same results whether I use the standard Dark Gray from the FM color catalog, or Pantone 444 CVC. The only font in play is Calibri. Heading row background is Pantone 307 CVC with 10pt Calibri 100% White text for headings. Cellbody text is 9pt Calibri 100% Black text (colors from FM stock color definitions).
I was going to upload a sample FM file, but I don't see a way to do so...?
Rene

First line not coming when FCC is used

Dear All,
I am using FCC on sender side and the input file is in UTF-8 format....
i am using FCC with key fields on the sender file adapter...
now as the UTF-8 file was having control characters at start the keyfield was not matching the start of file and hence the first line of data was not coming in moni..
i got an answer to this query yesterday where Stefan Grube and Volker replied saying that some of the editors like notepad and word add control chars at start in UTF-8 files and hence UTF-8 files should be created only using editors like TEXTPAD .....
but the problem is that the file would always have control chars at start.. what are the ways of removing it ?
i am thinking of an adapter module at the sender side...
Edited by: Tarang Shah on Jun 11, 2009 6:31 AM

Hi,
I faced this kind of problem previously.
Have used SynTextEditor in which the hidden/special/control chars are clearly visible, delete those chars and use for input.
Alternatively, you can save the file in UTF8 format in textpad and use as input.
Regards

Force jvm to use UTF8 encoding for properties?

hi,
my problem is i cannot display turkish characters that are retrieved from properties file [(key, value) pair].The value may contain turkish characters.
reference : java toc
"..When saving properties to a stream or loading them from a stream, the ISO 8859-1 character encoding is used. For characters that cannot be directly represented in this encoding, Unicode escapes are used; however, only a single 'u' character is allowed in an escape sequence..."
instead of iso 8859-1 or directly representing non-conforming characters in the form of UTF8 encoding , i want to use UTF8 . i dont know is there a way to enforce the encoding to UTF8 .is it possible ?
note : javac -encoding or java -Djava.encoding has no use..
thanx in advance

Hi,
I did a lot of testing with the method of my last posting and ran into the following problem: each character, that is not available in iso 8859-1 is discarded and replaced by a '?'. So when e.g. loading arabic characters you get just "?????" as your property's value.
The only possibility to enable other encodings of Property Files is to replace the encoding of the reader to one that is better suited. So I created a customized class, that inherits from java.util.Properties, and supports loading and storing to any encoding. This class I give here:
* Properties.java
* Created on 11. Juni 2003, 14:08
package xy;
* The <code>Properties</code> class represents a persistent set of
* properties. The <code>Properties</code> can be saved to a stream
* or loaded from a stream. Each key and its corresponding value in
* the property list is a string.
* 
* A property list can contain another property list as its
* "defaults"; this second property list is searched if
* the property key is not found in the original property list.
* 
* Because <code>Properties</code> inherits from <code>Hashtable</code>, the
* <code>put</code> and <code>putAll</code> methods can be applied to a
* <code>Properties</code> object. Their use is strongly discouraged as they
* allow the caller to insert entries whose keys or values are not
* <code>Strings</code>. The <code>setProperty</code> method should be used
* instead. If the <code>store</code> or <code>save</code> method is called
* on a "compromised" <code>Properties</code> object that contains a
* non-<code>String</code> key or value, the call will fail.
* 
* <a name="encoding"></a>
* When saving properties to a stream or loading them from a stream, the
* ISO 8859-1 character encoding can be used. For characters that cannot be directly
* represented in this encoding,
* <a href="http://java.sun.com/docs/books/jls/html/3.doc.html#100850">Unicode escapes</a>
* are used; however, only a single 'u' character is allowed in an escape sequence.
* The native2ascii tool can be used to convert property files to and from
* other character encodings.
* 
* 
* This Properties class is an extension of the default properties class an supports the
* loading and saving from and into other encodings than ISO 8859-1.
* 
* @see <a href="../../../tooldocs/solaris/native2ascii.html">native2ascii tool for Solaris</a>
* @see <a href="../../../tooldocs/win32/native2ascii.html">native2ascii tool for Windows</a>
* @author Gregor Kappler, extended the class of JDK by
* @author Arthur van Hoff
* @author Michael McCloskey
* @version 1.64, 06/26/00
* @since JDK1.0
public class Properties extends java.util.Properties {
 private static final String keyValueSeparators = "=: \t\r\n\f";
 private static final String strictKeyValueSeparators = "=:";
 private static final String specialSaveChars = "=: \t\r\n\f#!";
 private static final String whiteSpaceChars = " \t\r\n\f";
 /** Creates a new instance of Properties */
 public Properties() {
 * Reads a property list (key and element pairs) from the input stream.
 * The stream is assumed to be in the specified character encoding.
 * 
 * Every property occupies one line of the input stream. Each line
 * is terminated by a line terminator (<code>\n</code> or <code>\r</code>
 * or <code>\r\n</code>). Lines from the input stream are processed until
 * end of file is reached on the input stream.
 * 
 * A line that contains only whitespace or whose first non-whitespace
 * character is an ASCII <code>#</code> or <code>!</code> is ignored
 * (thus, <code>#</code> or <code>!</code> indicate comment lines).
 * 
 * Every line other than a blank line or a comment line describes one
 * property to be added to the table (except that if a line ends with \,
 * then the following line, if it exists, is treated as a continuation
 * line, as described
 * below). The key consists of all the characters in the line starting
 * with the first non-whitespace character and up to, but not including,
 * the first ASCII <code>=</code>, <code>:</code>, or whitespace
 * character. All of the key termination characters may be included in
 * the key by preceding them with a \.
 * Any whitespace after the key is skipped; if the first non-whitespace
 * character after the key is <code>=</code> or <code>:</code>, then it
 * is ignored and any whitespace characters after it are also skipped.
 * All remaining characters on the line become part of the associated
 * element string. Within the element string, the ASCII
 * escape sequences <code>\t</code>, <code>\n</code>,
 * <code>\r</code>, <code>\\</code>, <code>\"</code>, <code>\'</code>,
 * <code>\ </code> (a backslash and a space)
 * are recognized and converted to single
 * characters. Moreover, if the last character on the line is
 * <code>\</code>, then the next line is treated as a continuation of the
 * current line; the <code>\</code> and line terminator are simply
 * discarded, and any leading whitespace characters on the continuation
 * line are also discarded and are not part of the element string. 
 * Note:
 * <code>\u</code>xxxx is not supported if the encoding is not
 * ISO 8859-1!
 * 
 * As an example, each of the following four lines specifies the key
 * <code>"Truth"</code> and the associated element value
 * <code>"Beauty"</code>:
 * 
 * <pre>
 * Truth = Beauty
 * Truth:Beauty
 * Truth :Beauty
 * </pre>
 * As another example, the following three lines specify a single
 * property:
 * 
 * <pre>
 * fruits apple, banana, pear, \
 * cantaloupe, watermelon, \
 * kiwi, mango
 * </pre>
 * The key is <code>"fruits"</code> and the associated element is:
 * 
 * <pre>"apple, banana, pear, cantaloupe, watermelon, kiwi, mango"</pre>
 * Note that a space appears before each <code>\</code> so that a space
 * will appear after each comma in the final result; the <code>\</code>,
 * line terminator, and leading whitespace on the continuation line are
 * merely discarded and are not replaced by one or more other
 * characters.
 * 
 * As a third example, the line:
 * 
 * <pre>cheeses
 * </pre>
 * specifies that the key is <code>"cheeses"</code> and the associated
 * element is the empty string.
 * @param inStream the input stream.
 * @exception IOException if an error occurred when reading from the
 * input stream.
 public synchronized void load(java.io.InputStream inStream, java.nio.charset.Charset encoding) throws java.io.IOException {
 if (encoding.equals (encoding.forName("8859_1"))) {
 super.load (inStream);
 return;
 java.io.BufferedReader in = new java.io.BufferedReader(new java.io.InputStreamReader(inStream, encoding));
 while (true) {
 // Get next line
 String line = in.readLine();
 if (line == null)
 return;
 if (line.length() > 0) {
 // Continue lines that end in slashes if they are not comments
 char firstChar = line.charAt(0);
 if ((firstChar != '#') && (firstChar != '!')) {
 while (continueLine(line)) {
 String nextLine = in.readLine();
 if(nextLine == null)
 nextLine = "";
 String loppedLine = line.substring(0, line.length()-1);
 // Advance beyond whitespace on new line
 int startIndex=0;
 for(startIndex=0; startIndex<nextLine.length(); startIndex++)
 if (whiteSpaceChars.indexOf(nextLine.charAt(startIndex)) == -1)
 break;
 nextLine = nextLine.substring(startIndex,nextLine.length());
 line = new String(loppedLine+nextLine);
 // Find start of key
 int len = line.length();
 int keyStart;
 for(keyStart=0; keyStart<len; keyStart++) {
 if(whiteSpaceChars.indexOf(line.charAt(keyStart)) == -1)
 break;
 // Blank lines are ignored
 if (keyStart == len)
 continue;
 // Find separation between key and value
 int separatorIndex;
 for(separatorIndex=keyStart; separatorIndex<len; separatorIndex++) {
 char currentChar = line.charAt(separatorIndex);
 if (currentChar == '\\')
 separatorIndex++;
 else if(keyValueSeparators.indexOf(currentChar) != -1)
 break;
 // Skip over whitespace after key if any
 int valueIndex;
 for (valueIndex=separatorIndex; valueIndex<len; valueIndex++)
 if (whiteSpaceChars.indexOf(line.charAt(valueIndex)) == -1)
 break;
 // Skip over one non whitespace key value separators if any
 if (valueIndex < len)
 if (strictKeyValueSeparators.indexOf(line.charAt(valueIndex)) != -1)
 valueIndex++;
 // Skip over white space after other separators if any
 while (valueIndex < len) {
 if (whiteSpaceChars.indexOf(line.charAt(valueIndex)) == -1)
 break;
 valueIndex++;
 String key = line.substring(keyStart, separatorIndex);
 String value = (separatorIndex < len) ? line.substring(valueIndex, len) : "";
 // Convert then store key and value
 key = loadConvert(key);
 value = loadConvert(value);
 put(key, value);
 * Writes this property list (key and element pairs) in this
 * <code>Properties</code> table to the output stream in a format suitable
 * for loading into a <code>Properties</code> table using the
 * <code>load</code> method.
 * The stream is written using the ISO 8859-1 character encoding.
 * 
 * Properties from the defaults table of this <code>Properties</code>
 * table (if any) are not written out by this method.
 * 
 * If the header argument is not null, then an ASCII <code>#</code>
 * character, the header string, and a line separator are first written
 * to the output stream. Thus, the <code>header</code> can serve as an
 * identifying comment.
 * 
 * Next, a comment line is always written, consisting of an ASCII
 * <code>#</code> character, the current date and time (as if produced
 * by the <code>toString</code> method of <code>Date</code> for the
 * current time), and a line separator as generated by the Writer.
 * 
 * Then every entry in this <code>Properties</code> table is written out,
 * one per line. For each entry the key string is written, then an ASCII
 * <code>=</code>, then the associated element string. Each character of
 * the element string is examined to see whether it should be rendered as
 * an escape sequence. The ASCII characters <code>\</code>, tab, newline,
 * and carriage return are written as <code>\\</code>, <code>\t</code>,
 * <code>\n</code>, and <code>\r</code>, respectively. Characters less
 * than <code>\u0020</code> and characters greater than
 * <code>\u007E</code> are written as <code>\u</code>xxxx for
 * the appropriate hexadecimal value xxxx. Leading space characters,
 * but not embedded or trailing space characters, are written with a
 * preceding <code>\</code>. The key and value characters <code>#</code>,
 * <code>!</code>, <code>=</code>, and <code>:</code> are written with a
 * preceding slash to ensure that they are properly loaded.
 * 
 * After the entries have been written, the output stream is flushed. The
 * output stream remains open after this method returns.
 * @param out an output stream.
 * @param header a description of the property list.
 * @exception IOException if writing this property list to the specified
 * output stream throws an <tt>IOException</tt>.
 * @exception ClassCastException if this <code>Properties</code> object
 * contains any keys or values that are not <code>Strings</code>.
 * @exception NullPointerException if <code>out</code> is null.
 * @since 1.2
 public synchronized void store(java.io.OutputStream out, java.nio.charset.Charset encoding, String header)
 throws java.io.IOException
 if (encoding.equals (encoding.forName("8859_1"))) {
 super.store (out,header);
 return;
 java.io.BufferedWriter awriter;
 awriter = new java.io.BufferedWriter(new java.io.OutputStreamWriter(out,encoding));
 if (header != null)
 writeln(awriter, "#" + header);
 writeln(awriter, "#" + new java.util.Date().toString());
 for (java.util.Enumeration e = keys(); e.hasMoreElements();) {
 String key = (String)e.nextElement();
 String val = (String)get(key);
 key = saveConvert(key, true);
 /* No need to escape embedded and trailing spaces for value, hence
 * pass false to flag.
 val = saveConvert(val, false);
 writeln(awriter, key + "=" + val);
 awriter.flush();
 * changes special saved chars to their original forms
 private String loadConvert (String theString) {
 char aChar;
 int len = theString.length();
 StringBuffer outBuffer = new StringBuffer(len);
 for(int x=0; x<len; ) {
 aChar = theString.charAt(x++);
 if (aChar == '\\') {
 aChar = theString.charAt(x++);
 if (aChar == 't') aChar = '\t';
 else if (aChar == 'r') aChar = '\r';
 else if (aChar == 'n') aChar = '\n';
 else if (aChar == 'f') aChar = '\f';
 else if (aChar == '\\') aChar = '\\';
 else if (aChar == '\"') aChar = '\"';
 else if (aChar == '\'') aChar = '\'';
 else if (aChar == ' ') aChar = ' ';
 else
 throw new IllegalArgumentException ("error in Encoding: '\\"+aChar+" not supported");
 outBuffer.append(aChar);
 } else
 outBuffer.append(aChar);
 return outBuffer.toString();
 * writes out any of the characters in specialSaveChars
 * with a preceding slash
 private String saveConvert(String theString, boolean escapeSpace) {
 int len = theString.length();
 StringBuffer outBuffer = new StringBuffer(len*2);
 for(int x=0; x<len; x++) {
 char aChar = theString.charAt(x);
 switch(aChar) {
 case ' ':
 if (x == 0 || escapeSpace)
 outBuffer.append('\\');
 outBuffer.append(' ');
 break;
 case '\\':outBuffer.append('\\'); outBuffer.append('\\');
 break;
 case '\t':outBuffer.append('\\'); outBuffer.append('t');
 break;
 case '\n':outBuffer.append('\\'); outBuffer.append('n');
 break;
 case '\r':outBuffer.append('\\'); outBuffer.append('r');
 break;
 case '\f':outBuffer.append('\\'); outBuffer.append('f');
 break;
 default:
// if ((aChar < 0x0020) || (aChar > 0x007e)) {
// outBuffer.append(aChar);
// } else {
 if (specialSaveChars.indexOf(aChar) != -1)
 outBuffer.append('\\');
 outBuffer.append(aChar);
 return outBuffer.toString();
 * Returns true if the given line is a line that must
 * be appended to the next line
 private boolean continueLine (String line) {
 int slashCount = 0;
 int index = line.length() - 1;
 while((index >= 0) && (line.charAt(index--) == '\\'))
 slashCount++;
 return (slashCount % 2 == 1);
 private static void writeln(java.io.BufferedWriter bw, String s) throws java.io.IOException {
 bw.write(s);
 bw.newLine();
}I hope you can use this class for your needs as I can. For me it supports any characters so far. If you find some bugs on it, let me know
Regards,
Gregor Kappler

Insert byte[] into postgres text-field

Hi,
i made some tries on using postgresql and jdbc, i noticed that
for some reason the postgres jdbc.driver does not convert
text from the db correct to UNICODE. The db is in ISO-8859-1.
So, i tried to write a workaround to this and was successfull
for reading data. The code is this:
try {
    String sOrt   = null;
    InputStreamReader isString;
    BufferedReader bisString;
    ResultSet result =
        stmt.executeQuery( "select * from adresse.ort" );
    while( result.next() ) {
        isString = new InputStreamReader(
                            result.getBinaryStream( "ort" ),
                            "ISO-8859-1" );
        bisString = new BufferedReader( isString );
        sOrt = bisString.readLine();
...This works fine. Now i also wanted to but a correctly convertet
String in the db.
And i tried so:
try {
    String sOrt = "solal�";    // note the special german char �
    byte[] sOrt_ba = sOrt.getBytes( "ISO-8859-1" );
    pstmt = con.prepareStatement( "insert into adresse.ort " +
                                  "(ort, vorwahl_o, id_land) " +
                                  " values " +
                                  "(?, '00000', 1)" );
    pstmt.setBytes( 1, sOrt_ba );
    int sRows;
    sRows = pstmt.executeUpdate();
}but this sets not the correct character for the special char �
but instead puts the byte-value \366 into the db.
My question is as simple as the answer might be complex, what am
i doing wrong, and how can i accomplish this.

i found a solution for me, its not clean (to be sure its very ugly) but it works for the moment, if anyone has a better idea please tell. I will make the
following.
create a small plpgsql function like this.
CREATE FUNCTION jdbc_clean(text) RETURNS text AS'
    DECLARE
        ret text;
    BEGIN
        SELECT INTO ret replace($1, ''\\\\344'', ''�'');
        SELECT INTO ret replace(ret, ''\\\\366'', ''�'');
        SELECT INTO ret replace(ret, ''\\\\374'', ''�'');
        SELECT INTO ret replace(ret, ''\\\\337'', ''�'');
        RETURN ret;
    END;
' LANGUAGE 'plpgsql'and call this in my Java-method for every String i inserted or
updated in a seperate update query.
I have not written it for now, but i guess this will be working.

Pls help to understand this routine program

Pls help to understand this routine program written in transformation level for a field.
Data a Type /bic/oizsnote_2.
Data: l_len type i,
 l_time type i.
Move source_fields-zztdline+60(60) TO a.
l_len = STRLEN(a).
DO l_len TIMES.
IF a+l_time(1) CN
',<>?/:;"''ABCDEFGHIJKLMNOPQTRSTUVWXYZ abcdefghijklmnopqrstuvwxyz!%^&' & '*' & "()__+=12346567890'
a+l_time(1) = '~'.
Endif.
l_time = l_time + 1.
enddo.
replace all occurrences of '~' in a with space.
Result = a.
not having much exposure in ABAP programming.
Raj

In addition to the above to posts..
HI Raj,
Your routine is used to remove the invalid characters.
IF A+l_time(1) CN
A is a Char which contains the data .*
I_time is used for iteration(itu2019ll check each char by char in a word/Sentence).
*CN u2013 Contains not
,?/:;"''ABCDEFGHIJKLMNOPQTRSTUVWXYZ abcdefghijklmnopqrstuvwxyz!%^&' & '*' & "()__+=12346567890.
These are the Valid chars and numbers which will be accepted by BW system, System will throw an error only when load receives a char which is not there in the above. And that char will be treated as a Invalid Char.
A+l_time(1) = '~'.
What ever the special/Invalid char appears in the load apart from the above mentioned, system will convert them to u2018~u2019
REPLACE ALL OCCURRENCES OF '~' IN a WITH space.
 CONDENSE A.
System will replace all the ~ with space, then condenses the space.
You can do this using RSKC transaction instead of going for routine.

String.replaceAll doesn't work

Hi,
I hope this is the correct forum to post about this problem. It's not a compiler error, it rather seems to be an interpreter or a logical error.
Please consider this test program I wrote to clarify the problem.
public class Test {
    public static void main( String args[]) {
     String someString = "Hello $place!";
     System.out.println( someString.replaceAll( "place", "world"));
     System.out.println( someString.replaceAll( "$place", "world"));
}The method String.replaceAll should replace all occurences of regex with replacement.
Also see http://java.sun.com/j2se/1.4.2/docs/api/java/lang/String.html#replaceAll(java.lang.String, java.lang.String)
So, one should think my test program would have the following output:
Hello $world!
Hello world!Alas, it isn't so. The program outputs the following using SDK 1.2.4:
Hello $world!
Hello $place!The String.replaceAll method doesn't seem to replace occurences if they are preceeded of "$". Or am I just missing something?

The String.replaceAll method doesn't seem to replace
occurences if they are preceeded of "$". Or am I just
missing something?You're right. The method replaceAll is expecting a [url http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html]regular expression. See there how to escape special control chars like $ which means 'end of line'.

How to change charset into extended set?

Hi, my server is setup with en_US.iso8859-1, I would necessity to change this set to get a special accented chars, such as "�,�,�,�" and so on. In practice, I would change this charset to it_IT.iso8859-15.
I tried to change var locale, such as LC_* but it doesn't work, I still have old character set. How to do this?
Thanks

Hi,
If you are attempting this on Solaris 8, then would suggest to have look on info doc 23063 on http://sunsolve.sun.com.
Hope this helps you.
Thanks,
Santosh

Special slovenian char - č,Č

Similar Messages

Maybe you are looking for