| View previous topic :: View next topic |
| Author |
Message |
TRUETYPIST
General User
Joined: 25 Oct 2006
Posts: 47
|
 Posted: Mon Jun 11, 2007 8:09 am Post subject: [Wish] Finding "manually formatted" paragraphs. |
 |
|
The Styles concept is wonderful. I'm missing one feature:
a) Seeing/looking for "manually formatted paragraphs".
Adobe's Indesign has a info window quite similar to OOo' "Styles and Formatting".
There's a very nice feature: when a paragraph "has suffered" some manual formatting (i.e. changing the font directly on a few words), the style name shows it, with a warning "+" suffix.
Is there any way to achieve this, on OOo Writer ?
I know that I can use the Find funtion to search for styles. I just would like to be able to differentiate the "perfect styled" paragraphs from the manually formatted ones.
Last edited by TRUETYPIST on Mon Jun 11, 2007 10:45 am; edited 2 times in total |
|
| Back to top |
|
 |
Hagar Delest
Super User
Joined: 06 Feb 2006
Posts: 5167
Location: France
|
| Posted: Mon Jun 11, 2007 10:07 am Post subject: |
|
|
Not by default. It has been required IIRC. You should search the OOo Issue Tracker for this.
You can also look here : Reveal Codes macro - feedback required. Never used myself but perhaps it will suit your need.
Thanks to add '[Solved]' in your first post title (edit button) if your issue has been fixed.
_________________
Now on the EN user community forum |
|
| Back to top |
|
|
TRUETYPIST
General User
Joined: 25 Oct 2006
Posts: 47
|
| Posted: Mon Jun 11, 2007 10:43 am Post subject: |
|
|
Thank you for your answer.
Iannz had made a good job (way beyond my capabilities...  ).
He wrote:
| Quote: | | At this stage this is a macro to see what people want and to get some constructive discussion going. It is not yet complete! |
In fact, the macro is still on development phase. As Iannz recognizes, it will probably be too slow for "real use".
On the other hand, it goes too far, for my requirements 
Not much hope: no posts have been made since Wed Aug 30, 2006 11:59 am  |
|
| Back to top |
|
|
Hagar Delest
Super User
Joined: 06 Feb 2006
Posts: 5167
Location: France
|
|
| Back to top |
|
|
TRUETYPIST
General User
Joined: 25 Oct 2006
Posts: 47
|
| Posted: Mon Jun 11, 2007 11:57 am Post subject: |
|
|
Thanks
done
(no milestone for this issue... ) |
|
| Back to top |
|
|
BillP
Super User
Joined: 07 Jan 2006
Posts: 2702
|
| Posted: Mon Jun 11, 2007 12:04 pm Post subject: |
|
|
There is also an enhancement request for "reveal codes" which is not being worked on.
http://wp.openoffice.org/rcodes.html
http://qa.openoffice.org/issues/show_bug.cgi?id=3395
Assuming you are using Windows, if you save your documents in .odt format, you can open the .odt file with an archive manager such as 7-Zip, then double-click the revealed "contents.xml" file to open it. Any directly formatted paragraphs can be found by looking for paragraphs with "paragraph" styles named "P1", P2", etc. Directly formatted characters can be found by looking for text with "text" styles named "T1", "T2", etc. |
|
| Back to top |
|
|
Hagar Delest
Super User
Joined: 06 Feb 2006
Posts: 5167
Location: France
|
| Posted: Mon Jun 11, 2007 12:16 pm Post subject: |
|
|
Thanks, I've added a comment on the last report (53827) that has only 4 votes saying it should be marked as duplicate of the oldest one.
_________________
Now on the EN user community forum |
|
| Back to top |
|
|
TRUETYPIST
General User
Joined: 25 Oct 2006
Posts: 47
|
| Posted: Mon Jun 11, 2007 12:31 pm Post subject: |
|
|
BillP wrote:
| Quote: | | Directly formatted characters can be found by looking for text with "text" styles named "T1", "T2", etc. |
Allways learning...
Although not practical for everyday use, It can be used for special documents that will be used as "templates", and repeatedly used. For this ones, it's worthwhile to look for (and correct) all style "imperfections".
I understand that OOo developers must be targeted on MS Word compatibilization issues, since this is what matters most to 99,9% of OOo users.
Personally, it's a pity that they can't dedicate more time to delevope some of the unique OOo features, that are already much better than MSWord. |
|
| Back to top |
|
|
BillP
Super User
Joined: 07 Jan 2006
Posts: 2702
|
| Posted: Mon Jun 11, 2007 12:44 pm Post subject: |
|
|
| Hagar de l'Est wrote: |
Thanks, I've added a comment on the last report (53827) that has only 4 votes saying it should be marked as duplicate of the oldest one. |
It's not a duplicate. Although either enhancement could be used to help find direct formatting, Issue 53827 justs requests that direct formatting be noted on formatting dialogs for character, paragraph, etc. "Reveal codes" would show both direct formatting and styles formatting inline with the document text, not on the formatting dialog. |
|
| Back to top |
|
|
Hagar Delest
Super User
Joined: 06 Feb 2006
Posts: 5167
Location: France
|
| Posted: Mon Jun 11, 2007 12:49 pm Post subject: |
|
|
Yes, I've seen there are small differences but I think we can merge the 2 in a single feature. I don't think the user really cares about where the information is located. He just needs the feature. I've seen such a pane in MS Word 2k something, it's rather good, giving all the information IIRC.
_________________
Now on the EN user community forum |
|
| Back to top |
|
|
thom314
OOo Enthusiast
Joined: 03 Aug 2005
Posts: 186
Location: Denver, Colorado
|
| Posted: Mon Jun 11, 2007 7:27 pm Post subject: |
|
|
I realize that this isn't what was originally asked for but, for reference, the following macro will clean all manual formatting from a text selection in Writer. Actually, it will not clean manually added numbering or bulleting, but other than that, it seems to be good.
| Code: | Sub cleanManualFormatting
On Error Resume Next
Dim oSelection As Object
Dim aProperty
Dim i As Integer
For i = 0 To ThisComponent.CurrentSelection.Count - 1
oSelection = ThisComponent.CurrentSelection.getByIndex(i)
If oSelection.supportsService( "com.sun.star.text.TextRange" ) Then
For Each aProperty In oSelection.PropertySetInfo.Properties()
oSelection.SetPropertyToDefault( aProperty.Name )
Next aProperty
End If
Next
On Error GoTo 0
End Sub |
p.s. Be careful about text tables. The macro has some issues which I have never bothered to fix. Just select the text within the cells, not the cells themselves or the table.
_________________
- Tom on Linux Mint |
|
| Back to top |
|
|
|
