Is it OK for Spanish characters not to be entities in RH8 webhelp output?

We are using RoboHelp 8. We have some Spanish words in our English-language help; these Spanish words use some of the accented characters that aren't present in English. My coworker tried using HTML entity codes to enter these characters in the code view, but she noticed that RoboHelp changed these to the actual Spanish character as soon as she switched back to Design view, and this is how they are in the generated webhelp HTML files as well.
I think this is not a problem. The UTF8 declaration appears in the webhelp output, and the characters seem to appear correctly in the browsers I've tested. Am I correct? Should the output work in older browsers as well?
Thanks,
Tammy

RoboHelp supports 35 languages so the fact that the Design Editor supports those entities does not surprise me.
The following is from the RoboHelp Tour that can be accessed from my site.
RoboHelp 7 introduced the ability to work with 35 languages. In RoboHelp 8, you can now define a language for the project, a language for a topic and a language for a paragraph.
The search works with all the supported languages you use in the project.
There is a lot more information in the help topic "Authoring content in multiple languages".
It sounds like you are just including the odd word so the above may not be relevant, I just wanted to make sure you are aware of this.
I can't help you on how older browsers will handle this but my thinking is they should, they are just HTML entities after all.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Similar Messages

[Solved] Spanish characters not read on NTFS hard drive

Hi there,
Every time I mount my NTFS hard drive with the windows partition on it, I can't read the file names properly. Instead of á, é, í, ó and ú it introduces boxes or interrogation signs. Any idea why that may be?
Last edited by Zespris (2008-11-19 12:28:20)

Yes, it's surely missing support for utf8. I guess that's happening with automount? Are you running Gnome? For I encountered that just shortly ago there. HAL isn't getting the correct locale options. (It can't be KDE for it got fixed there in 4.1.1 or .2)
In Gnome run gconf-editor
/ -> apps -> system -> ntfs-3g -> mount_options: [locale=es_ES.UTF8]
Set locale to whatever your locale is, I just assumed Spain now. That should get you going. Additionally you might want to add ",utf8" to vfat mount_options as well, just in case you use FAT32 drives as well (or will in the future).
If that doesn't help you please tell us where exactly you get this issue and, what DE etc. Good luck.

Spec for this report not able to get values in the output

okSection 1: Document information
Title     PP Total Component Requirement by Sales Forecast Report     Create Date     5/2/2006
Author     Ivie Ng     Revision     1.0     Last changed on
Program type     ( X ) Report    (   ) Form        (   ) Batch input    (   ) Dialog program
Priority     (   ) High       ( X ) Medium    (   ) Low
Frequency      (   ) As require     (X ) Daily     ( ) Weekly       ( ) Monthly         ( ) Yearly
(   ) Conversion
Doc-Ref.
Section 2: Contact Person
Task/Responsibility     Name     Signature     Date
JM Project Manager     Sean Gilgunn
ISS Project Manager     YB Cisse
JM-Business Team Lead     Sathe
Functional Consultant      Ivie
ABAP Consultant     Soh
User Acceptance Test / Approved by
Transport
Section 3: Functional Description
Background (whatever; Ex.Why does this program have to develop?)
This is to allow materials dept to view and analyze total component requirement base on sales forecast ie. budget forecast, inactive version within specific planning horizon.
Requirements
In SOP, material dept will maintain planning data (sales & production plan) in various version.
1. Active version: A00
This version is transferred to demand mgmt as active version. MRP will use this planning data to create order proposals (planned orders, purchase requisitions).
2. Inactive version: 001 999
There are 3 types of inactive version in SOP:
a) Sales forecast 000 799
b) Budge forecast 800 820
c) Forecast report 821 999
This report should allow to read any version of the sales forecast and return the total component requirements in the planning horizon that specify.
Section 3.1: Selection screen
Field name     Technical name     Type of selection field
     (*Please specify Transparent Table and field name)     (X) Single value             ( ) Range             ( ) Required field
          ( ) Single value             (X) Range             ( ) Required field
          (X) Single value             ( ) Range             ( ) Required field
