Characters (&, , ' ,...)

I want to generate a xml file with text from a txt file but i have problems with special characters such as &, <... I'd like to know if there�s any class or library to filter the text in order to generate my xml without problems.
Thank you.

If you are asking if there's a special class that converts & to & and so on, no there isn't. At least not in the standard API.

Similar Messages

Grouping and Decimal characters in rtf templates.

Hi guys and girls,
I’m really struggling with a problem here regarding the decimal characters for the prices in my output.
I'm using XML Publisher 5.6.3.
My goal is to control the grouping and decimal character from my template.
The numbers in the XML data file can either be 10.000,00 or 10,000.00. The format is handled by the users nls_numeric_characters profile option.
The output of the template shall be based on the locale and not the data generated by Oracle Reports. For example: Reports to US customers shall show the numbers in the following format 10,000.00. Reports to our European customers shall show the numbers in this format 10.000,00.
How can I achieve this in my templates? Can it be achieved at all?
Thank you in advance.
Kenneth Kristoffersen
Edited by: Kenneth_ on May 19, 2009 1:30 AM

Hi,
Thank you for your reply.
The problem is that the report is generating the output based on the users profile option nls_numeric_characters.
I have tried to override the users profile option in the before report trigger without any luck. I can alter selects so the query gets the numbers in the right format but then I would have to go through all queryes and reports which seem a bit wrong? Especially for the standard Oracle reports.
BR Kenneth

HT5361 Tools Options Mail format Plain text options Set you characters to 130 Click ok

How do I goto out look to change mail format

smercurio_fc wrote:
Then it sounds to me like this other application is not decoding the attachment correctly, especially if you looked at the attachment yourself after you received it and verified it's correct.
No, no, smercurio. This is charcter encoding here. In older versions of LabVIEW you could specify what character encoding to use when sending an email through the SMTP VIs. But that gave problems since people in certain locales used certain characters that where not transfered right when the wrong encoding was specified, and that encoding stuff is not understood by most people at all, so the wrong selected encoding was rather the rule than the exception. In newer versions of LabVIEW do the SMTP VIs handle the encoding automatically based on the currently used locale on the system.
This change is documented in the Upgrade Notes of LabVIEW and probably happened around LabVIEW 7.1 or 8.0.
A decent mail client will recognize the encoding and convert it back to whatever is necessary before presenting it to the user. The OPs posters server application obviously isn't a smart mail client but probably just some crude text file parser that has no notion of proper mail character encoding and how to deal with it.
I would suppose that there is a chance to dig into the SMTP VIs itself and try to manipulate or disable that encoding altogether in there but that may open a whole can of worms somewhere else. The proper way would be to process the incoming mail by a character encoding aware mail client before passing it to the text parser. On Unix setting up something like this would be fairly trivial.
Rolf Kalbermatter
Message Edited by rolfk on 01-23-2008 10:21 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Report Pdf output getting Junk characters for some boiler Plate fields

Hi All
For Dunning Letter Report registered in Oracle Applications,made changes in Column headings like added customer number as Kunde for German Letter
but in pdf output it's appearing as junk characters even date field is happening like that. It's happening for German, Spanish, Italy and French Letters. Working ok for Netherlands, English.
any input to fix this solution will be great
Thanks
Kamalakar.G

Maybe you check the NLS_LANGUAGE-settings on the client where you "edit" the reports-definition.

XML Publisher report not printing excel output due to special characters

Hello,
I am trying to create a xml publisher report which should display the output in excel. But the program completes with a warning status and the output is displayed as XML instead of excel, with some errors "An invalid character was found in text content. Error processing resource " and i think these errors are due to the special characters(eg: city/province - A Coruña, Cáceres). If i give rownum < 10 in my query, where there are no such characters it works fine and i am getting an excel output.
Tried changing the XML encoding and it doesn't help (both mentioned below)
<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml version="1.0" encoding="UTF-8"?>
Do anyone have a solution for this
Thanks in advance
Edited by: user10317098 on Jan 16, 2012 10:58 AM

Hi,
Check this links that might help you..
https://forums.oracle.com/thread/1018488
http://docs.oracle.com/cd/E10091_01/doc/bip.1013/e05000/toc.htm
Here the Exact solution from Oracle
In the XML PUBLISHER ADMINISTRATOR Resp..
Click the administration..
then Click HTML Output
Then in the Base Image URI Give the url of your application for example
http://Test.Test.com:8000/OA_MEDIA/
And then
Image File Directory give this as per your application setup
/u01/app/oracle/apps/apps_st/comn/java/classes/oracle/apps/media/
Thanks & Regards
Srikkanth.M

Convert smart quotes and other high ascii characters to HTML

I'd like to set up Dreamweaver CS4 Mac to automatically convert smart quotes and other high ASCII characters (m-dashes, accent marks, etc.) pasted from MS Word into HTML code. Dreamweaver 8 used to do this by default, but I can't find a way to set up a similar auto-conversion in CS 4. Is this possible? If not, it really should be a preference option. I code a lot of HTML emails and it is very time consuming to convert every curly quote and dash.
Thanks,
Robert
Digital Arts

I too am having a related problem with Dreamweaver CS5 (running under Windows XP), having just upgraded from CS4 (which works fine for me) this week.
In my case, I like to convert to typographic quotes etc. in my text editor, where I can use macros I've written to speed the conversion process. So my preferred method is to key in typographic letters & symbols by hand (using ALT + ASCII key codes typed in on the numeric keypad) in my text editor, and then I copy and paste my *plain* ASCII text (no formatting other than line feeds & carriage returns) into DW's DESIGN view. DW displays my high-ASCII characters just fine in DESIGN view, and writes the proper HTML code for the character into the source code (which is where I mostly work in DW).
I've been doing it this way for years (first with GoLive, and then with DW CS4) and never encountered any problems until this week, when I upgraded to DW CS5.
But the problem I'm having may be somewhat different than what others have complained of here.
In my case, some high-ASCII (above 128) characters convert to HTML just fine, while others do not.
E.g., en and em dashes in my cut-and-paste text show as such in DESIGN mode, and the right entries
    –
    —
turn up in the source code. Same is true for the ampersand
    &
and the copyright symbol
    ©
and for such foreign letters as the e with acute accent (ALT+0233)
    é
What does NOT display or code correctly are the typographic quotes. E.g., when I paste in (or special paste; it doesn't seem to make any difference which I use for this) text with typographic double quotes (ALT+0147 for open quote mark and ALT+0148 for close quote mark), which should appear in source code as
    “[...]”
DW strips out the ASCII encoding, displaying the inch marks in DESIGN mode, and putting this
    "[...]"
in my source code.
The typographic apostrophe (ALT+0146) is treated differently still. The text I copy & paste into DW should appear as
    [...]’[...]
in the source code, but instead I get the foot mark (both in DESIGN and CODE views):
I've tried adjusting the various DW settings for "encoding"
    MODIFY > PAGE PROPERTIES > TITLE/ENCODING > Encoding:
and for fonts
    EDIT > PREFERENCES > FONTS
but switching from "Unicode (UTF-8)" to "Western European" hasn't solved the problem (probably because in my case many of the higher ASCII characters convert just fine). So I don't think it's the encoding scheme I use that's the problem.
Whatever the problem is, it's caused me enough headaches and time lost troubleshooting that I'm planning to revert to CS4 as soon as I post this.
Deborah

Help - I need more than 1000 Notes of 4000 characters

The 4000 character limitation of Notes and the limitation of 1000 Notes and the length of time it takes to load in Notes make using iPod notes very limiting. I've experimented with a few other options which I explain below, BUT MY QUESTION IS does anyone have any other suggestions on how to work around the 4000 character limitation?
Here is what I have found to be alternative options:
Split your notes into 4000 character blocks using the split command (open Terminal and type "man split" to read about the command)
Install Linux on the iPod. This worked with my older iPod but there isn't a Linux for the newer iPod yet.
Using Contacts "note"
Summary: Uses a manually created Contacts file to store text of up to 243,185 characters in length. If creating files manually requires special formatting for linebreaks. Compatible with music playback and iTunes sync.
Contacts are stored on the iPod according to the vCard standard. vCard stores contact entries in vcf files. A single vcf file can contain any number of vCard entries. The iPod firmware looks for the vcf files in the iPod Contacts folder. The Contacts folder can contain any number of vcf files and will load all of them into memory when viewing contacts.
Contacts synchronized with iTunes are stored in the iSync.vcf file.
You can paste your text content into an Address Book entry and sync it to the iPod via iTunes. There may be limits in the Address Book application regarding the amount of text it will allow.
Using any text editor you can create your own vcf files and place them into the Contacts folder as well. Using the org and note attributes in the vCard entry in a vcf file you can create a contact that can display up to 243185 characters of text. A sample vcf file with a single vCard entry would look like this:
begin:vcard
version:3.0
org:Sample Note
note:You can use Contact notes to get around the 4k limitation of iPod notes. Doing so requires some changes in the syntax of the text however because the vCard format is fairly restrictive.\nFor one thing any line breaks must be converted to a backslash followed by lower case n.\nFor another many symbolic characters must be escaped by preceding them with a backslash.
end:vcard
The "org" attribute names the contact, and the "note" attribute contains the text, up to 243,185 characters of text. While a vCard entry can only have a single note attribute, you can have any number of vCard entries in a single vcf file.
One requirement of this approach is that the text must be edited to a format compatible with the vCard standard. That means that all linebreaks in the text must be converted to a backslash "\" followed by "n", and any symbolic characters should be preceded with backslash.
The negatives of this approach are that linebreaks must be altered and the notes are mixed in with your contacts. But to the positive they are still viewable while music is playing, and they are left alone by the iTunes synchronization process.
This method does not interfere with listening to a song. This method is independent of synchronizing with iTunes.
Using the Calendar "description"
Summary: Uses a manually created Calendar file or Calendar entries in iCal to store text of up to 20,600 characters in length per calendar event. If creating files manually requires special formatting for linebreaks. Compatible with music playback. NOT compatible with iTunes sync if using a manually created file.
The iPod supports the vCal standard for displaying calendar information. Version 1.0 of this standard uses vcs files; and version 2.0 of this standard uses ics files. Most calendar programs can export either vcs or ics files and there is plenty of information available online for how to convert data from a calendar application into one of these formats.
The iPod firmware will display the contents of vcs and ics fles that are located in the iPod Calendars folder.
Calendar events defined in the vCal standard have a description attribute. The iPod firmware displays the description attribute when displaying the calendar event. It is possible to create a calendar specifically for the purpose of storing text in description attributes. You could create a calendar in a calendar program such as iCal and sync it with the iPod via iTunes, or you could create your own calendar file manually. Unfortunately if you sync calendars using iTunes then iTunes will delete all files in the Calendars folder that it does not directly control, so maintaining any kind of external calendar file is not compatible with syncing calendars using iTunes.
The iPod can read both vcs and ics calendar files, but for creating your own you should use vcs because vcs doesn't have a line length limit while ics does and requires special line-wrapping. The iPod will display only the first 20600 characters of the event description.
A simple vcs file with a single fake event would look like this:
BEGIN:VCALENDAR
VERSION:1.0
X-WR-CALNAME:Notes Calendar
BEGIN:VEVENT
DTSTART:20070201T220000Z
DTEND:20070201T230000Z
SUMMARY:Sample note
DESCRIPTION;ENCODING=QUOTED-PRINTABLE:=0D=0ALine breaks need to be converted to an equal sign followed by 0D followed by another equals sign followed by 0A. There is no line length limit, so the text can be as long as you need. There may be a reasonable limit imposed by the iPod calendar interface due to scrolling.
END:VEVENT
END:VCALENDAR
Each Calendar in the file is demarcated by the BEGIN:VCALENDAR and END:VCALENDAR statements. The VERSION statement when set to 1.0 indicates a vcs file (2.0 should be used in an ics file). The X-WR-CALNAME statement can be used to indicate a name for the calendar. If no calendar name is specified the iPod uses "Other".
Each Calendar event is demarcated by the BEGIN:VEVENT and END:VEVENT statements. Each event requires start and end times (DTSTART and DTEND, respectively), a SUMMARY which is the event title, and the DESCRIPTION which is the text you wish to read. Linebreaks in the description text must be converted to "=0D=0A".
The negatives of this approach are that linebreaks must be altered and the notes are attached to specific dates in the calendar so to find them you would need to navigate to those dates. Of course you could put all notes on the same date, or use different dates or even different calendars (within the same vcs file or not) to organize them.
This method does not interfere with listening to a song. This method is NOT compatible with syncing Calendars with iTunes if you are using a manually created file.
Using Music Lyrics
Summary: Uses the Lyrics section of fake songs to store text of up to 10,000 characters in length per song. Does not require special formatting of text. Incompatible with music playback. Requires the text to be stored in iTunes.
iTunes allows the lyrics of a song to be attached to the ID3 tags of the song and viewed on the iPod while the song is playing. Technically lyrics can be up to 256 MB in length, but the iPod will only display the first 10000 characters.
Using lyrics allows notes to be sorted into playlists just as songs are which could be helpful for organizing them. To attach lyrics though there must be a song as well. It is possible to create a very small MP3 that can be used just to attach lyrics to. The process for doing so is described in forum message 2331260, but the short story is:
- In the iTunes main library window, select a track you want to chop up, and select "Get info". The track cannot be a protected AAC track such as those purchased from the Apple Music Store.
- Go to the "Options" tab. Set "Start Time" and "Stop Time", corresponding to the start and finish of the chunk of song you want to chop out. Click "OK".
- Right-click on the track again in the main library window and select "Convert selection to XXX". (The XXX will be whatever file format you happen to have set in your iTunes Importing preferences at the time.)
- After a little while, iTunes will spit out a second, smaller copy of the track, containing just the music between the Start and Stop times you set in the original track. Rename the new track as you please. You can then use iTunes to paste the lyrics to this song clip.
The negatives of this approach are that it requires synchronization with iTunes, requires storage of the text on your computer as well as your iPod, requires the creation of fake songs in your Library, and cannot be used while a song is playing (unless the song you are listening to is the song that has the text you want to read in its lyrics).
Advantages are that this method does not require any editing of the text regarding linebreaks, and this method allows playlists to be used to organize the notes.
While all of these methods work, none of them are completely ideal. If Contacts could be stored in hierarchical folders then that method would be pretty good.
Are there any other alternatives that people have found to work well to work around this iPod limitation of 1000 max notes of 4000 max characters?
Regards,
Brendan

The iPod shuffle is a music player. The iPods with screens have always been more than that. If the iPod didn't have a calendar, contacts, and notes I wouldn't have considered buying one. Music playing is nice, but I certainly didn't want to carry around multiple devices needlessly. The iPod and a simple cell phone are enough. When the iPhone comes out maybe I'll be down to one device.
As for the Palm, having been a Newton user at the time I was never impressed with anything about Palm except its size. The same people who bought cheap PC's instead of Macs bought cheap Palms instead of Newtons. Quantity rather than quality won out.
Apple learned from that and made the iPod a good size to begin with, otherwise it might have suffered a similar fate.
The only PDA capability the iPod lacks is the ability to edit its content independently of the computer. That would be handy, but it turns out hasn't been a critical need for me. More often than not I need to look something up not change something while away from my office. There is a good side to this though, if I lost the iPod I would not have to worry a bit about losing any Contacts, Calendar events, or Music. Notes though, well that is a different matter, those I backup.
I guess one person's music player is another person's PDA.
Regards

How to print Arabic characters in Oracle BI Publisher report

Dear Experts,
Kindly suggest me how to print arabic characters in BI Publisher.
Regards,
Mohan

see link
https://blogs.oracle.com/BIDeveloper/entry/non-english_characters_appears

How to print Special Characters in Sap-Scripts

How to print Special Characters in Sap-Scripts
Thanks,
Ravi

Hi
if u want print special characters we can use hot codes i.e ' ' (single inverted commas). in between these hot codes insert u r special characters.
write ' !@#$%^&*( ) '.
for the above write statement output is
output is !@#$%^&*( )

Filename and path sizes and characters

I am failing to load 4000+ tracks to my Ipod from my XP machine using Itunes 7.50.0.20. This is an Ipod Clickwheel 20GB. I want to load 17.86GB in the now empty Ipod. However it gets so far then stops saying there is not enough space.
I wonder if am I getting the wrong message?
Some of my tracks have very long filenames/paths e.g 124 charactere filenames and 213 character paths. I also have some filenames with " (double quote) in.
Could this be the reason?
If so what characters must I avoid and what size should the filename and paths be limited to?

Filenames and paths are irrelevant. They are renamed on the iPod anyway.
20 GB is not really 20. It is a rounded number all HD manufacturers use. Plus you lose some space due to formatting and the iPod software. There is also meta data for the songs which takes some space.

PDF Preview for a PO template with polish characters shows question marks

When I view the PDF using application I see the polish characters(Boilerplate text) as question marks. But when I view it through XML Publisher Dsktop version 5.5.0 it is fine I have download the new version of adobe 7.08 and I can see the polish characters but the preview in XML publisher in the application stll shows "?"

No I havent configured any fonts on desktop/application .. when I view Document properties on the PDF which works the XML Publisher version 5.5.0 and that of the application is 5.6.0.
In the fonts tab on the desktop version there is one additional one listed fromt he application one - AlbanyWTJ(Embedded Subset)

Non-English characters

Hello, I have read several times that since Java uses Unicode, it solves the problems of non-English characters automatically or something like that.
But my app is not working as expected. Would someone help please?
I have a client/server combo written in Java. The server can send messages in English or Japanese. The Japanese messages are hard-coded as String literals in the server source code. On the client side, they are displayed on a JEditorPane. But the Japanese characters are all garbled. The OS on the server side and client side are, of course, different.
My supposition, which is obviously wrong as it is not working, is that since both ends of communication are Java app, I need not worry about any encoding conversions for String literals.
Suggest me what is wrong here?

How is the required encoding/decoding supposed to be done?
When I didn't worry about non-English characters, I did the following, which WORKED.
// SENDER side
Socket socket ;
PrintWriter out = new PrintWriter(socket.getOutputStream(),true);
String outMessage = "my message";
out.println(outMessage);//RECEIVER
Socket socket ;
BufferedReader in = new BufferedReader(new InputStreamReader(socket.getInputStream()));
String inMessage = in.readLine();When non-English characters are involved, I did the following, which DID NOT WORK. Please someone correct me.
// SENDER side
Socket socket ;
PrintWriter out = new PrintWriter(socket.getOutputStream(),true);
String outMessage = "my message";
String utfString = new String(outMessage.getBytes(),"UTF-8");
out.println(utfString);//RECEIVER
Socket socket ;
InputStreamReader ins = new InputStreamReader(clientSocket.getInputStream(),"UTF-8");
BufferedReader in = new BufferedReader(ins);
String inMessage = in.readLine();The received message is still garbled.

Non-English characters processed correctly by XML Parser 2 XSLT?

I'm trying to transform an XML document (parsed as an XMLDocmument) using an XSL stylesheet (parsed as an XSLStylesheet) and the XSLProcessor class in Java, I encounter the following problem:
Non-US characters such as German umlauts, stored in the XML in &#xxx; style, are not processed properly. "|" (ü), for example, comes out as "C<". Is this a bug in the XSLProcessor class or am I doing something wrong? I'm using this stylesheet declaration:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns="http://www.w3.org/1999/xhtml1/strict"> Or should I mess with the encoding attribute of the ?xml ...? PI?
tia
John Smith

I have not specified any encoding.
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="completeproduct.xsl"?>
<PRODUCT connection="demosample" xmlns:xsql="urn:oracle-xsql">
<xsql:query>
select * from products
</xsql:query>
should i specify encoding
null

Non English characters in FTP transport

Hi gurus,
I have this kind of problem: I need to create text file from internal table (table of 10000 charactes lines) , the file should be created in given ftp server (currently using FM FTP_R3_TO_SERVER).
But, and here is the problem, the text file contains some non English character (Czech to be specific) and after the file is created in ftp server the non English character are replaced by #, characters are fine in the table, even after creating the file on local system everything is fine.
I checked rfc connections, their are Unicode, file is sending in bin mode of ftp (ascii mode had no change, only acsii mode cuts the line to 256 character which is not enough) and parameter of fm FTP_R3_TO_SERVER character_mode is checked.
I will appreciate any help or "kick" in right direction.
Thanks
Martin

Hi Salehashaikh,
I'm not using the FM 'FTP_R3_TO_SERVER' any more to transfer the internal table to ftp, so I do not have the code. Sorry,
but i will try to answer the question.
when you are using function module 'FTP_R3_TO_SERVER' to transfer internal data to ftp the parameter fname should be the name or path of the file you are creating. If you only put file name there for example:
     CALL FUNCTION 'FTP_R3_TO_SERVER'
       EXPORTING
       handle = w_hdl
       fname = 'test_file.txt'
     character_mode = 'X'
this will create file test_file.txt in root directory on ftp.
You could also put there whole path on the ftp for example
      fname = '/directory/test_file.txt'
Other approach will be to change to the directory with function module 'FTP_COMMAND' with parameter command set to cd /directory/ code will look like this:
data: lv_command type string,
         lv_path type string.
constants: lc_change_dir type string value 'cd'.
*body of the program including calls of FM to connect to ftp
concatenate lc_change_dir lv_path into lv_command sepparated by space.
CALL FUNCTION 'FTP_COMMAND'               "this FM will execute any ftp command on ftp server
EXPORTING
   HANDLE                = lv_handle
    COMMAND               = lv_command
TABLES
    DATA                  = lt_result
CALL FUNCTION 'FTP_R3_TO_SERVER'
       EXPORTING
       handle = w_hdl
       fname = 'test_file.txt'
      character_mode = 'X'.
this "code" will create file test_file.txt in the ftp server on given directory from internal table passed to fm ftp_r3_to_server.
list of ftp commands could be found http://www.cs.colostate.edu/helpdocs/ftp.html
good explanation of ftp is here http://wiki.sdn.sap.com/wiki/display/Snippets/ABAPsolutiontoimplementFTP+transactions
I hope this is understandable and helps to solve your problem
Martin
Edited by: Martin Gabris on Feb 3, 2011 1:38 PM

Non english characters in DN cannot be retrieved

We are using Netscape directory server 4, protocal V3. We have a problem related to non-english characters appearing in RDN.
We publish to Ldap entries using the values from database. For example, we have pubulished an entry to Ldap, based on DB values, the entry should have a DN like: ou=Liege BELGIUM ... LGG1a, <other components of DN>. However, when we call netscape search API (search against uid attribute which does not have non-english characters), the search return the entry, but when further call getDN() method on the returned Ldap Entry, it only returns Li, instead of the complete DN value.
It seems the entry is corrupted in Ldap. I wanted to delete the corrupted entry and re create new one to test. I tried many ways, but none of them worked, I think it is because DN is corrupted, there is no key value to identify the Ldap entry for any operation(modify, delete).
You help and insights are much appreciated.
Thanks.
Han Shen

LDAP uses the UTF8 encoding. You must store data in the directory using the UTF8 encoding. This includes DN values. This also means that if you want to be able to view the values in your native character set and font, you must use an application that can convert the UTF8 LDAP data back to the native character encoding. The directory console by default should work for LATIN-1 (ISO 8859) languages if the LOCALE is set correctly.

Non English characters in BIP email

Hi, my report contains Japanese characters, when I view the output in HTML format. It is displayed properly. But when I click on send button , enter email parameters like to, cc, bcc, subject , etc and send it, in the mail I receive, the japanese characters are not getting displayed properly. The same problem occurs for spanish and portugese texts-in general to all non english characters. I am using Oracle Business Intelligence Publisher Release 10.1.3.4. If someone has faced a similar issue, kindly help. Thanks in advance

Suggestions
1) Try with NLS_LANG as
SWEDISH_SWEDEN.WE8DEC
2) Make a paramform and enter via paramform (unencoded)
(This is just for testing purpose)
3) Change machine locale to swedish and try
4) Which reports version is this ?
Please see
BUG 2713695 - NLS CHARACTERS FOR PARAMETERS CHANGE TO QUESTION MARKS WHEN PASSED ON URL BAR
Get in touch with Support to see if this is the issue and if "yes" get a one-off patch.
[    All Docs for all versions    ]
http://otn.oracle.com/documentation/reports.html
[     Publishing reports to web - 10G ]
http://download.oracle.com/docs/html/B10314_01/toc.htm (html)
http://download.oracle.com/docs/pdf/B10314_01.pdf (pdf)
[   Building reports - 10G ]
http://download.oracle.com/docs/pdf/B10602_01.pdf (pdf)
http://download.oracle.com/docs/html/B10602_01/toc.htm (html)
[   Forms Reports Integration whitepaper 9i ]
http://otn.oracle.com/products/forms/pdf/frm9isrw9i.pdf
---------------------------------------------------------------------------------

Characters (&, , ' ,...)

Similar Messages

Maybe you are looking for