John Moran

(FWIW) http://www.microsoft.com/technet/prodtechn...e/o03flshr.mspx

http://www.microsoft.com/technet/prodtechn...e/o03flshr.mspx (FWIW)

Dick- Open Office Writer may be more dependent on "Styles" than MSWord. You and your Linux OOo Writer guru may want to have a look at OOo Frame Styles by using the F11 Key, and then clicking on the top middle "page" icon, which is Frame Styles. It may be that TMG Journal Report exports of Word doc files (in recent builds 8 or 10) make some use of Styles directly, but I doubt it. I continue to look in (uncompressed, unencrypted) TMG RTF file exports for answers to questions you pose. But the answers are not to be found there - just more questions due to coding errors, or use of obsolete RTF specs by the 3rd party Wordport converter. This coding causes Footnote Style errors in OOo, in particular. ____________________________________________ If you do a Search for the string, "style", in the current MS RTF spec, you will find it. If you do a Search for the string, "style", in a Journal Report file exported from MSWord 2002 in RTF format, you will find it. But if you do a Search for the string, "style" in a Journal Report exported directly from TMG, you will not find the word, "style" _____________________________________________ To put things in perspective, go to Google and do a search for "Wordstar History" and read the first entry. Takes you back to the seventies and eighties. (Note: WordStar and Sun StarOffice, from which Open Office Writer is derived, are apparently two different animals.) John

Dick- I found this posting about Open Office Writer picture sizing on an unrelated site. It may not be on target, but you might run it by your Open Office and TMG Gurus. John http://www.nabble.com/RTF:-Size-of-images-...t--t728421.html

As a followup to other threads, I became interested in the concept of storing Exhibit Captions and Keywords within original image files - in addition to within TMG Exhibit Albums. Experimentation with a few Photo Editors, including current versions of ACDSee (trial), MS PictureIt!, Win XP Explorer, Irfanview, Adobe "Starter Album" (trial) and my ancient version of PhotoImpact 6 gave indications that there was no real standard for data field inclusion in Jpgs. Yes, I had read of Adobe Photoshop and CS Suite metadata inputs on Photography forums, but I did not have those Apps to experiment with. Even then, I had read of changes in field locations with nearly every version of "big" Adobe Photoshop. It did not appear that many users of Photoshop Elements even bothered with this feature, if it existed in that app. Yesterday I ran across an application called Pixvue. It is not a photo editor, although it will rotate jpgs. It is instead an imbellishment of Windows 98, 2000, and XP Explorer that permits adding metadata to jpogs and other image files in accordance with the latest XMP spec promulgated by Adobe. My experiments have been minimal, but it looks like a winner. http://www.usatoday.com/tech/columnist/and...-metadata_x.htm http://www.pixvue.com/ John

Dick- My observation has been that Open Office Writer saves RTF files in a much more complicated format than the basic RTF output of TMG or UFT, even if the file is only opened and closed in Writer without modification. Perhaps you can inspect the differences in a short sample RTF file before and after being opened in Writer to correct the graphic sizing problem. This may give a hint not only as to how TMG might handle the coding, but also give a hint as to a simple "Find and Replace" operation on the original RTF file when opened as Text and resaved. John

Toni- If no experienced TMG users suggest a feature of TMG that will do this internally within 24 hours, I will post a suggestion that you export a Journal Report in doc or RTF format and do the search in your 3rd party Text Editor, such as MSWord, Open Office, or WordPerfect. Good luck, John

. . . . . or is it possible that your jpg file associations are incorrect in Windows Explorer because you have not reinstalled your Photo Editor App? . . . . . .or that TMG's internal photo search is looking for a particular Photo Editor as host server, and it is missing? Don't know how that is implemented on TMG, but . . . .

Diana- Is it possible that you reinstalled an older version of TMG to kick things off, and that the version you used does not recognize the file format of certain images? Is it possible that you have edited certain images in a new Photo Editor application, or that you accidentally saved some of them them in a format of jpg that TMG does not recognize? Good luck, John

Have you gone online to Symantec to check for updates? http://www.symantec.com/avcenter/security/...2005.03.28.html