Section 3.2: Program Logic
Business Requirement
This report will allow option to choose to read the source from SOP or COPA.
Input Selection
Main Menu:
o     Total Component Requirement from SOP forecast
o     Total Component Requirement from COPA forecast
If SOP is selected, Source = SOP
If COPA is selected, Source = COPA
Option 1: SOP
1.     Input Layout
Material: _____________    (note: allow multiple materials entry, no entry indicate all materials)
RM Material Group: __________     (note: allow multiple entry, no entry indicate all Mat Grp)
Plant: MY11 (note: default value)
Standard Price as of : _____________ (YYYYMM)
Version: ________    (note: allow F4 option with Version and Description)
Output Type: ____ (Month/Year)
(If the output type chosen is Month, the below is display)
Period From: _________ (YYYYMM)
Period To:      _________ (YYYYMM)
(If the output type chosen is Year, the below is display)
Period From: __________ (YYYY)
Period To:      __________ (YYYY)
2.     Output Layout
Plant: MY11
Source:
Version:
System Date/Time:
Output Layout in Month:
Material     Desc     Component     Desc     UOM     M04.2006     M05.2006     M06.2006     M07.2006     M08.2006     M09.2006     BOM
TO2368          NGK0003          PC                                   TO2368
          SIN96-015          MG                                   TO2368
          SIN96-066F          MG                                   TO2368
          SIN96-066N          MG                                   TO2368
          SIN96-127          GCL                                   WCS2004
          SIN96-055          G                                   WCS2004
          SIN96-110          G                                   WCS2004
          SIN96-007          G                                   WCS2004
          SIN96-002          GCL                                   WCS1003
          SIN96-001          GCL                                   WCS1003
          SIN96-006          GCL                                   WCS1003
          TO2358/511          PC                                   TO2368
          TO2358/512          PC                                   TO2368
          WCS2004          GCL                                   TO2368
          WCS1003          GCL                                   WCS2004
Output Layout in Year:
Material     Desc     Component     Desc     UOM     2006     2007     2008     BOM
TO2368          NGK0003          PC                    TO2368
          SIN96-015          MG                    TO2368
          SIN96-066F          MG                    TO2368
          SIN96-066N          MG                    TO2368
          SIN96-127          GCL                    WCS2004
          SIN96-055          G                    WCS2004
          SIN96-110          G                    WCS2004
          SIN96-007          G                    WCS2004
          SIN96-002          GCL                    WCS1003
          SIN96-001          GCL                    WCS1003
          SIN96-006          GCL                    WCS1003
          TO2358/511          PC                    TO2368
          TO2358/512          PC                    TO2368
          WCS2004          GCL                    TO2368
          WCS1003          GCL                    WCS2004
3.     Header Section:
Header Field: Plant
Print input field Plant.
Header Field: Source
If SOP is selected, Source = SOP
If COPA is selected, Source = COPA
Print Source.
Header Field: Version
Print input field Version, Print RMCP2-VETXT (version description).
Header Field: System Date/Time
Print current system date and time.
4.     Table: S076 (SOP - Sales & Operations Planning)
Read S076 rows with input selection of Material, Plant, Year, Month, Version sorted by Material.
      This table provides sales forecast figure.
Table: MAKT Material Decription
Table: MARA - General Material Data
Table: CDHDR - Change document header
Table: CDPOS - Change document items
5.     Details Section: -
Read S076.PMNUX(Material).                    Note: There will be multiple rows in S076.PMNUX (Material)
Field: Material
Print S076.PMNUX(Material).
Field: Description
Read MAKT.MATNR(Material), Print MAKT.MAKTX.
6.     Read L1 (Level 1) BOM Transaction: CS03
               Where Material = S076.PMNUX (Material), Plant = MY11 (input field), BOM Usage = 1, Status = 01
7.     This is to print BOM component.
If Input Material Group =
Read Component (Material), Component Qty from BOM sorted by MARA.MTART (material type) = ZROH, ZHLB , ZRUH
If Input Material Group <>
Read Component (Material), Component Qty from BOM sorted by MARA.MTART (material type) = ZROH, ZHLB , ZRUH
      Where MARA-MATKL (Material Group) = Input Material Group.
If MARA.MTART (material type) = ZRUH,
      Read L1 (Level 1) BOM Transaction: CS03
              Where Material = S076.PMNUX, Plant = MY11 (input field), BOM Usage = 1, Status = 02.
