Hello, This is a longstanding RFE (issue #5991) and one I would like to see implemented. I am prepared to develop the necessary patches, but would like some guidance.
The vcl module already supports the rendering of overlined text (although it is a little buggy), so the main changes required are to provide a means to select this attribute and to support loading and saving this attribute (in the native file format). The obvious way to present this to the user is via a new list box in the Format->Character->Font Effects form that provides the same options as the Underlining list box. This is easy enough to implement (I've already patched the code to do it). The problem comes in adding the infrastructure to attach the new attributes to selected text. Again, the obvious solution is to simply duplicate the code that supports underlined text. However, having started down this route, I soon realised this was going to be a major change to the code base, modifying many class declarations across several modules. A way of significantly reducing the quantity of changes required would be to change the definition of the enumeration type FontUnderline so that it could represent all possible combinations of underline and overline style (i.e. store the underline and overline styles as two separate bit fields within a FontUnderline value). So the question is, which would be more acceptable - a patch that changed many files and classes, or a patch that contains fewer changes, but is a bit of a kludge? A second issue is that currently the ODF schema does not support overlining as a text attribute (although it does support it as a font attribute). What are the chances of getting this added to ODF in a timely manner? I assume the alternative is to define a private schema. Finally, I am currently developing my patches against the 680_m6 (version 2.1.0) snapshot. What tag point should I be using? Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]