Hi all, My experience with ;;W is that it works, but with a peculiarity (perhaps a bug?).
This report (with angle bracket replaced by square brackets for email): [html] [head] [meta name="keywords" content="Mexico travel, ~P1F2:A35;;WT~ travel"] [title]~P1F2:A35;;WT~[/title] [body] [h1]~P1F2:A35;;WT~[/h1] [/body] [/head] produces this result: [html] [head] [meta name="keywords" content="Mexico travel,Acapulco travel"] [title]Acapulco[/title] [body] [h1]Acapulco[/h1] [/body] [/head] I chose a record without special characters so as to not mix the character encoding issue with the peculiarity of ;;W. Notice that the field appears as expected in the title and h1 tags. But, in the meta tag, the space preceding the field value is gone, and there is an extra space after the field value. The workaround that I have found is to use a formula for rv1 which is ' ' P1F2 (prepending a space) and then using it as: [meta name="keywords" content="Mexico travel, ~rv1:A35;;WT~travel"] which produces the correct line: [meta name="keywords" content="Mexico travel, Acapulco travel"] The extra leading space somehow appears at the end of the field value (in spite of the ;;T print indicator). Thanks again for the reminder of the /W startup flag, which does not have this peculiarity. Best wishes, Bruce On May 29, 2010, at 7:33 AM, Brian Hancock wrote: > I think that changed with the very latest release. I think it now > works on > Alphanumeric fields. But I have gotten so used to first saving my > alphanumeric Ax fields to a report variable and then outputting it > as an > AxAz;;W field, I would not have to go and check > > Bye > Brian > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of [email protected] > Sent: Saturday, 29 May 2010 5:42 PM > To: [email protected] > Subject: Re: [Dataperf] Printing accented letters & > othercharacterscorrectlyin HTML pages. > > Hi all, > > Brian is right: > > 1: *in any case*, the /W startup switch is needed to translate DOS- > text > into Latin 1 > > 2: the ;;W report format should *not* be used for alphanumeric fields > (A20). In fact, *nothing* is printed *at all* on such fields when > using a > ;;W format! > > 3: the ;;W report format only works with memo-fields (A20A3)... > > Regards, > Geert. > > > > > On Fri, 28 May 2010 22:50:01 +0200, Brian Hancock > <[email protected]> wrote: >> Hi everyone, >> I thought the the ;;W and /W switch were complimentary but >> different in >> their effect. >> >> My understanding is that the startup switch /W is used to translate >> report characters into the standard ISO Latin 1 web font, and the ;;W >> print mode indicator is used to expand the 5 standard XML entities >> eg< >> into < and to convert bold and underlined text in memo fieldsinto >> html <b> and <u> elements. >> >> I have no experience with foreign language charsets, so it has never >> been an issue for me. >> >> Regards >> Brian _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