GET RC29K-BMENG (Base Qty) ***
Field: Material Group
Print MARA-MATKL
Field: Component
Print BOM Component.
Field: Description
Print MAKT.MAKTX.
Field: UOM
Print MARA.MEINS.
Field: Currency
Field: Standard Price
If Input Standard Price Date =
   Print Currency =
   Print Standard Price = 0
Else
Read CDHDR-OBJECTID (Material), CDHDR-CHANGENR (ChgNo)
Where CDHDR-OBJECTID (Material) = BOM Component
And CDHDR-TCODE (Transaction) = MR21
And YYYYMM[CDHDR-UDATE (Date)] = Input Standard Price Date
If NOT Found, look up YYYYMM[CDHDR-UDATE (Date)] 1
I.e.    Input Standard Price Date is 200702, If CDHDR-UDATE (Date) Not Found, look up 200701.
If Not Found, look up 200612 until the record is found    **
If row return > 1, select the latest CDHDR-UDATE (Date)
i.e. If rows return 20070201 and 20070215, Select 20070215    **
Read CDPOS-CUKY_NEW (Currency), CDPOS-VALUE_NEW (New Value)
Where CDPOS-OBJECTID (Material) = CDHDR-OBJECTID (Material)
And CDPOS-CHANGENR (ChgNo) = CDHDR-CHANGENR (ChgNo)
Print CDPOS-CUKY_NEW (Currency)
Print CDPOS-VALUE_NEW (New Value)
8.     If the output type is Year, print Requirement Qty in Yearly bucket.
Requirement Qty = sum[S076-ABSAT (Sales) for current Year] ie 2006
Requirement Qty = sum[S076-ABSAT (Sales) for current Year + 1] ie 2007
Requirement Qty = sum[S076-ABSAT (Sales) for current Year + 2] ie 2008
     If the output type is Month, print Requirement Qty in Monthly bucket.
Field: Month (ie. M04.2006)
Requirement Qty = S076-ABSAT (Sales) * Component Qty / RC29K-BMENG (Base Q)
Print Requirement Qty.
Field: Total Price (ie. M04.2006)
Total Price = Requirement Qty * Standard Price
Print Total Price
Field: Month (ie. M05.2006)
Requirement Qty = S076-ABSAT (Sales) * Component Qty / RC29K-BMENG (Base Q)
Print Requirement Qty.
Field: Total Price (ie. M05.2006)
Total Price = Requirement Qty * Standard Price
Print Total Price
Field: Month (ie. M06.2006)
Requirement Qty = S076-ABSAT (Sales) * Component Qty / RC29K-BMENG (Base Q)
Print Requirement Qty.
Field: Total Price (ie. M06.2006)
Total Price = Requirement Qty * Standard Price
Print Total Price
Field: Month (ie. M07.2006)
Requirement Qty = S076-ABSAT (Sales) * Component Qty / RC29K-BMENG (Base Q)
Print Requirement Qty.
Field: Total Price (ie. M07.2006)
Total Price = Requirement Qty * Standard Price
Print Total Price
Field: Month (ie. M08.2006)
Requirement Qty = S076-ABSAT (Sales) * Component Qty / RC29K-BMENG (Base Q)
Print Requirement Qty.
Field: Total Price (ie. M08.2006)
Total Price = Requirement Qty * Standard Price
Print Total Price
Note: Repeat the requirement qty display in Monthly bucket base on period specified.
Field: BOM
Print L1 BOM which is S076.PMNUX (Material) from Step 6.
If Is end of component,
      Repeat Step 5 for next Material in SOP (S076.PMNUX).
If MARA.MTART (material type) = ZROH,
Perform Step 7 to read next L1 BOM Component.
Perform Step 8 to print Requirement Qty.
If [MARA.MTART (material type) = ZHLB] and [MARA.MATKL(material group) = WP0100, WP0110, or WP0120],
      Go Step 9 to read L2 BOM.
If [MARA.MTART (material type) = ZHLB] and [MARA.MATKL (material group) <> WP0100, WP0110, WP0120],
      Perform Step 7 to read next BOM Component.
      Perform Step 8 to print Requirement Qty.
9.     Read L2 (level 2) BOM for the ZHLB at Transaction: CS03
            Where Plant = MY11(input field), BOM Usage= 1, Status = 01.
