|
Gotcha - So I'm curious then what you mean by 'Formatting the received message text' then. I guess you are saying that a message has come in with these characters embedded. What is it you plan to do with that data that requires you to handle these characters? JPW -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of M. Lazarus Sent: Monday, 26 September 2005 11:40 To: Midrange Systems Technical Discussion Subject: RE: Message text formatting Jim, I think that it's the "QMHRTVM - Retrieve Message" API. I'm referring to the paragraph formatting characters, not the message data characters. -mark At 9/25/05 07:27 PM, you wrote: >I've worked a lot with formatting message text, but I'm not sure I >completely understand your question. Could you give an example of where >you are getting the &N &B etc.? > >One API that I think you might need is QMHRTVM - Retrieve Message. It >will take a message text in parm form and expand it out into full text. >You will have to know where the message file is that has that message ID >in it though.... > >JPW > >-----Original Message----- >From: midrange-l-bounces@xxxxxxxxxxxx >[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of M. Lazarus >Sent: Monday, 26 September 2005 10:13 >To: midrange-l@xxxxxxxxxxxx >Subject: Message text formatting > > > Is there an API to format retrieved message text? I mean resolving >the >&N, &B, &P codes. If no API is available, does anyone have a routine to >do >this? It's not a huge deal to write one, but I would rather avoid >reinventing the wheel. Thanks. > > -mark > >-- >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing >list >To post a message email: MIDRANGE-L@xxxxxxxxxxxx >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/mailman/listinfo/midrange-l >or email: MIDRANGE-L-request@xxxxxxxxxxxx >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l. > > >###################################################################### >This message was scanned for compliance with Foodstuffs email policies >###################################################################### >This message has been sent from Foodstuffs (Auckland) Limited ("Foodstuffs"). > >The information contained in this message and or attachments >is intended only for the person or entity to which it is >addressed and may contain confidential and/or privileged >material. Any review, retransmission, dissemination or other >use of, or taking of any action in reliance upon, this >information by persons or entities other than the intended >recipient is prohibited. If you received this in error, >please contact the sender and delete the material from any >system and destroy any copies. > >The views and opinions expressed in this message may be those >of the individual and not necessarily those of Foodstuffs, >and are not given or endorsed by it. > >Please note that this communication does not designate an >information system for the purposes of the Electronic >Transactions Act 2002. > >-- >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@xxxxxxxxxxxx >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/mailman/listinfo/midrange-l >or email: MIDRANGE-L-request@xxxxxxxxxxxx >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.