is there a spec doc soemwhere?

not yet - this is what issue 24388 is about
Sorry, but since we're required to add tasks to CWS before actualy starting with
the task, I needed to submit these issues without a preliminary spec.

change subcomponent to 'none'

edited text\shared\02\01170101.xml

.

UFI: pls verify in CWS helpcontentbeta and close

Set to correct status 'resolved fixed'.

not fixed in cws helpcontentbeta
I can't found anything in the help about Rich Text Controls.

reassign to ufi

Please enter "rich" in the Index Search term box. You should see the Controls
help page with "Text type" at the top. This is the help text:

"Allows you to use line breaks and formatting in a control field, such as a text
box or label. To manually enter a line break, press the Enter key. Select
"Multi-line with formatting" to enter formatted text."

aargh - this weird Issuzilla task handling!

please look once more

.

Oh, you mean this single sentence 

"Select "Multi-line with formatting" to enter formatted text"

describe the whole new MS interoperability Feature "Rich Text Control".

You are joking, don't you?

Please see the spec
http://dba.openoffice.org/specifications/forms/rich_text_control.sxw for details
what is possible with rich text controls and what not.

reassign to ufi

Yes, I know the spec doc. And no, I will not quote all the attributes that a
rich text control can have: 
start_of_quote:
Font, Font style (bold/italic), Font size, Font Language, Underlining,
Strikethrough, Text line color, Font color, Word line mode, Relief, Outline,
Shadow, Position (Superscript/Subscript), Scaling, Kerning.
Additionally, the following character attributes are available when Asian
Language support is enabled in the OpenOffice.org installation: Emphasis mark,
Emphasis mark position.
Yet more additionally, the attributes Font, Font style, Font size and Font
Language are available in an Asian and/or complex text version, if and only if
"Asian language support" respectively "Complex text layout support" is enabled
in the OpenOffice.org installation.
The semantics of these attributes follows their semantics in other contexts, for
instance when used for the text in a shape. The reader is referred to the
"Character" dialog for such text, in particular the well-known tab pages "Font",
"Font effects", and "Position". Every attribute on these tab pages will be
supported by the rich text control, and every attribute supported by the rich
text control will be available on these tab pages.
end_of_quote.
This is of no help to the normal user. For the normal user, the information that
it is possible to apply formatting to the contents of a text box is sufficient.
The user can then select all the formatting he wants; it is visible in the UI
what is available. There is no need to provide detailed lists. We even have no
lists which attributes can be applied to normal text. So why for text on a
control which is used at most by one out of a million users?

Hi,

you don't need to explain all the formats you can apply to text, of cource,
however may be you can provide a little bit more information about this new
feature. For example you can not bind this kind of controls to a database field. 

Why shouldn't we say what we can?
For me this feature is till not enough documented,
But may be any other has an other opinion.  MSC -> FS , FPE , TZ: Any opinion?

Bye Marc

FPE:
> Why shouldn't we say what we can?
Because Online help is not a marketing instrument. We describe what is needed
for the user to operate the software. I took a look and IMO the documentation is
basic but ok. If you think that more is needed we should open an RFE for OOo later.

> For me this feature is till not enough documented,
We don't document features as such. If I understood correctly, the feature
manifests in one single drop down list entry. We document it using one single
clearly understandable sentence. For me that's fine.

I kind of agree to both sides. On the one hand, we don't really want to list
every single attribute, for most users it's sufficient to know that they can
somehow "format" the text in the control.

On the other hand, IMO it would be nice to also document the restrictions which
this mode has, in particular, as msc said, that formatted text cannot be stored
in a database field, and thus the respective controls in the property browser
are disabled then.

There are other implications of chosing "text with formattin", but of much less
interest (like scrollbars, line ends, and such).

So, could we agree on adding the DB restriction to the text as some "Note: ...!"?

After choosing the "Text type" "Multi-line with formatting", the Data tab page
on the control's properties window disappears. This will be documented.
(Although it looks like a bug). This should fix the reference help for this control.
On the other hand, we do not have a how-to guide on using controls at all. But
we need several guides for those features. And when xforms will appear one day,
it is much more important. This is another topic not to be covered by this bug.

.

.

FPE: reset target

added a warning to text\shared\02\01170101.xhp

.

FPE: Pls verify in hc680postbeta
Hint for QA: index entry "rich text control"

fixed

FPE: Due to time constraints removed from CWS

FPE: Due to time constraints removed from CWS

verified in current master m106 -> close this issue now.