GET RC29K-BMENG (Base Qty) ***
10.     Read Component (Material), Component Qty from BOM sorted by MARA.MTART (material type) = ZROH, ZHLB.
Field: Material Group
Print MARA-MATKL
Field: Component
Print BOM Component.
Field: Description
Print MAKT.MAKTX.
Field: UOM
Print MARA.MEINS.
Field: Month (ie. M04.2006)
Requirement Qty = Requirement Qty from L1 BOM * Component Qty / RC29K-BMENG (Base Q)
Print Requirement Qty.
Field: Total Price (ie. M04.2006)
Total Price = Requirement Qty * Standard Price
Print Total Price
Field: Month (ie. M05.2006)
Requirement Qty = Requirement Qty from L1 BOM * Component Qty / / RC29K-BMENG (Base Q)
      Print Requirement Qty.
Field: Total Price (ie. M05.2006)
Total Price = Requirement Qty * Standard Price
Print Total Price
      Note: Repeat until end of Period.
Field: BOM
Print L2 BOM from Step 9.
If is end of component, perform Step 7 to read next L1 BOM component, and Step 8 to print Requirement Qty.
If MARA.MTART (material type) = ZROH,
Perform Step 10 to read next L2 BOM Component.
If MARA.MTART (material type) = ZHLB and MARA.MATKL(material group) = WP0100, WP0110, or WP0120,
      Go Step 11 to read L3 BOM.
If [MARA.MTART (material type) = ZHLB] and [MARA.MATKL (material group) <> WP0100, WP0110, WP0120],
      Perform Step 10 to read next L2 BOM Component.
11.     Read L3 (level 3) BOM for the ZHLB at Transaction: CS03 where Plant=MY11(input field), BOM Usage=1, Status =01.
12.     Read Component (Material), Component Qty from BOM sorted by MARA.MTART (material type) = ZROH, ZHLB.
Field: Material Group
Print MARA-MATKL
Field: Component
Print BOM Component.
Field: Description
Print MAKT.MAKTX.
Field: UOM
Print MARA.MEINS.
Field: Currency
Field: Standard Price
Read CDHDR-OBJECTID (Material), CDHDR-CHANGENR (ChgNo)
Where CDHDR-OBJECTID (Material) = BOM Component
And CDHDR-TCODE (Transaction) = MR21
And YYYYMM[CDHDR-UDATE (Date)] = Input Standard Price Date
If NOT Found, look up YYYYMM[CDHDR-UDATE (Date)] 1
I.e.    Input Standard Price Date is 200702, If CDHDR-UDATE (Date) Not Found, look up 200701.
If Not Found, look up 200612 until the record is found    **
If row return > 1, select the latest CDHDR-UDATE (Date)
i.e. If rows return 20070201 and 20070215, Select 20070215    **
Read CDPOS-CUKY_NEW (Currency), CDPOS-VALUE_NEW (New Value)
Where CDPOS-OBJECTID (Material) = CDHDR-OBJECTID (Material)
And CDPOS-CHANGENR (ChgNo) = CDHDR-CHANGENR (ChgNo)
Print CDPOS-CUKY_NEW (Currency)
Print CDPOS-VALUE_NEW (New Value)
Field: Month (ie. M04.2006)
Requirement Qty = Requirement Qty from L2 BOM * Component Qty / RC29K-BMENG (Base Q)
Print Requirement Qty.
Field: Total Price (ie. M04.2006)
Total Price = Requirement Qty * Standard Price
Print Total Price
Field: Month (ie. M05.2006)
Requirement Qty = Requirement Qty from L2 BOM * Component Qty / RC29K-BMENG (Base Q)
      Print Requirement Qty.
Field: Total Price (ie. M05.2006)
Total Price = Requirement Qty * Standard Price
Print Total Price
      Note: Repeat until end of Period.
Field: BOM
Print L3 BOM from Step 11.
If is end of component,
      Perform Step 10 to read next L2 BOM Component.
If MARA.MTART (material type) = ZROH,
Perform Step 12 to read next L3 BOM Component.
If MARA.MTART (material type) = ZHLB and MARA.MATKL(material group) = WP0100, WP0110, or WP0120,
      Repeat for next level of BOM reading.      ** for future BOM expansion **
