Remove blank spaces in Include Text used in Smartforms

[former_member553202]

Hi All,

we are using include text to print Item long description in smartform. Item description is comming correctly in output but in some cases, when item long description is maintained with extra blank spaces, it is not removing blank spaces in output instead blank spaces converted to hashtag #.

item long description: "Long Description "

it is converting to "Long Description ########" in smartform output. someone has any idea if we can do something with include text???

[former_member553202]

Hi All,

we are using include text to print Item long description in smartform. Item description is comming correctly in output but in some cases, when item long description is maintained with extra blank spaces, it is not removing blank spaces in output instead blank spaces converted to hashtag #.

item long description: "Long Description "

it is converting to "Long Description ########" in smartform output. someone has any idea if we can do something with include text???

[arpan_shukla]

Hi Dinesh,

Usually "#" comes for any character which is not defined in that font, in your case it can be due to extra "Tabs space" in the description. Try to rewrite the items's long description or use READ TEXT fm to fetch the text data and then use condense command to remove additional spaces. Also check the Paragraph type and font used for the text.

I hope this will resolve you issue.

Thanks and Regards,

Arpan Shukla

[hedvig_rohonyi]

Hi Dinesh,

The space character that prints as # seems to be the NBSP character (non breakable space, U+00A0).
A # usually means that the character does not exist in the system character set or that it is not known to the device type.
If you had a Unicode system, you could have created the spool via device type SWINCF, which supports character U+00A0.

I suppose the root case of problem is in the step of creating /save the ITF text. Befor function SAVE_TEXT sould be called the function CONVERT_STREAM_TO_ITF_TEXT to remove the NBSP characters by the application.

Best regards,
Hedvig

[RaymondGiuseppi]

I agree with king Hedvig Rohonyi, the task of correcting the text should not belong to the printing form, so look for OSS notes if the long texts are generated in a standard transaction, or use suggested FM, or even good old SCP_REPLACE_STRANGE_CHARS or CLM_FIND_AND_CONV_WRONG_CHAR FM to 'clean' the text before saving text.