Computed Rich Text && Courier font

I have a Computed Rich Text field in a form. The function is an @DBLookup to a rich text field in a saved document that exists in the DB.

Everything is fine with the @DBLookup, as it returns no errors, the only problem is that in the resulting Rich Text field (that contains the @DBLookup), all of my rich text has the courier font.

The rich text that is being looked up (in the source document) is in Arial, but after the @DbLookup, it is in Courier. Any thoughts? I changed the font in the source to a couple of different fonts and it doesn’t matter, it always displays in Courier after the @DbLookup.

Here’s my @DbLookup, where “body” is the name of the field who’s rich text contents I want to retrieve.

@DbLookup(“notes”:“noCache” ; “”:“” ; “keywordsView” ; “sampleContentDoc” ; “body” )

I really appreciate any help somebody can give me.

Thanks, Kevin

Subject: Computed Rich Text && Courier font

The trick is that the $Fonts won’t match up. You can try tweaking the fonts on the target form by adding a bit of Arial near the top, but your best best is to convert the text to Default Sans Serif. For a bit more explanation, see my article Rich Text 101 - Text, which explains the messed up fonts generally.

Subject: RE: Computed Rich Text && Courier font

Thanks, Ben, for your help. I read your write-up and it was informative. It turns out it was the $fonts field. The way I fixed it was to run an agent that deletes the $fonts field on my source docs (the one’s I’m pulling the RT from, using @dbLookup). This made all the RT into default monospace, then I set the font manually. For my purposes in this app, this was enough for me.

Since you seem to be a bit of a super guru, perhaps you can take a look at another post I have out there that is really giving me a hard time.

Here’s the URL…

http://www-10.lotus.com/ldd/nd6forum.nsf/DateAllThreadedweb/9ffe281efc01d55085256dff0062f5cf?OpenDocument

Thanks again,

Kevin

Subject: RE: Computed Rich Text && Courier font

LOL. Thanks for the compliment, but I am hardly a super guru, except perhaps in the area of rich text. I’ll take a look., but I bet Rod Whiteley or Stan Rogers or someone else beats me to the solution.