If [MARA.MTART (material type) = ZHLB] and [MARA.MATKL (material group) <> WP0100, WP0110, WP0120],
      Perform Step 12 to read next L3 BOM Component.
13.     The report is ALV format and should allow to export to Excel. See example below:
Option 2: COPA
1.     Input Layout
Company Code: ________
Plant: MY11
Material: _____________    (note: allow multiple materials entry, no entry indicate all materials)
Material Group: __________     (note: allow multiple materials entry, no entry indicate all materials)
Standard Price as of : _____________ (YYYYMM)
Version: ________    (note: allow F4 option with Version and Description)
Read V_TKEVS_CL-VERSI (Version), V_TKEVS_CL-VTEXT (Version Description)
Output Type: ____ (Month/Year)
(If the output type chosen is Month, the below is display)
Period From: _________ (YYYYMM)
Period To:      _________ (YYYYMM)
(If the output type chosen is Year, the below is display)
Period From: __________ (YYYY)
Period To:      __________ (YYYY)
2.     Header Section:
Header Field: Plant
Print input field Plant.
Header Field: Source
If SOP is selected, Source = SOP
If COPA is selected, Source = COPA
Print Source.
Header Field: Version
Print V_TKEVS_CL-VERSI (Version), V_TKEVS_CL-VTEXT (Version Description)
Header Field: System Date/Time
Print current system date and time.
3.     Report details: -
Table: CE2ASIA - JM Operating Concern
If input selection is Monthly Report:-
Read CE2ASIA-ARTNR (Product No), Sum[CE2ASIA-ABSMG001 (Sales Qty)]
Where CE2ASIA-BUKRS (Company Code) = Input Company Code
And CE2ASIA-WERKS (Plant) = Input Plant
And CE2ASIA-PALEDGER (Currency Type) = 10
And [CE2ASIA-PERBL (FI Period) > = Input Period From And CE2ASIA-PERBL (FI Period) < = Input Period To]
Group by CE2ASIA-ARTNR (Product No)
If input selection is Yearly Report:-
Read CE2ASIA-ARTNR (Product No), CE2ASIA-ABSMG001 (Sales Qty)
Where CE2ASIA-BUKRS (Company Code) = Input Company Code
And CE2ASIA-WERKS (Plant) = Input Plant
And CE2ASIA-PALEDGER (Currency Type) = 10
And [YYYY[CE2ASIA-PERBL (FI Period)] > = Input Period From And CE2ASIA-PERBL (FI Period) < = Input Period To]
Note: The details similar to Option 1: SOP, refer section (5) to (13)
Section 3.3: Report Layout
Field name     Technical name     Comment
     (Please specify Transparent Table and field name)     (Ex. In case field does not read directly from transparent table but derive from formular or sum or else. Please show the detail how to do that.)
Section 3.3: Unit Test Criteria
Section 4: Technical Description
Section 4.1: Object information
Development class
Transport number
Section 4.2: Input/output file layout (In case upload/download file)
*Please determine structure of file like as below:
No.     Field description     Type (Char,Numeric,)     Length     Note
Section 4.3: Report/Form information
Paper size     Inch 11 8 X 11     Type of printer     ( ) Laser printer     (X) Dot matrix
Output report / Pre-printed Attach
Technical Issue

Hi gurus,actually this program selecion screen is linked to ..as
First screen is .Sop
                      .copa
Again for sop is having a selection screen and in this it is divide based on month and year seperately in two more screens.
same for copa also....
so pls tell me a correct solution where to correct and get values.
Priority is very highhhhhhhhhhhhhh,so pls help me in sorting out this.

Support for English and Spanish Characters

I have created a database with character set WE8iso8859P1. Some of my tables that I imported from MS Access Database using ODBC contain English as well as Spanish characters. When I select the same from the database I just get ? for the non-English characters. What should I do to see the Spanish characters as well?

In the timeline, next to the audio (on the left) is a small drop down box which lets you set the language for the track. You'll see 'En' in both of them at the moment, and you need to change the Spanish one to be for Spanish. You should then be able to complete the build.

Safari for Windows is NOT compatible with Unicode 3.1 CJK characters!

