NoOp wrote: > > Per the msgs that I sent back to you; 2.0.4 definitely freezes using > that font in the document on a linux system. It does not freeze on 2.0.4 > if the doc saved in MS Word format and then reopened in OOo (again using > the same font). I'll test a bit more & send you results tomorrow but it > certainly appears that OOo 2.0.4 has a problem with that font. > > Note to OOo development folks: the font can be found at: > > http://www.ecko.org.uk/font.html > http://www.ecko.org.uk/o-font.ttf
Well, here is something interesting. I rebooted to Windows 2000 Professional and: I installed the Orienteering font from the UK site (http://www.ecko.org.uk/font.html) and in Microsoft Word 97: - Loaded the rtf file from the site (http://www.ecko.org.uk/font_instructions.rtf) and in Word the fonts/symbols display correctly. - Saved the rtf file to an MS Word doc from MS Word and again the fonts/symbols display correctly in Word. Also if I open the font to insert a symbol, all of the symbols display correctly and I can sucessfully insert a proper orienteering symbol. I then try in OOo 2.0.3 (Windows): - Opened the rtf and the MS Word doc in OOo 2.0.3 (Windows) and the fonts do not display correctly. If I open the Orienteering font for instertion as a special character I show all squares. This behaviour is the same that you had experienced in your thread "Question on a custom symbol font" [1] - Just to be sure that the font sticks in Windows and is not working with OOo 2.0.3 (Windows) I reboot back into Win2KP and try again. Again the font does not work in OOo 2.0.3 (Windows) using the rtf document. Note: I am using the rtf document as a base so as to not get anything confused with your document and or anything that OOo may save in the process. Now here is where it gets interesting... - When I open the saved MS Word doc (the one that was created in MS Word from the rtf doc) in OOo 2.0.3 the fonts/symbols in the document appear correct with the exception of Dec characters 33 - 44 and 48 (Hex 0x21 - 0x2E and 0x30). However, if I attempt to insert one of the symbols (Insert|Special Character|Orienteering) the fonts do not display properly in the selection box, nor do they insert properly. The only symbol that inserts properly is Dec 253/Hex 0FD (SW edge). - If I save the MS Word doc (again using the one converted in MS Word from the rtf) as a odt file using OOo 2.0.3 (Windows) and reopen, in OOo I get the same results as above. The symbols with the exceptions mentioned above are shown properly, and the insert Orienteering font does not work. Testing on OOo (linux) 2.0.4: - As above the Orienteering font from the UK site is installed. This time on 2 separate systems: 1 Ubuntu 6.10 (Edgy) and 2 Ubuntu 6.061 (Dapper) [2]. System #1: - Open OOo 2.0.4 Writer with a blank document. Insert orienteering symbols from Insert|Special Character|Orienteering - all characters display correctly and I can insert the fonts/symbols into the blank document. - Download clean rtf file from http://www.ecko.org.uk/font_instructions.rtf and open in OOo 2.0.4. The fonts no not display correctly. However, when I attempt to insert one of the symbols into this document again the Orienteering symbols appear correct via Insert|Special Character|Orienteering and I can insert a proper orientieering symbol into the document. - Next I open (in OOo 2.0.4 linux) the MS Word document that I'd made from the rtf in the OOo 2.0.3 windows test. Exact same results as above with the rtf file. System #1: Exact same results a those on System #1. Other word processors - AbiWord: I tested the rtf document in AbiWord 2.4.4 (linux) and the document opens and displays properly. I can also display an insert all symbols from the font into the document without any problem whatsoever. Conclusion: OOo 2.0.3 (windows) and 2.0.4 (linux) does not properly handle the Orienteering (ttf) font found on http://www.ecko.org.uk/font.html. MS Word (97) handles the font without any problems whatsoever. OOo 2.0.3 in Windows does not display or allow proper insertion of the orienteering symbols. If the symbols have been used in a saved MS Word (97) document, OOo 2.0.3 will open and display most of the symbols in the document only but does not interpret the font any further for insertion of new symbols. OOo 2.0.4 in Linux does allow proper insertion of the characters, but does not recognize the characters if they have previously been used in a rtf or MS Word document. Given that this ttf font is used extensively and internationally by folks in the Orienteering crowd (of which I am not one... I'm too lazy & not interested :-), and in that it works just fine in MS Word, I recommend that Richard and/or someone that uses this font file a bug report with OOo. I would _not_ recommend modifying the font to work with OOo (no matter how well meaning as then offset fonts get passed on to OOo orienteering users) and instead fix OOo to handle the font properly. I also note that this does not address Richards issue with the freezes in in 2.0.4 vs 2.0.2. However he is now using Ross Johnsons modified font in his document (see [3]) and that seems to work as a temporary workaround. [1] I've tested Ross Johnson's font modifications and had mixed results so I've eliminated that font from both the linux and windows systems for testing. I thinks it best to stick to a single font that is known to work with Windows & MS Word than to introduce a modified font for testing. (see [3] below). [2] Tested on 2 systems because the Ubuntu 6.10 (Edgy) and OOo 2.0.4 on that system are fresh installs. Therefore, system #1 has only basic fonts installed and there should be no conflict after installing the Orienteering font. System #2 (Dapper) has hundreds of fonts installed and the OOo 2.0.4 on that system has been used considerably w/various templates, docs, fonts etc., so I thought it wise to test on both. Also the OOo 2.0.4 on the Dapper system is installed directly from the OOo website files whereby the OOo 2.0.4 is from the Ubuntu Edgy repository files. Added personal note: the Edgy system & OOo runs considerably slower than the Dapper system that it replaced so I'd not recommend going to Edgy for awhile just yet. [3] Special thanks to OOo'er Ross Johnson who took the time to modify the font for Richards use so that he could get his newsletter out. Not including Ross's font in the testing and recommending that OOo fix OOo to work with the UK Orienteering font isn't intended to judge Ross's kind work. Instead I simply think that OOo should be fixed to accomodate the widely used font that seems to be the standard in the Orienteering community. Gary Lee glgxg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