Why use RTF for TMG Report generation? The current RTF specification has more than enough bells and whistles for most reports from a typical genealogy program, and cannot be retracted, unless MS claims some sort of patent infringement. It's out there. It is understandable to the typical TMG user. The major Word Processor applications support it. Whether they support it correctly and fully is another matter. Rich Text Format, although proprietary to Microsoft, is "open" in the sense that the the current specification is freely downloadable and the file structure is not compressed. This means that any experienced user of TMG can review exported Report files as TXT and discover whether unexpected behavior of the reports, when opened in MSWord or other similar applications, is a bug or a feature. File size is not much of an issue, as far as storage space goes these days. Decryption and decompression is not an issue. This is not true of Report exports in MS *.doc or most other proprietary formats. TMG developers are no doubt currently at work on creating report exports in some form of open document format, perhaps XML based. If the chosen format is uncompressed and, life could be simpler for TMG users. John M.

To John R. From John M. No, I had apparently screwed things up royally in Ram and who knows what else. It took at least three cold reboots to get back to "normal". Perhaps the virus checker was trying to protect the computer from scripting macros, but I saw no such indication. The $20 USB 2.0 multi format flash memory card controller may have been in play originally..

Gentlemen- I got up this morning with the intention of commenting on this thread. Dick beat me to it. I will suggest that the problems exposed by OpenOffice.org Writer are not necessarily indicative of errors in Writer. It may well be that TMG has some repetitve styling errors in its doc and rtf file conversions that may/may not be designed to cover up complementary errors in MSWord. In any event if TMG would concentrate on getting the rtf export correct, and if the power users such as Dick would use only rtf exports for their tests, perhaps the "problems" would be solved rather quickly. That TMG needs another internal Text Editor that can at least support Right-to-left scripting of certain middle eastern languages was also a matter of record - at least until the board was wiped clean three months back. A recent reply by Virginia on another thread gave a link to a historical event that should no longer be in play. It seems that the release of TMG 1.2 was delayed because Commsoft had apparently thought it had patented the process of creating and indexing footnotes in 1989. Perhaps the computing world is past that issue. Seems like, after much consternation, I purchased Word 2.0 instead of Wordperfect for my college age son circa 1991. An hour later he showed up to say he had dropped out of school for a semester. And so it goes. But back to 2006, perhaps if TMG would concentrate on rtf, and perhaps an open document xml format of file exports for the future, the overall workload TMG programmer workload could be simplified and the errors could be minimized. Wordperfect users would just have to limp along with existing TMG 6.x versions. Oh, by the way, it is possible to change footnote font styles back and forth from text body default in OOo writer, to correct errors form TMG exports. But, like the image sizing problem, it apparently cannot be done globally in OOo at this point. John

Robin- Buried in rather lengthy forum thread in which I recently participated, I posted the following impressions MSWord and OpenOffice regarding image linking. http://www.whollygenes.com/forums201/index...?showtopic=4744 (quote) Dick- Well, it is possible to crash both MSWord 2002 and OpenOffice Writer 2.0 with these experiments. Word does seem to get a little flakier - flakier perhaps than OOo - when exhibit linking to original source paths is exported from TMG. Word seems to default to clipping images with large pixel counts at the paper width, minus margin settings (8.5in -0.5 in -0.5 in = 7.5 in. in width). Word maintains the picture aspect ratio. OOo Writer seems to default to square images of approximately 1.58 inch square size and does not initially display the correct aspect ratio unless the original was square. OOo expands thumbnails and shrinks large pixel count images to obtain this default 1.58 in. square size. If OOo is in control of the file, and not in "read only" mode because the file is also open in Word, a couple of mouse clicks on EACH and EVERY individual image will fix the aspect ratio, and perhaps the size. I found no global override yet. And, yes, Dick I did experiment with breaking paths by renaming folders containing "some" of the source graphics files. Results were predictably unpredictable. i.e. Maybe you get a link in Word right off the bat; maybe you don't. Doesn't matter if the link is broken or not if you select "footnote" export, it seems flaky. It became apparent that TMG may try to save your bacon by maintaining a thumbnail image of the former external link until thumbnails are regenerated. This could cause a little confusion, however well meaning the procedure - but TMG does warn immediately that external exhibit links are broken. In my limited experiments, it seemed that TMG was exporting more or less as advertised. However, at this point, I would be reluctant to blame either TMG or OOo Writer for linking experiments that do not go exactly as as perceived in MS Word on the Win XP platform. Over and out, John (unqote) I would also suggest the following caveat, or warning. If any image linking tests are performed on any Text Editor apps, including OOoWriter and MS Word, be sure to have only one application open at a time and close down all applications between tests. John

Robin- Ooo is freely available for download. It speaks for itself. Sun stock was up substantially at noon today in the USA. Regards. John