This is an "old" problem since Safari for Windows was initially released. In the meantime, the problem is still not fixed in the latest version 4.0.3 (531.9.1).
Not only Safari (for Windows) does not properly show homepages that contain Unicode 3.1 CJK characters, but it also fails to show Unicode 3.1 CJK characters (it shows "squares" instead) in the whole application, such as Search box and all dialog boxes. Will this be fixed in the next release?
By the way, it is strange that Safari 4 for Mac is Unicode 3.1 compatible.

To speak more precisely, the Safari for Windows doesn't support CJK characters of Unicode CJK Unified Ideographs Extension B.
The following test illustrates the incompatibility of Safari for Windows:
1. Sample text displayed in Firefox 3.0.2 on Fedora 9.
http://farm4.static.flickr.com/3020/3002743180_e026d5c84b.jpg
2. Sample text displayed in Safari 3.x/4.x on Windows XP with "MingLiu Ext-B" (an Ext-B font provided by Microsoft) installed.
http://farm4.static.flickr.com/3224/2971019999_1c113109a9.jpg

List of characters not supported for a field search of type char

Hi,
I have a field of type char.
When we create entries for that field in a table we use special characters like &, etc. When searched it is not supported and not displayed in results.
I suppose it might be because SAP can support for characters of specific ASCII codes.
If you have any list of the ASCII codes supported in search, kindly let me know.
Thanks and Regards,
Jaisish

Hi Jaisish,
as far as I know, there are two "special" characters that act as jokers in a field search
+: standing for one character
*: standing for zero or more characters
You can search for these characters into the content of a field, if you "escape" them. The symbol for escaping is "#" (before the special character + or *).
For example, if you search for "#*", this will search all entries with an asterisk in its content.
I hope this helps. Kind regards,
Alvaro

How can I get the Spanish characters for my N97

I need the spanish characters so I can send SMS in spanish...

To get the accented letters, hold the Sym key down and repeated press the "base" letter until you see the character you want.
Example: Sym & "n" results in "ñ", etc.

HTML + using spanish characters

Hi
If this is a dumb question - forgive me.
Note this is for a site that will be in English & Spansih
(translated pages
in Spanish)
But if I want to include spanish characters on a site do I
need to replace
each spanish character with ascii code or is there another
way to get the
characters to display
e.g.
resúmenes - do i have to enter it into the html as
resúmenes
also
When I view the pages on my pc the spanish characters display
correctly.
Once the pages are uploaded the spanish characters do not
display - why
would this happen?
Thanks
B
www.visit-the-coqui.com/
If you are thinking of a vacation to Puerto Rico
http://gadgetgrapevine.blogspot.com
Latest gadget and other news here

Thanks david for the explaination.
So now I need to figure out how I can save my html as utf-8
without using
notepad (I don't have dreamweaver and have used up my trial
period).
Any one know of any other way of creating a utf-8 html file?
thanks
B
www.visit-the-coqui.com/
If you are thinking of a vacation to Puerto Rico
http://gadgetgrapevine.blogspot.com
Latest gadget and other news here
"David Powers" <[email protected]> wrote in message
news:[email protected]...
>B wrote:
>> could you explain the difference in 'laymans terms'
>
> UTF-8 (Unicode) is designed to handle virtually all
writing systems,
> including Arabic, Japanese, Chinese - and English.
ISO-8859-1 is Western
> European encoding, which handles only those characters
used in Western
> European languages. ISO-8859-1 actually supports the
accented characters
> used in Spanish, but older browsers weren't always
capable of displaying
> them, which led to the use of HTML entities, such as
ñ.
>
> If you select ISO-8859-1 (Western European) in
Dreamweaver, it
> automatically converts all accented characters, such as
those used in
> Spanish, into entities, which makes the code very
difficult to read. If
> you select UTF-8, the accented characters are preserved.
Since English
> doesn't have any accented characters, the encoding is
identical in
> ISO-8859-1 and UTF-8.
>
> If you're working with a database, though, it's very
important not to mix
> the two types of encoding for data that uses accented
characters. If you
> do, the accented characters will be garbled.
>
>> also I posted another ? regarding a BOM warning that
I now get after
>> saving as utf-8 - is this an issue?
>
> I saw that, but didn't reply because you said you used
Notepad. I have no
> idea how Notepad handles the BOM (if I remember
correctly, it stands for
> Byte Order Mark). As the validation warning told you,
older browsers can't
> handle the BOM, so it's best to omit it. Dreamweaver
Preferences let you
> determine whether to add the BOM or leave it out of
UTF-8 pages. By
> default, Dreamweaver omits the BOM.
>
> --
> David Powers, Adobe Community Expert
> Author, "The Essential Guide to Dreamweaver CS3"
(friends of ED)
> Author, "PHP Solutions" (friends of ED)
>
http://foundationphp.com/

