On 28/02/2006, at 4:10 AM, Andy Pepperdine wrote:

On Monday 27 February 2006 16:01, G. Roderick Singleton wrote:
On Mon, 2006-02-27 at 09:34 -0600, Rod Engelsman wrote:
G. Roderick Singleton wrote:

[snipped]

I'll agree with you that once you understand how it works, it's fairly easy to deal with. I just don't think that a style is where folks tend
to look for that property.

I think you have hit the point. Our users have _NOT_ grasped that OOo is
different and expect MSO behaviour without bothering to check the
differences. I do know that the people on both the doc project and
OOoAuthors try to compensate for that but there is a limit especially
when these are not even read by those needing the information.

I think that once someone has grasped that language is a property of the text,
it is easy to see how it all fits together.

However, it feels like a different sort of property from fonts and size and bold/italic etc. and so it is difficult to find where to make the changes when they are needed. Fonts can change within a word, but it makes little or no sense to change the language within a word, so looking under character
formatting is counter-intuitive.

I wonder whether it is worth considering adding another entry on the context
menu, on the Format menu and possibly elsewhere that just changes the
language and operates like the font menu entry.

This would simply add a paragraph style with the specified langauge. I think it would be quite easy to do, but again, would people see the use of it when
they only use one language predominantly.

And a second possibility is to move the language identification to the
Organizer tab of the Style definition where it will be seen whenever new
styles are made.

This is just cosmetic - it does not really change the real problem which is that people do not realise that language settings for documents are within
the styles.

Regards
Jonathon

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to