text format

[philwatr]

Hi

When i publish in cdml some field I can't keep the text format that I have in my db, like one paragraph and then another.

all the text is one line after another line of text.

is there a solution ?

thanks

------------------

Philippe Waterloos

Webmaster

[elvis_impersonating_penguin]

[FMP-field:FIELD_NAME, break]

This should put the paragraph breaks in where they are supposed to be.. hope this helps ya.

[philwatr]

Thanks a lot, it works

do you know if it is possible to keep the bold text as text.

I try to put a <b> tag like I do in sql

but it doesn't work.

thanks again

[philwatr]

Thanks a lot, it works

do you know if it is possible to keep the bold text as bold text.

I try to put a <b> tag like I do in sql

but it doesn't work.

thanks again

[Vaughan]

It's an all-or-nothing thing... yes you can embed html in the field and use the [FMP-Field: name, HTML] option to get web companion to render it. But if you do this you'll have to use <p> or <br> tags to get the line and paragraph breaks.

[Anatoli]

quote:

---

Originally posted by philwatr:

Thanks a lot, it works

do you know if it is possible to keep the bold text as bold text.

I try to put a <b> tag like I do in sql

but it doesn't work.

thanks again

---

If you use the RAW and you run the field through calculation field for line breaks conversion, you will get the best:

Line breaks AND HTML tags.

I am using that often

[philwatr]

hi

what do you mean by RAW ?

thanks

------------------

Philippe Waterloos

Webmaster

[Vaughan]

In your html format file, there is a cdml element for each field. The code will be of the form [FMP-Field: fieldname, encoding] where "encoding" can be either raw, url, html or break. HTML is the default.

The encoding option instructs Web Companion how to process or display the contents of the field.

The default html option makes web companion encode the text into html, converting special characters like <>& into their html equivilents so they will display as intended on the web page but in doing so all carriage returns and FMP formatting are lost. (To put it another way, whatever *character* you type in the text field in FMP will appear in the web page, but formatting including returns are lost.) Formatting for the field is usually done on the html format file.

The break option keeps line breaks and carriage returns but formatting is similarly lost.

The raw option instructs web companion not to process the field contents in any way. This option is used when you have html embedded in your text field.

The url option is used when the text field is part of a url -- web companion will change characetrs into their url equivilents eg., space is %20.

[Keith M. Davie]

For additional information look in your CDML Reference. You will note some tags which have a subheading titled "Parameter(s)" which discusses the encoding which is available, and also which parameter is used as default which, if appropriate, means you do not have to use the encoding in your tag.

Peace

Keith M. Davie