How to find out the ASCII Values for Spanish character

Hi,
I had an requirement to store Spanish character and also need to fileter the records based on the Spanish character.
Kindly guide me for below.
To filter the Records which contains spanish characters?
To get the ASCII Values for the particular column?
E.g. we can find out the ASCII value of 'a' by using the syntax select ASCII('a') from dual.
But I want to find the ASCII Values for the particular column value. Ie. name.
E.g., Client name is "Suresh", I want to the ASCII Values for entire name of "Suresh".
Kindly do the needful help / Guidance on this.
Thanks,
Orahar

To expand on what I said in my first post, you want to do something along these lines:
with t (thename) as
select 'Suresh' from dual
select thename
     , substr(TheName, level, 1)
     , ascii(substr(thename, level))
from t
connect by level <= length(thename);The output of the above query is:
THENAM S ASCII(SUBSTR(THENAME,LEVEL))
Suresh S                           83
Suresh u                          117
Suresh r                          114
Suresh e                          101
Suresh s                          115
Suresh h                          104
6 rows selected.Note that the WITH statement is only there to simulate a table for this example. With a table, all you do is get rid of the with and substitute the name "t" for the name of your table (also the name of the column to whatever name the column has in your table).
Lastly, I suggest you post your question along with, an example table and the output you'd like to get in the PL/SQL forum. There are people there that will give you all kinds of great ways of solving that problem.
HTH,
John.

Special Spanish Characters - What do i need?

I am using Photoshop 7 to create graphics for a training series that is being translated into Spanish. I am using FCP 6.03 on a G5. What do I need from Adobe in order to create the graphics in the Spanish language? i only have access to some of the special characters of the language using the Spanish keyboard - I can show a list of the characters, but how do I use the unicode IDs of the characters in Photoshop to display the special characters? I can get the upside down ? and !, and the n with the tilde; the accented vowels are not part of the keyboard combinations.

Scroll to the bottom for Mac key combinations:
http://www.spanishnewyork.com/spanish-characters.html

Special characters not displaying in button label

My production environment is: Oracle Forms 6i connecting to an Oracle 8i database. Forms are Windows client/server. In a form there is a layout of buttons like a QWERTY keyboard. And in the property palette information for each data block, the item is of type "Push Button" and the default Label is set to a specific number which correlates to what that number translates into a special character (i.e. Portuguese, or Spanish characters). So example: CHR196 label = "196". So when at runtime. The following command is executing upon seeing this canvas:
Set_Item_Property('CHR196', LABEL, CHR(196));
So in Forms6i the CHR(196) comes out to be a letter in the alphabet from either Spanish or Portuguese and shows up perfectly.
But NOT in 11g. That environment I'm in is:
Oracle Fusion Middleware Forms 11g on RHEL5 (Red Hat Enterprise Linux version 5) on a 32-bit platform
connecting to
Oracle Database 11g on RHEL5 (Red Hat Enterprise Linux version 5) on a 64-bit platform
using a
Windows based browser (IE7 - Internet Explorer 7).
Could it be due to the forms being in a JVM (Java Virtual Machine)? All I see is a small "square" and this shows up on ALL the button labels. Could it be the NLS_LANGUAGE format of the database? Because when I run the query : SELECT CHR(196) FROM dual on 8i or 11g, the proper character shows up in TOAD or SQL+.
Thanks,

Hello Paul,
I once used hexadecimal coded characters like &xnnn; and they were not transformed. When coding them in decimal, everthing worked fine.
Hth
J�rg

Allowing Spanish characters in PDF forms

I'd like to develop a PDF form primarily for Spanish speaking users. Is it possible to allow Spanish characters in a PDF form? I know setting the "default locale" in LC has nothing to do with this, so is it a matter of system settings (ie. keyboard settings) on the user's machine?
Has anyone every tried this before?
Thanks