The only Journal Report tests I have ever made in TMG were with Projects based on the Sample "as is" as far as Sources, Citations, and Memo coding goes. I occasionally experiment with language character sets other than English/Latin code page 1252 in memo fields or name fields, but I don't think that would have any effect here. John

Jim- In further testing I cannot duplicate the restore operation to the 256mb Lexar Compact Flash Card, nor to a 1.0mb SanDisk UltraII Compact Flash card as Drive F. But the project data files from the initial "mousing" experiment definitely exist on the F drive, and I did not deliberately copy it from the C drive. The card reader again appears to be operating correctly with either flash memory card, but this means I cannot again trick TMG into restoring files to it. John

Gentlemen- I decided to try a warm reboot with the Lexar 256mb "standard speed" Compact Flash media containing the TMG data and a few Canon jpg images still plugged into a CompUSA 9-in-1 $20 card reader. I got an error meesage concerning the card reader application on shutdown, and the Computer never got past the MB bios memory check on reboot. It may be a little premature to jump to any conclusions about TMG workability if we all have similar setups. The external card readers may be somewhat suspect and erratic in operation with databases, but can apparently be "tricked" into working with variations in mousing around in the restore operation. John

Dick- There are no rules in mousing around! I have previously suggested that beta testers set up a video camera to record keyboard and mouse actions, . . . but I am not a beta tester. . . and I don't remember exactly. John

And then there is the default square size used by OpenOffice.org Writer.

Dick- I am assuming you are on the XP operating system, and not Linux this time??<g> My computer showed the same message, "Wrong Destination Path", on an initial attempt to restore a sqz file from a backup on the root of "Flash Drive F" to a newly created folder on Flash Drive F. But after a little mousing around with the back and next buttons, as well as changing the path in Preferences, it did restore the Sample file to the flash media folder on drive F. I did not have a convenient way to try the letter H, which would be a different memory type with my 9 in 1 USB adapter. As a further test, when opening TMG with the flash media disconnected, TMG properly greyed out the Last File option for startup. John

Michael- That's way too much for my attention span, but in experimenting with Journal Reports exported in *.RTF format, it appeared that footnote erors in the Sample project could be triggered by a change in citation Style. That is, citations of a style that contained italics - including the Bible one -could trigger errors in OpenOffice.org Writer footnote fonts, while non-italicized text in citations caused no obvious errors. When the same Sample Journal file was opened in MSWord from from *.RTF report export, it appeared that all footnotes might be superscripted. I assumed this to be an error. Do you also see superscripted footnote numbers in Word? John

On Win XP Desktop Right Click on Start button Left click on Explore> Tools>Folder Options>File Types Scroll down to Doc File Type Left click on "Change" Select Microsoft Word Or reinstall MSWord 2003 last to have doc files and other necessary file types associated with MSWord instead of Works In TMG Report Definition Screen(s) Select MSWord 2000

TMG Journal footnote/endnote font sizing errors (RTF export only) exposed in tests of OpenOffice.org writer are apparent in MSWord 2002 also. It may be that TMG RTF coding exported in Journal Reports is designed to be backward compatible with a maximum number of older text editors, but the coding appears to be inconsistent with the Microsoft Word 2003 RTF spec and gives errors in both Word 2002 and OpenOffice.org 2.0 Journal Reports in those applications. Specifically, in Word, footnote numbers may be incorrectly superscripted in default 12 point font, rather than the specified non-superscripted font, which is typically 8 point. In OpenOffice.org writer, footnote errors seem apparent only in footnote numbers for citations containing italics. For those citations, the font size for footnote numbers jumps from specified 8 point font to the default 12 point "fallback" font for RTF commands not understood. Or so it seems from this end of the tunnel. There seemed to be a "quick fix" find and replace substitution of italic coding in the RTF file, but that only showed different errors in Bold. It is not a deal breaker for either Word or Open Office, but it makes Open Office, which is the new kid on the block appear in error, when it fact it may be working exactly in accordance with the 2003 spec, and that OOo errors are just more obvious. Note: In previous tests, similar errors were noted in discontinued UFT RTF exports. John

Be sure to print (either to paper or to pdf files) some sample Journal reports containing headers, footers and endnotes, to see what is missing in Works text editor. Not certain about the "embedded" picture links to Works in Rich Text Format (RTF) or *.doc files from TMG. Otherwise, you might not know what you are missing. <g>