F
Fudzy
Guest
Looks like Open Office can do the tracking, review and commenting:
http://wiki.openoffice.org/wiki/Documentation/OOo3_User_Guides/Writer_Guide/Tracking_changes
So it opens up a new window to show comment?
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Looks like Open Office can do the tracking, review and commenting:
http://wiki.openoffice.org/wiki/Documentation/OOo3_User_Guides/Writer_Guide/Tracking_changes
So it opens up a new window to show comment?
Not sure that's exactly what they mean but they also link to
http://wiki.openoffice.org/wiki/Documentation/OOo3_User_Guides/Writer_Guide/Inserting_notes
Which looks (at first glance very similar to comments in Word.)
I'll have a play with it in Open Office when I have chance and see how it actually works.
Office 2013 also allows it now, IINM it wasn't until they opened the PDF spec that either apps could do it without paying royalties to Adobe.
Please notice: Use this extension cautiously as editing PDF files is not a trivial task. Encouraged by the huge number of positive comments and the improved quality of this extension, we decided to remove the Beta tag from this release. Of course we will continue to work on this extension to reflect user needs and any changes to the PDF standard. To further improve this extension, please continue sending us feedback at [email protected].
Interesting. I haven't tried 2013 yet and I wasn't aware of that feature. Not sure how long ago Adobe opened up the PDF spec off the top of my head but the OpenOffice PDF import was originally relesed before Oracle took over Sun (Beta when I first saw it I think.)
Current link to the OO extension is :http://extensions.services.openoffice.org/project/pdfimport
Take note of the caveat at the bottom:
Having tried to edit a number of pdf documents in the past, I think that's a fairly reasonable comment. It will be interesting to see how MS 2013 handles it.
OpenOffice needs someone like Google to take them over, they understand UE a lot better than Microsoft IMO (seeing how they're scrambling for second place online)
The other problem OpenOffice faces are the cramsession fed MS certification junkies that flood the IT sector.
I can add a simple example that put me off open office and back on (pirated) MS Office: Locale settings. In MS Office, the locale settings (in this case, the number format settings specifically) are taken from the Windows locale settings, which are customisable. Open office has it's own list of standards for each locale.
So, being who I am, I [-]want[/-] demand that my currency decimal be a comma and my currency symbol to be one space away from my first digit (R 50 392,35), my normal decimal be a point and my thousands separator be a space (50 392.35). I have several JSE Top 40 financial statements proving that this is the de facto and industry standard way of presenting data. Can I do this in open office? NOooooo. Open office knows best! South Africa locale settings are set in stone based on god knows what reference (maybe a 1977 government gazette or something) and there's no way to fix them.
And that actually gives away the attitude of the developers. "Take it or leave it.", "You're getting it for free, so shut up and like it, or **** off." And like InvisibleJim said, the code may be open source, but modifying it is definitely not for amateurs. So back to MS I went.
That's a little bit of a surpise as open source applications generally aim for a good level of internationalisation.
Ref number formats, I'm a Pommie and where I come from, a comma is always a thousand separator (if you use a thousand separator at all) and a decimal separator is always a decimal point. Until I moved here, I was unaware that a comma was used as a decimal separator in South Africa. I think France and some other countries may have traditionally used a comma as a decimal separator but I don't know if that you could consider it de facto standard worldwide. I can see how non South African Developers could easily get that wrong,
Does open office not give you the capability to easily create custom formats though the same as MS Office does? I'll have to check but I think they both work in a very similar way with no coding required (apologies if I've missed something with your post.)
Do you use Windows or Linux? What I think he's saying is in the Windows regional settings you can create a custom format which MS products adopt.
That's a little bit of a surpise as open source applications generally aim for a good level of internationalisation.
Ref number formats, I'm a Pommie and where I come from, a comma is always a thousand separator (if you use a thousand separator at all) and a decimal separator is always a decimal point. Until I moved here, I was unaware that a comma was used as a decimal separator in South Africa. I think France and some other countries may have traditionally used a comma as a decimal separator but I don't know if that you could consider it de facto standard worldwide. I can see how non South African Developers could easily get that wrong,
Does open office not give you the capability to easily create custom formats though the same as MS Office does? I'll have to check but I think they both work in a very similar way with no coding required (apologies if I've missed something with your post.)
The problem with the point and the comma as either decimal mark or digit group separator is that, internationally, they have both often been used for both meanings, and their meaning is context-dependent (one must know which notational system is being used in order to interpret them). Therefore the space is recommended in the SI/ISO 31-0 standard,[12] and the International Bureau of Weights and Measures states that "for numbers with many digits the digits may be divided into groups of three by a thin space, in order to facilitate reading. Neither dots nor commas are inserted in the spaces between groups of three".[13] Other style-defining bodies are also moving toward this clearer notation. For example, the International Union of Pure and Applied Chemistry (IUPAC) suggest never using a comma or a point as thousands separator: "For numbers with many digits, the digits may be separated in groups of three, counting from the decimal sign toward the left and the right. The groups should be separated by a thin space (half space), and never by a comma or a point, or by any other means."[14] The American Medical Association, whose AMA Manual of Style is widely followed in health professions literature, also endorses a space for the digit group separator.[11] (Specifically, a thin space is endorsed for typesetting; a regular word space is sufficient wherever typographical nicety is impractical.) The United Kingdom Metrication Board also proposed this system for Metrication in the United Kingdom and, while not universally adopted, it is the standard in the UK construction industry.
Pet peeve: When inserting an image into OpenOffice (and there can be a lot for a technical report), the software seems to put the image wherever it wants. Then comes all the editing of image handles to get things where they were meant to be in the first place. The extra time taken on just one report more than pays for a copy of MS Word.
This. Wife designs flyers etc for her creche using OO, and it's not easy getting things to go where you want them. Also, compatibility is broken with these sort of documents between OpenOffice and LibreOffice. Busy looking at alternatives (free) to use in this regard.
On the other hand, if you can't afford M$ Office, then it might be worthwhile to use Open/Libre Office.
I prefer Libre office to OO. Sure MS office can do VBA stuff but in all honesty how many users actually require that?
Busy looking at alternatives (free) to use in this regard.