Hi,
I am not sure if you are referring to the users creating your forms or the users using your forms.
In terms of typing charactes if the keyboard is set so that you can type spanish characters and the font you are in has those characters then they will be entered into the form, both when creating and filling of the form.
There is nothing specific that needs to be done to the form to allow this, it just accepts the characters that the OS passes to it from the keyboard.
(Point of note: if you are specifying a font to be used this would need to contain the characters that you want to use).
If I have misunderstood the problem then I apologise and if you provide more detail I can investigate further.
Regards
Malcolm

EPMA dimension import issue with spanish characters

We are using special characters for spanish words, like the word Español.
When this was imported into EPMA using the Import Profile and importing a flat file, EPMA added the alias member as espan then showed a square box and then the l. Then, when deploying the app, no errors recorded in EPMA but planning showed errors since SQL query could not deal with this strange character (the square box symbol) in its query. When I manually change the member in the dimension library to Español, then the app deploys. So my relational database clearly accepts the characters.
So, the problem is in the Import of the text file when it has the special character ñ or other spanish characters with the accent marks or tildes. Is there something I need to do when importing a file with this character or other spanish language special characters?
Thanks
using V11.1.1.3 EPMA with weblogic
Jeff

Hi!
We have the same problem. Please somebody could help us?
Thanks in advance!
Analía

Problem with spanish characters

Hello
I am using an existing and proven app written in visual foxpro with a recently installed Oracle11g database (have done this before without problems)
I am using Microsoft ODBC for Oracle and have no possibility of changing this. (always used this without problems)
If I insert a string in in a fixed length char field of the same length of the string (say char(30)) IF THE STRING DOES NOT HAVE SPECIAL CHARACTERS, everything goes as usual. However, if the string contains some spanish language chars (ó, é, á, ñ) the insert fails indicating that the string is too long. I suspect "somewhere" this characters are encoded in double-byte instead of single-byte.
My question is, which is the Oracle setting that allows/prevents this? I need special characters encoded in 1 byte. Language is Spanish.
Some settings that the Oracle DBA passed to me are
NLS_CHARACTERSET = AL32UTF8
NLS_NCHAR_CHARACTERSET= AL16UTF16
Any help will be appreciated, thanks!

In the database character set AL23UTF8 (NLS_CHARACTERSET=AL23UTF8), accented Spanish characters occupy 2 bytes each. This cannot be changed.
Two possible solutions:
-- recreate the database using the character set WE8MSWIN1252
-- redefine the column from CHAR(30), which usually by default means CHAR(30 BYTE), to CHAR(30 CHAR). This means no more than 30 characters but up to 120 bytes (in AL32UTF8).
If you run your application with NLS_LANG=.WE8MSWIN1252 and you do not use byte-oriented SQL functions such as SUBSTRB, INSTRB, or LENGTHB, you will most probably see no functional difference between single-byte storage and multibyte storage of Spanish characters. On the client side, these characters will be single-byte.
-- Sergiusz

Embedding Spanish characters

Hey, I'm building a bi-lingual tool (english and spanish)
that uses all dynamic text fields. Problem: special Spanish
characters are being dropped, even though I have specified them
within the fields' embed-character sets.
The piece is built as such: all copy is stored as nodes on
two data objects – one english, one spanish. Texts are then
populated into the dynamic text fields from the active language's
object. I have specified
"ÁáÉéÍíÓóÚúÜüÑñ¡¿"
as characters to embed. However, the special characters are
displaying incorrectly (or not at all). For example: "Español"
displays as "Espaol". I also ran into a scenario where the "í"
gylph (as in "Sí") displays as a copyright symbol (©).
If anyone has any insight on this, I'd GREATLY appreciate
it.

How comes the text into the movies? If it's loaded from a
textfile, make sure it's saved in UTF-8/Unicode format. In xml
files, you can include this also in the xml header, like this:
<?xml version="1.0" encoding="UTF-8"?>
but it's more important that the text is saved in the right
format, then Flash should display it right.
Here's more on that:
http://www.adobe.com/support/flash/languages/flashlocalization/.
hth,
blemmo

Is it OK for Spanish characters not to be entities in RH8 webhelp output?

Similar Messages

Maybe you are looking for