Long text editor - sign problem

[Former Member]

Hi,

Currently I am facing an issue that the & sign is not being displayed correctly in the Long text editor. It is shown as '<(>&<)>' in the transaction once I input my value in the graphical editor , save and come back.

Please help...

Thanks

Praneeth

[Former Member]

Hi,

Currently I am facing an issue that the & sign is not being displayed correctly in the Long text editor. It is shown as '<(>&<)>' in the transaction once I input my value in the graphical editor , save and come back.

Please help...

Thanks

Praneeth

[RaymondGiuseppi]

We have opened such messages in OSS via service.sap.com, but not fully answered today. When using Word Editor, special characters are encapsulated via strings "<(>" and "<)>" (characters like "&" or ",")

Only found one OSS note ([Note 1388221 - Long text: Display of SAPscript control chars in short text|https://service.sap.com/sap/support/notes/1388221] (and two related notes) where SAP removed the "<(>" and "<)>" string before copy to short text)

But the problem happens in many programs which do not remove the "wildcard" characters

- moving leading part of text to short text

- displaying long text input with Word in container using class like CL_GUI_TEXTEDIT.

So I suggest you to open such a message via [Report a Product Error - Customer Messages|http://service.sap.com/message]

Regards,

Raymond

Edited by: Raymond Giuseppi on Aug 24, 2011 8:44 AM

- Another [Note 1555083 - Delinking the short text and long text in Routing / BOM|https://service.sap.com/sap/support/notes/1555083]

[Former Member]

Hi Raymond,

I have implemented SAP note 1536828 which actually talks exactly about the same error which I am facing but still it does not seem to resolve my issue. It is happening only when the '&' is inserted at certain locations in the text on word editor and at some places it is doing a correct conversion without the wild characters.

Anyhow I am raising an OSS note for the same. I am using this text to display on the smart form and is a client facing form and it is really a confusion to the customer if we send him an Invoice with wild characters.

Regards

Praneeth

[Sandra_Rossi]

Hi Praneeth,

May I know what is really the issue with <(>&<)> ?

AFAIK, this code is only found internally (or when you display the internal format, i.e. using SAPscript old editor), but it is always translated into & at all other outputs. The only situation I know where it is not well displayed is bug in custom programs, which forget to convert long texts from internal to external format. If you use CONVERT_ITF_TO_ASCII function module, you'll get a correct & character.

Sandra

[RaymondGiuseppi]

Hello Sandra,

but it is always translated into & at all other outputs

There are still transactions in my current systems too that don't yet convert the "internal" format of those texts, can you try a transaction like IW32 on your system, we have still the problem in this standard transaction (ECC6, Ehp4) the text is not converted when copied to short text as well as when displayed in the standard transaction itself (which use good old one class cl_gui_textedit)

Regards,

Raymond

[Sandra_Rossi]

Hi Raymond,

I was not aware of this. But only by reading the op's comments, I'm not sure he's talking of these few bugs? I often see developers take the long text as is and print it, it's why I posted the initial question

Sandra

[Former Member]

Hi Sandra,

I am also talking about the same issue in IW32 and the internal SAP program is not doing a correct conversion due to which the wild characters are entered into the long text window on IW32.

I received an answer for my OSS note and they say it is how the system is ..please see the comments from SAP below ...

26.08.2011 - 12:37:23 CET - Reply by SAP

Hi,

I am sorry, but the behaviour which you describe is correct.

I will try to explain the meaning of the special characters and

why they have to be there: In Sapscript there are some characters,

which have a special meaning. E.g. a '&' starts a symbol, a '<'

starts a character format, etc. So if you use e.g. a '&' in your

text, this Sapscript needs the information, whether the '&' shall

start a symbol or whether it shall be printed as '&'.

So if you want to print the '&' as '&', the character must be masked.

This is done via the characters <(>...<)>. So when you enter

a '&' (and when it is not sure, whether it may start a symbol),

the Sapscript internally saves the character as <(>&<)>.

Usually this should be no problem: If you process the text via

the Sapscript, you will not notice the masking characters. The

graphical editor will not display them. And if you print the text

via a Sapscript form or a Smartform, you will not see them.

Only if you look into the internal table, which is returned

by EDIT_TEXT or READ_TEXT, you will see the characters.

(and the old Sapscript editor displays them, too, because it

is displays the text in the Sapscript-internal format).

If you process the internal table yourself, you must take this

into consideration. E.g. if you want to convert the

Sapscript-internal ITF format which is returned by EDIT_TEXT

into 'normal' text format, you can use the function module

CONVERT_ITF_TO_ASCII.

Kind Regards,

Marian O'Connell

Support Consultant

AGS Primary Support

Visit the Enterprise Asset Management (EAM) forums:

[Sandra_Rossi]

Hi Praneeth,

SAP's answer looks very much like mine. So probably, SAP and me didn't understand your issue

Unfortunately, I don't have access to IW32 so I can't have a look. But I suggest you to ask SAP support again because they just explained you how it works usually, maybe they didn't have a deeper look in your system, or maybe you didn't provide a reproducible case?

Sandra

[RaymondGiuseppi]

For information, the answer of SAP to same problem (IW32 and other transactions) was

Our developers have looked at this issue but have now reported that
it is techinically not possible to provide a specific correction to
resolve this.
This is because of the way SAPscript editor is transferring controls.
Effectively a solution requires multiple adjustment to ensure the text
controls are recognised in the same way by all applications that use
the common SAPscript editor.
For the moment we advise that users avoid the special charachters where
possible.

I don't expect a solution for some time...

Regards,

Raymond

[Former Member]

HI,

Goto Change editor or word editor and then insert the it.

Regards

Shiva