[framework-issues] [Issue 115563] "Special Characters" dial og, zoom character on mouse over
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=115563 --- Additional comments from j...@openoffice.org Sat Nov 13 22:15:10 + 2010 --- Created an attachment (id=74725) suggestion for displaying character name (per Unicode) - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[framework-issues] [Issue 115563] "Special Characters" dial og, zoom character on mouse over
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=115563 --- Additional comments from j...@openoffice.org Sat Nov 13 22:14:09 + 2010 --- Thank you, regina, I wasn't aware of the meta issue. I can't find my request for showing the character *name* on there, however. To be clear about it, I'm attaching a quick mock up image of the dialog. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[framework-issues] [Issue 115563] Usability tweaks to "Spec ial Characters" dialog
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=115563 Issue #|115563 Summary|Usability tweaks to "Special Characters" dialog Component|framework Version|1.0.0 Platform|All URL| OS/Version|All Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|ENHANCEMENT Priority|P3 Subcomponent|ui Assigned to|tm Reported by|jurf --- Additional comments from j...@openoffice.org Sat Nov 13 17:34:05 + 2010 --- Feature request: tweaks to "Special Characters" dialog This issue requests three minor changes to the "Insert | Special Characters" dialog, all intended to improve usability. Should these requests be programatically distinct, feel free to split the issue. 1. At present, when a character is selected, the dialog shows a zoomed view of the character, and its Unicode value. The request is for the character's Unicode name to be shown as well (eg "LATIN SMALL S WITH DOT BELOW"), as per Unicode's scheme (see http://unicode.org/Public/UCA/5.2.0/allkeys.txt - a more recent version may exist). The enchancement removes confusion between visually similar but semantically very different characters, which can be indistinguishable depending on font design, hinting, and/or screen resolution. For example, can you tell the difference between these: ᾽ ᾿ ’ ʼ ̓ ̕ ? (if this looks corrupt, your font lacks some of the characters) 2. At present, the zoomed character view and Unicode value are only shown when a glyph is actually selected (and thus added to the selection string). The information would be more usefully displayed before character selection, meaning on mousing over. 3. At present, the dialog's Delete button clears the entire selection string; kinder would be for it to clear only the last character added. If implemented, "Undo" might be a better button label. Many thanks - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 113587] Change case - Sentence ca se does not work correctly with mix languages text
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113587 --- Additional comments from j...@openoffice.org Fri Aug 20 07:28:35 + 2010 --- Thanks, tl, for the fix and also the one for issue 113584. I look forward to pawing my grubby mitts over whichever release gets the CWS first. :-) - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 113584] Crash formatting as "Capi talize Every Word" text with ligatures or simi lar characters
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113584 --- Additional comments from j...@openoffice.org Sat Aug 14 01:31:53 + 2010 --- -> tl OS is XP sp2 (Portuguese), heavily tweaked and streamlined (eg just 12 services run on start up). Uniscribe (usp10.dll) version as used by OOo is 1.626.6000.16386. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 113584] Crash formatting as "Capi talize Every Word" text with ligatures
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113584 --- Additional comments from j...@openoffice.org Thu Aug 12 21:45:20 + 2010 --- Those ligatures are really getting us in a bind! I suggest changing the summary to "Change Case mangles output due to miscounted ligature length", or something like it - the *crash* originally reported by es appears to have vanished in OOO330m2. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 113584] Crash formatting as "Capi talize Every Word" text with ligatures
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113584 --- Additional comments from j...@openoffice.org Wed Aug 11 12:09:47 + 2010 --- The list of ligs reminds me: a problem with Sentence case and so presumably also with Capitalize Every Word, albeit currently masked by the bug described in this issue, is that all the letters in a ligature at the start of a sentence for Sentence case (so presumably at the start of any word for Capitalize Every Word) are converted to all caps, not just the first letter. eg: find -> FInd fluke -> FLuke ſtop -> STop stop -> STop (same with ff, ffi and ffl, but those sequences don’t appear at the start of any words in English). - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 113587] Change case - Sentence ca se does not work correctly with mix languages text
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113587 --- Additional comments from j...@openoffice.org Wed Aug 11 12:07:39 + 2010 --- The list of ligs reminds me: another problem with Sentence case is that all the letters in a ligature at the start of a sentence are converted to all caps, not just the first letter. eg: find -> FInd fluke -> FLuke ſtop -> STop stop -> STop (same with ff, ffi and ffl, but those sequences don’t appear at the start of any words in English) I’ve copied this comment to issue 113584 (Capitalize Every Words), as it may be related. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 113584] Crash formatting as "Capi talize Every Word" text with ligatures
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113584 User jurf changed the following: What|Old value |New value CC|'sba' |'jurf,sba' --- Additional comments from j...@openoffice.org Tue Aug 10 18:19:15 + 2010 --- To elaborate on my example: The flickering projector On my system, selecting entire sentence, then Capitalize Every Word, results in entire sentence disappearing. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 113584] Crash formatting as "Capi talize Every Word" text with ligatures
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113584 --- Additional comments from j...@openoffice.org Tue Aug 10 18:16:23 + 2010 --- Problem still there on my DEV300_m86 (test case as I posted on Aug 4 - copy and paste my example - the 'fl' is a ligature). Text disappears or is mangled by Capitalize Every Word. It's not a clean install but on top of OOO330m2. OS-related? (I'm running XP sp2) A long shot, but perhaps related to Graphite? (though the bug shows up with any font, Graphite or not). ??? - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 113587] Change case - Sentence ca se does not work correctly with mix languages text
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113587 --- Additional comments from j...@openoffice.org Tue Aug 10 17:13:17 + 2010 --- tl, thanks for your post. You ask two questions: BEHAVIOUR OF SENTENCE CASE After writing a first draft for this reply, it occurred to me that, logically, there's actually no reason to offer anything more complicated than capitalizing the first word of the sentence, with everything else lowercase. Two reasons: 1. Assuming that the main usage of Sentence case is to quickly correct blocks of text in all-caps or in all lower-case, guessing the casing of proper nouns, acronyms etc would be a cpu-heavy waste of resources, and pointless if the words aren't in a dictionary. In other words, the user would likely have to correct stuff manually anyway. 2. If the original text is mixed case (where some words are and should remain capitalized, like proper nouns and acronyms), it's unlikely a user would want or need to apply Sentence case, as the casing should, in theory, already be correct! In other words, and conversely, you're unlikely to come across a block of text whose sentences start with lowercase but which contain words that have and should have caps. Conclusion: keep it simple by just capitalizing the first letter of each sentence. ** SELECTION SCOPE I'd expect the selection(s) to (temporarily) expand to cover the entire sentence. This is what I've implemented in a case toggling macro that applies my own casing code: when it gets around to sentence case, it temporarily expands the selections to entire sentences, before restoring the original selections. As I'm not up to speed with textcursors and the like, I use temporary bookmarks to mark the original selections (RegExp would have been easier, but kills character formatting). The advantage of selection expansion is apparent when applying a casing routine to multiple selections. Instead of having to carefully select each sentence in its entirety (and risk accidentally clearing all selections by misclicking and having to start again), I can scoot through a document CTRL-clicking any bits of those sentences, before firing off the macro. Thanks again - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 113584] Crash formatting as "Capi talize Every Word" text with ligatures
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113584 --- Additional comments from j...@openoffice.org Wed Aug 4 23:42:14 + 2010 --- No crash in OOO330m2, but test string (in odt attachment) disappears completely. Bug appears to be caused by miscounting character length(s) of ligatures. e.g.: The flickering projector - select "flickering" - apply Capitalize Every Word Output is "The projector" (two spaces, no flickering; the selection now covers " pro") The miscounting is corrupting text buffers or whatever the OOo equivalent is, as shown when if apply "Undo" after the above: Output is "The flickeringr" Have fun... - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 113558] Change Case broken by lan guage tags and/or ligatures
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113558 --- Additional comments from j...@openoffice.org Tue Aug 3 01:32:42 + 2010 --- Thanks for splitting this. FYI, the dictionary bug was solved in CWS tl81, integrated in OOO330m2. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[framework-issues] [Issue 113568] Silent corruption of user dictionaries
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113568 --- Additional comments from j...@openoffice.org Sun Aug 1 19:45:09 + 2010 --- Thank you majukr05 for the heads up - OOO330_m2 works for me as regards the dictionaries, though the casing bugs (issue 113558) are still present - evidently unrelated. Closing this issue as a dupe. Thanks again - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[framework-issues] [Issue 113568] Silent corruption of user dictionaries
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113568 Issue #|113568 Summary|Silent corruption of user dictionaries Component|framework Version|DEV300m84 Platform|PC URL| OS/Version|All Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|tm Reported by|jurf --- Additional comments from j...@openoffice.org Sun Aug 1 07:43:05 + 2010 --- OOo-dev330m85 and probably OOO330m2 may corrupt .dic user dictionaries when user adds words. Buggy behaviour is not present in 3.2.1, hence regression. DESCRIPTION When adding words to a user dictionary (right-click menu), one of four things may happen: 1. word is added normally, speller behaves as expected; 2. word is added to *another* user dictionary (not the one selected, and not necessarily active); 3. only part of the word is added, appended at the end of the .dic (tested on UTF8-versioned dic files); 4. word is not added at all, but part of the last word in a .dic (not necessarily the one selected) is repeated as the new last entry. The buggy behaviour was first noticed on an updated install (using settings, including user dictionaries, created in older versions of OOo), but also occurred on a clean installation with default user settings. In that case, words I'd supposedly added to standard.dic were actually added to the ignore list. Having seen similar bugs in a variety of programs (garbage appearing at the end of incorrectly processed files, paragraphs or text selections, or even in other non-selected paragraphs or files), I'd guess the problem is caused by a text/bound parser that isn't counting straight when it encounters anything other than single-byte characters, which in turn causes miscalculated insert positions and data corruption while sorting fields etc. I'm quite confident about this guess as the same build I was testing (OOo-dev330m85) also has data-corrupting flaws in its new text-casing options, which also relies on calculating text bounds - see Issue 113558. For the user dictionary routine, I noticed the problem surfaced when multi-byte characters (such as a letter with unusual accents, for which there are no precomposed versions in Unicode) were present, either in the word being added, or - fatally - already included in a user dictionary (not necessarily the one selected to receive the word). I'm afraid I got fed up with M85 and reverted to 3.2.1 before completing testing. As such, I'm only guessing that the bug might also be triggered by the presence of ligatures, or by trailing periods (OOo's spell-checker normally ignores trailing periods, such that "A.D." is entered as "A.D", but this appears to have buggy for a while), or indeed by anything else that might trip up a mathematically-challenged parser. If you need a quick and dirty test word, copy/paste aaaṣbbb (I know, not a word, but it will at least appear at the top of your word lists to save you a scroll - the s has a dot underneath, by the way). - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[framework-issues] [Issue 113558] Change Case broken by lan guage tags and/or ligatures
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113558 --- Additional comments from j...@openoffice.org Sun Aug 1 04:25:39 + 2010 --- One more comment... After posting this report yesterday, I starting playing with the new user dictionary interface in M85 (the default for new user dictionary files has changed from binary to UTF-8). There are bugs there, too, which may possibly be related to the casing errors. So, please don't treat the following as a separate bug report (it's in the wrong place for that, I know), but instead as a clue to the possible cause of the casing errors. In short, when I add a word to a user dictionary that contains a double-byte character (eg a letter combined with an unusual accent, such as dot underneath), or if the user dictionary already contains such words, things start getting buggy: in some cases, an *incomplete* copy of the last word in the list gets appended to the dictionary; in other cases, the word is not added to the selected dictionary at all, but to another one. Again, I'm not a programmer, but if I were to bet on it, I'd guess there's a possibility that both sets of errors are caused by a bug in a text parsing library used by both the casing and user dictionary routines. Reason for saying this is that all the errors - casing and dictionary - appear to involve miscalculating text bounds. The parallel is particularly compelling when comparing Capitalize Every Word's mangling of text with ligatures (which could be counted as one, two or more characters), to the dictionary parser's mangling of user dictionaries that contain non-compiled characters with combining accents (which could also be counted as one, two or more characters). Has something recently changed in a text parsing component? - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[framework-issues] [Issue 113558] Change Case broken by lan guage tags and/or ligatures
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113558 --- Additional comments from j...@openoffice.org Sat Jul 31 05:35:39 + 2010 --- My apologies, I merged two examples into one in my post. It should have one of these examples: 1. SENTENCE CASE Input: the rapide brown fox [with 'rapide' marked as French] Output: The Rapide Brown fox Underlying code: The Rapide Brown fox 2. Capitalize Every Word Input: the rapide brown fox-like creature [with 'rapide' marked as French] Output: The Rapide BroWn Fox-Like Creature [with everything from 'Rapide' to 'Creat' inclusive marked French] Underlying code: The Rapide BroWn Fox-Like Creature - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 1601] Provide change case for: To ggle case, First Letter Capitalized and Senten ce case
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=1601 --- Additional comments from j...@openoffice.org Sat Jul 31 05:22:18 + 2010 --- Many thanks, first of all, for having got this done - it's much appreciated. Alas, in my testing (DEV300m85) the new "Sentence case" and "Capitalize Every Word" functions are, unless dealing with plain .txt-style text, potentially destructive - almost certainly if the document contains ligatures, quite likely if the selected text contains language mark-up, and possibly (depending on the other two factor) if the new functions are being applied to multiple selections. The bugs may also be triggered by other kinds of formatting and situations I haven't tested for. I've opened a new issue for this (http://www.openoffice.org/issues/show_bug.cgi?id=113558), with priority P2 and a suggestion that it be added to the showstoppers for 3.3. There's a host of test cases and examples attached as an ODT. Whilst I've got a rough idea of what might be wrong, I'm not a programmer, so would appreciate more knowledgeable feedback. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[framework-issues] [Issue 113558] Change Case broken by lan guage tags and/or ligatures
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113558 Issue #|113558 Summary|Change Case broken by language tags and/or ligatures Component|framework Version|OOO330m1 Platform|PC URL| OS/Version|Windows, all Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P2 Subcomponent|code Assigned to|tm Reported by|jurf --- Additional comments from j...@openoffice.org Sat Jul 31 05:10:08 + 2010 --- Casing options broken by language tags and/or ligatures Issue 1601 (http://qa.openoffice.org/issues/show_bug.cgi?id=1601), marked Fixed and with CWS tl74 included in OOo-dev300m85 (tested) and OOO330m2 (not tested, but likely identical), implements three new and welcome options in Format | Change case, namely: Sentence case Capitalize Every Word tOGGLE cASE Whilst I've not tested tOGGLE cASE (it's not something I need), I have spent a good while poking Sentence case and Capitalize Every Word with a stick. Both functions are, unfortunately, very buggy. The implementation of Capitalize Every Word is especially bad, with a high probability of data loss (disappearing text with no guarantee that Undo works properly). So far, I've seen the bugs be triggered by either language mark-up or ligatures (the latter not necessarily in text selections), which are actually the only conditions I've been testing for. As such, it's likely there are other triggers, too. The data loss is particularly troubling as the "undo" function, even if given sufficient steps, does not necessarily restore the original text correctly. And even that assumes that the user is half-expecting trouble. Issue present in both Writer and Calc (not tested others), and in both cases is severe. I'm attaching an ODT file to this issue. It contains several examples you can try out yourself, together with mock-ups of expected and actual results. ** ISSUE DESCRIPTION In brief, the main problems I've found so far are: Sentence case - The presence of language mark-up within selected text confuses the parser, causing it to consider the marked-up section as a new sentence, thus capitalizing two or more words in the middle of a sentence. Capitalize Every Word - Language mark-up causes similar miscalculations, but more exaggerated, potentially causing data loss (see attached file) - The presence of ligatures, either within selected text, or before it (but in the same paragraph) causes similar problems. - Applying Capitalize Every Word to multiple selections further exacerbates the problem. ** POSSIBLE CAUSES I'm not a programmer, but I think the primary cause of the bugs in either function is a miscalculation of selection bounds, which leads to at times extremely severe offset errors both as regards the selection area and the bounds of the text itself. Among the causes would appear to be: 1. the parser gives language declarations a width (two characters for each "tag", apparently, being one for the opening, another for the closure); 2. the parser miscounts the length of ligatures (unicode FF00 to FF06) whether or not they're selected, which causes both selections and actual words processed to expand to the right - if there's no room at the end of the paragraph for this expansion, text disappears; 3. multiple selections are incorrectly handled (it appears as though errors in one selection block are carried over to the next, and so on). This may simply be the symptomatic of the first potential causes, but it may also be compounded by buffers not being cleared. Or something (TM). The problem was exacerbated, I think, by the original test case (http://quaste.services.openoffice.org/index.php?option=com_tcs&task=tcs_show&tcsid=3116), which is just plain text: no formatting, no language tags, no awkward characters such as non-diphthong ligatures (ff, fi, fl, etc.) ** EXAMPLE The following is a simple example of the buggy behaviour of Sentence case, to give you an idea of the type of problem. See the attached file for many more examples (all different) of both Sentence case and Capitalize Every Word: Input: the rapide brown fox [with "rapide" marked as French] Expected: The rapide brown fox Output: The Rapide Brown fox The underlying code (from contents.xml) is this, where T3 is default format, and T4 is French: The Rapide BroWn Fox-Like Creat ure ** Give
[framework-issues] [Issue 113558] Change Case broken by lan guage tags and/or ligatures
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113558 --- Additional comments from j...@openoffice.org Sat Jul 31 05:12:59 + 2010 --- Created an attachment (id=70901) Examples (input / expected / actual output) - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 104937] Custom frame and graphics styles ignored on ODT save
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=104937 --- Additional comments from j...@openoffice.org Thu Sep 10 00:32:11 + 2009 --- Created an attachment (id=64661) ODT file with incorrect output for a text frame: the framed text at the top of the doc had been formatted with the frame style, present in the output doc, called "Sidenote", but loses that applied style in the saved document. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 104937] Custom frame and graphics styles ignored on ODT save
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=104937 Issue #|104937 Summary|Custom frame and graphics styles ignored on ODT save Component|Word processor Version|DEV300m57 Platform|PC URL| OS/Version|Windows XP Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P2 Subcomponent|formatting Assigned to|writerneedsconfirm Reported by|jurf --- Additional comments from j...@openoffice.org Thu Sep 10 00:31:31 + 2009 --- DESCRIPTION: (bug seen in OOo-Dev_DEV300_m57; OOo-Dev_DEV300_m55 works fine; m56 not tested) Custom frame or graphics styles, whilst visually correct when created and applied within OOo, are not correctly saved to ODT (save as DOC is unaffected). When reopening the ODT file, text that had been formatted with a custom frame style is now formatted in the default "Frame" style, and images that had been formatted with a custom graphics style revert to the default "Graphics" style. The custom styles are still present as document styles, but have not been applied. This is a showstopper as it silently loses all custom frame and graphics formatting, and that in OOo's native format. STEPS TO RECREATE 1. Create a custom frame style or graphics style, with a horizontal position different to default (for easy visual confirmation). 2. Create a text frame or import an image, and apply the custom style to it. 3. Save, close, and reopen... If the bug is present, the frame or image will have reverted to its default position, and the applied style will be "Frame" or "Graphics", not the custom style. I'm attaching one file showing the incorrect output. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 104814] True Type font displays O K in MSWord, not in OpenOffice Writer
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=104814 --- Additional comments from j...@openoffice.org Thu Sep 10 00:17:18 + 2009 --- Glad to be of help... however, as tweaking fonts is beyond most people, I'm not sure marking this issue as FIXED is helpful, as the bug still needs resolution in OOo (the system itself sees the font correctly, as do other programs). I'm no programmer, but I guess OOo's font loading routine needs a check for valid non-alphanumeric characters in font family names. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 104814] True Type font displays O K in MSWord, not in OpenOffice Writer
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=104814 --- Additional comments from j...@openoffice.org Wed Sep 9 16:07:53 + 2009 --- Created an attachment (id=64646) To avoid naming conflicts, here's another version: no commas at all, and with "NEW" after the name - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 104814] True Type font displays O K in MSWord, not in OpenOffice Writer
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=104814 --- Additional comments from j...@openoffice.org Wed Sep 9 15:59:13 + 2009 --- You're still seeing the comma (when double clicking the font file) because I only changed the Font Family name, not the others, as that's the one that appears to confuse OOo. Two possible causes for the new version not working on your system: 1. The original font may still be installed (delete it from your c:\windows\fonts folder first; you might want to place a copy of it elsewhere before). 2. If you haven't rebooted and you have OOo's Quick Starter enabled, you need to shut down Quick Starter before installing the corrected version. Quick tip: you can temporarily "install" a font without having to install it properly, simply by double clicking the TTF (or OTF or PFM) file to show the font preview (be sure OOo's Quick Starter is not running). Don't close it, but start up OOo: you should see the font in the menu. Hope that helps. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 104814] True Type font displays O K in MSWord, not in OpenOffice Writer
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=104814 --- Additional comments from j...@openoffice.org Tue Sep 8 22:00:27 + 2009 --- Created an attachment (id=64624) The same font without a comma in the Font Family name. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 104814] True Type font displays O K in MSWord, not in OpenOffice Writer
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=104814 --- Additional comments from j...@openoffice.org Tue Sep 8 21:58:43 + 2009 --- I can confirm on XP SP2 running DEV300_m57 (Writer). Works with other Windows wordprocs. In OOo, font is replaced in document and in drop-down font list. Problem is caused by the comma in the font's internal Family Name (commas in other name fields don't seem to matter). Attached below is a version of the font without the comma in its Family Name, which should work. It was generated using Adobe's TTX utility for converting TTF fonts to and from editable text. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 104809] OpenOffice 3.1 Crash when opening a docx file
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=104809 --- Additional comments from j...@openoffice.org Tue Sep 8 21:21:19 + 2009 --- Can confirm on Windows XP (DEV V300_m55). - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[gsl-issues] [Issue 43029] support PS-OpenType/OTF/(S FNT with CFF) fonts for PDF export and printin g
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=43029 --- Additional comments from j...@openoffice.org Sat Aug 22 22:57:25 + 2009 --- Verified in Win XP - congratulations! Tested with Iwona, TeXGyre fonts, Yanone Kaffeesatz and other open-sourcers. If this test release seems fine to others, any idea when this might make it into a Dev build? Thanks. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@gsl.openoffice.org For additional commands, e-mail: issues-h...@gsl.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[l10n-issues] [Issue 64400] dash/hyphen (-) should be forwarded to spellchecker
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=64400 --- Additional comments from j...@openoffice.org Sat Aug 22 22:55:58 + 2009 --- Duh! Sorry, ignore my post above ... was intended for another issue (#43029). If someone has the ability to delete posts, feel free to slap that button! - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@l10n.openoffice.org For additional commands, e-mail: issues-h...@l10n.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[l10n-issues] [Issue 64400] dash/hyphen (-) should be forwarded to spellchecker
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=64400 --- Additional comments from j...@openoffice.org Sat Aug 22 22:53:03 + 2009 --- Works for me - congratulations! 20 August test release: Win XP. Tested with various embeddable open-source OTFs, inc Iwona, TeXGyre fonts, Yanone Kaffeesatz etc. If this test release seems fine to others, any idea when this might make it into a Dev build? Thanks. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@l10n.openoffice.org For additional commands, e-mail: issues-h...@l10n.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 102000] AutoSpellcheck and AutoGr ammarcheck - "lost" wavy marking lines
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102000 --- Additional comments from j...@openoffice.org Sun Jul 5 10:35:44 + 2009 --- Not sure what CWS os130a applies to, but can confirm issue in DEV300_m51, released today (5th July). Running XP. Occurs on clean install, also when using older user profile. Showstopper for me - have reverted to older build. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[framework-issues] [Issue 94474] Can't bring up search dial ogue in full screen mode
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=94474 --- Additional comments from j...@openoffice.org Sun May 24 03:32:14 + 2009 --- Confirmed on OOo-dev 3.1.0 (OOO310m4), Win XP. Appears to be a regression, as the same bug (CTRL+F dialog not visible in full screen) was certainly present in June 2007, as it prompted me to write my first macro (last post: http://www.oooforum.org/forum/viewtopic.phtml?t=21611). Macro let the find dialogue be visible, but no longer. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[sw-issues] [Issue 98931] macros does not paste tex t into Notes as in 2.4
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=98931
--- Additional comments from j...@openoffice.org Sat May 23 13:06:43 +
2009 ---
I've came across the same bug (3.1 dev OOO3010m40 build 9388), trying to paste
text into a new Note using a macro. Behaviour was extremely erratic: worked
about one in twenty times, if that, with no apparent logic.
This suggests a problem with timing or threads, and - so far - adding a short
pause after the Note's creation (.uno:InsertAnnotation) seems to work for me. A
simple example:
[code]
Sub Main
dim document as object
dim dispatcher as object
document = ThisComponent.CurrentController.Frame
dispatcher = createUnoService("com.sun.star.frame.DispatchHelper")
dispatcher.executeDispatch(document, ".uno:Copy", "", 0, array())
thisComponent.CurrentController.getViewCursor.collapseToStart()
dispatcher.executeDispatch(document, ".uno:InsertAnnotation", "", 0,
array())
wait 500
dispatcher.executeDispatch(document, ".uno:Paste", "", 0, array())
End Sub
[/code]
Hope that helps.
-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
-
To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org
For additional commands, e-mail: issues-h...@sw.openoffice.org
-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
[gsl-issues] [Issue 69129] Add support for Graphite f ont technology
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=69129 --- Additional comments from [EMAIL PROTECTED] Wed Jun 25 21:22:44 + 2008 --- Thanks Sharon, you're absolutely right - Graphite only understands Graphite. Unfortunately, I can also confirm that the latest OOo build from SIL (2.4) with Graphite doesn't include Uniscribe, so no OpenType. Sob sob sniff... - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 9350] Font list clumsy when have many fonts
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=9350 --- Additional comments from [EMAIL PROTECTED] Wed Jun 25 03:04:51 + 2008 --- Heh, 6000 installed fonts?! Even dedicated font managers can have trouble with that number. More likely to impact on users would be a modest number of installed fonts that include some particularly fancy display fonts containing complex glyphs, such as some Renaissance-style initial caps, very intricate dingbats, or fonts with fancy shading etc, all of which take a while to display. Some form of caching would be a solution. That said, I've just opened a request (issue 91032) for a user-definable font list, which could help circumvent problems. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 17479] "Closest available font" . .. is what?
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=17479 --- Additional comments from [EMAIL PROTECTED] Wed Jun 25 02:56:50 + 2008 --- Can confirm problem on 3.0 dev. Actually, I see no warning at all for missing fonts (on XP). Desired behaviour would be similar to InDesign: On opening doc with missing fonts, OOo to display warning message and three options: - Ignore - Change fonts temporarily - Change fonts permanently First option proceeds as OOo does now, temporarily substituting whatever seems right without altering the document's font definitions. Second option opens a dialog for the user to match installed fonts to document fonts, for display use only (ie. without changing the document's font definitions) Third option is similar to second but changes the actual font names in the doc (ie. substitutes them). - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 13893] When font set to bold, gap between this line and line above this become bigger
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=13893 --- Additional comments from [EMAIL PROTECTED] Wed Jun 25 02:45:52 + 2008 --- This is almost certainly a problem with the fonts: even professional font designers forget the simple step of ensuring that the "Typo Line Gap" defined in each font matches across all styles in a font family. As a workaround in OOo, you can used a fixed (eg. 1cm) line spacing. I'd suggest closing the issue as it's not OOo at fault. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 91032] Request: user-defined font list
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=91032 Issue #|91032 Summary|Request: user-defined font list Component|Word processor Version|OOo 3.0 Beta Platform|All URL| OS/Version|All Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|FEATURE Priority|P3 Subcomponent|ui Assigned to|mru Reported by|jurf --- Additional comments from [EMAIL PROTECTED] Wed Jun 25 02:40:20 + 2008 --- REQUEST It would be nice to have the ability for users to define which (installed) fonts get to appear in OOo's drop-down list. On Windows, for instance, a bunch of fonts are needed by the system but are never used by me when working with OOo (eg. Courier, Marlett, Tahoma, MS Reference, Verdana etc). It would be great to be able to choose which fonts appear in the list. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 82254] Growing and shrinking font size by one point from keyboard
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=82254 --- Additional comments from [EMAIL PROTECTED] Wed Jun 25 02:29:39 + 2008 --- Looks like a duplicate of issue 28016 (and 54923, which also looks like a dupe). - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 53792] If a sentence does contain "special characters" inserted, changing font change them also
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=53792 --- Additional comments from [EMAIL PROTECTED] Wed Jun 25 02:23:52 + 2008 --- I concur with later comments: expected behaviour these days (with Unicode) is not to "protect" characters. Modern symbol-style fonts, such as from Adobe, use Unicode to encode their characters, so fonts can be changed without losing the symbols. Obviously, a lot of fonts still don't use Unicode. It may then be useful to have OOo implement an easy method for protecting sections of text if a user wishes (ie. user selects text and clicks a "protect" button or right-clicks to select "protect"). - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 87462] export to pdf in an old ma ster document does not export the right font
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=87462 --- Additional comments from [EMAIL PROTECTED] Wed Jun 25 02:11:28 + 2008 --- May depend on the font used: OOo still can't embed postscript fonts in PDFs, nor postscript-flavoured OTFs. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 80700] Fontwork and Table border printing
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=80700 --- Additional comments from [EMAIL PROTECTED] Wed Jun 25 02:09:13 + 2008 --- Just a thought: anything to do with font formats? (as in OOo's inability to create PDFs with postscript or postscript-flavoured OTF fonts) - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 79634] aquavcl01_20070630_PPC: Un recognised fonts are inconsistent in imported .doc
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=79634 --- Additional comments from [EMAIL PROTECTED] Wed Jun 25 02:06:39 + 2008 --- Just to help narrow things down: the original doc renders fine on XP with OOo 3.0 dev (uses installed Myriad Pro for Myriad). I notice on the FontBook screenshot that Italic and Bold Italic (not condensed) are missing. Related? - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 77229] Strange layout when loadin g with unknown font
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=77229 --- Additional comments from [EMAIL PROTECTED] Wed Jun 25 01:55:41 + 2008 --- Cannot reproduce (XP: spacing is fine with Arial, which replaces the missing font). Incidentally, my install uses no font replacement table. Also looks okay with the actual Albertus Medium fonts. Does the problem persist on an RTF export? If yes, it might be useful to post that file, as it'd be easy to read the code. I guess the issue has died a natural death though. In the past I've noticed weird font/spacing behaviour from OOo regarding RTF or older Doc versions (eg. from Word 6.0 or Word 97), or in docs not produced by MS Word. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 45358] OOo can't distinguish font s lucida sans oblique and lucida sans demi-obl ique.
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=45358 --- Additional comments from [EMAIL PROTECTED] Wed Jun 25 01:40:38 + 2008 --- Thought I've sift through some unconfirmed font issues. This one seems to be caused either by a system-level conflict between two versions of Lucida Sans, or bad fonts (incorrect internal names and/or weights). Though I'm not on Linux, such a situation will confuse most apps on XP, and I've already seen at least one Lucida set with completely screwed up internal names. I'd suggest closing the issue as it doesn't appear to be OOo's fault. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 90735] fonts displayed are thin, weak, malformed
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=90735 --- Additional comments from [EMAIL PROTECTED] Wed Jun 25 01:34:22 + 2008 --- Can't confirm (no fonts or Gentoo, so I may be completely off-mark) but I can say that although the fonts on the two screenshots appear different, the relative spacing is identical, so visual differences in glyph outlines appear to be the result of rendering/hinting (the oowriter-2.4.1 version is properly hinted, either either grayscale or whatever the Gentoo equivalent to ClearType is, whilst the 3.0 version isn't). My guess is something up with Freetype 2.3.6. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[gsl-issues] [Issue 69129] Add support for Graphite f ont technology
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=69129 --- Additional comments from [EMAIL PROTECTED] Sat Jun 21 03:10:57 + 2008 --- I've added my votes to this 'un. I'm approaching this from a typographical point of view rather than complex scripts. I've long wondered (and ignored) what Graphite was, and only just realized that in addition to implementing Graphite's own "smart font" features, Graphite — certainly SIL's implementation in WorldPad — also implements OpenType features, at least on XP. I'm amazed I haven't noticed this before: seeing as SIL already have various OOo builds with Graphite support (though I haven't tested any), incorporating Graphite into standard builds would appear to be a quick and relatively painless way to implement support for OpenType features. At least the ones that OpenType specs recommend are on by default (eg LIGA for ligatures, and CALT for contextual alternates); features requiring input from the user, eg. figure substitutions, small caps etc., would require GUI work. It may be worth referencing this issue under other issues concerned with OpenType features, ligatures, advanced typography etc. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 87092] replace all broken with fo rmatting
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=87092 --- Additional comments from [EMAIL PROTECTED] Mon Apr 28 22:52:52 + 2008 --- Urk, it's not just macros: I also get stray "x"s using the "Find & Replace" UI (OOo-dev 3.0). To reproduce, paste in a bunch of paste, mark part of it bold, and an overlapping section as italic. eg. Gimme some x's: [b]with luck following here [i]and here[b] - see?[/i] Rats. (don't copy the tags - they're only there to suggest which bits you turn to bold and which to italic) The "Find & Replace" dialog settings are these: Search for: .+ Format: bold Replace with: [b]&[/b] Regular Expressions -> Replace All Ouch. Looks like the bug affects code that splits the tags to avoid overlaps. Workaround needs a macro: before running a search/replace involving formatting, protect your x's by switching them to some unique tag. You've run your replace routine, delete all the x's, and revert the temporary tags back to real x's. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 82185] Invalid formatting hangs F indAll/ReplaceAll with RegExp
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=82185 --- Additional comments from [EMAIL PROTECTED] Sat Apr 26 21:20:36 + 2008 --- Yep, this can be closed I think - tested in OOo-Dev 3.0 BEA300_m1. If any devs are interested, another italic/bold/underline selection/replace problem appears to have cropped up around the same time as this one disappeared, and may or may not be related - Issue 87092 (affects OOo 2.4 onwards). Thank you all. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 87092] replace all broken with fo rmatting
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=87092 --- Additional comments from [EMAIL PROTECTED] Mon Apr 21 00:25:56 + 2008 --- Bug also confirmed on OOo 3.0 beta m9 (OOo-Dev_DEV300_m9_Win32Intel). This is a definite regression introduced in the 2.4 beta series. Unfortunately, oDoc.ReplaceAll is a vital component of macros I use to clean up formatting (e.g. in OCR output); as such, this issue is a showstopper as it prevents me moving beyond OOo 2.3. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[gsl-issues] [Issue 43029] support PS-OpenType/OTF/(S FNT with CFF) fonts for PDF export and printin g
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=43029 --- Additional comments from [EMAIL PROTECTED] Fri Apr 11 00:56:24 + 2008 --- More votes for this issue. I sympathise with the previous poster's frustration at seeing this defect milestoned as "OOo Later". Three years ago there may still have been a little bit of scepticism regarding OTF, but there's no question now about it not being the standard. We're not asking for OpenType *feature* support on this issue, just the ability to embed OTFs in exported PDFs, which is something that any PDF-printer-driver program can do (eg PDFCreator). This should not be flagged as feature but DEFECT. At the very least the blurb writers could be a little more honest when flaunting OOo's PDF export feature, but somehow I doubt that "The PDF export feature will screw up your layout unless you only use TrueType fonts" is quite so attractive to potential punters. Gr... - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 87092] replace all broken with fo rmatting
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=87092 --- Additional comments from [EMAIL PROTECTED] Tue Mar 25 19:07:47 + 2008 --- I came across the same problem independently of reporter. Can confirm bug is present in beta 4.0 rc2 and rc6; likely other rc's too. Bug not present in 2.3.1 or earlier. Looks like some new feature or fix has created this problem. Bug can be isolated to oDoc.ReplaceAll. Tested with Italic and Bold. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 82185] Invalid formatting hangs F indAll/ReplaceAll with RegExp
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=82185 --- Additional comments from [EMAIL PROTECTED] Thu Oct 4 03:32:44 + 2007 --- Created an attachment (id=48691) testcase (two RTF files: one valid, one invalid) - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 82185] Invalid formatting hangs F indAll/ReplaceAll with RegExp
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=82185
--- Additional comments from [EMAIL PROTECTED] Thu Oct 4 03:31:02 +
2007 ---
The testcase docs are "embedded" in the original post! As mentioned above,
simply copy each of the two RTF snippets (the bits beginning {\rtf1\ and ending
\i0}) into a text editor and save them with .rtf extensions. They're complete
RTF files. The first one is valid, the second one - with the additional closure
- is not. The reason for providing such a barebones test case is to isolate the
cause of the problem from anything else.
Anyway, I'll try to post the two testcase files just in case (open them up in a
text editor and you'll see the exact same code as above).
-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 82185] Invalid formatting hangs F indAll/ReplaceAll with RegExp
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=82185
Issue #|82185
Summary|Invalid formatting hangs FindAll/ReplaceAll with RegEx
|p
Component|Word processor
Version|OOo 2.3
Platform|All
URL|
OS/Version|Windows XP
Status|UNCONFIRMED
Status whiteboard|
Keywords|
Resolution|
Issue type|DEFECT
Priority|P2
Subcomponent|open-import
Assigned to|mru
Reported by|jurf
--- Additional comments from [EMAIL PROTECTED] Tue Oct 2 15:53:13 +
2007 ---
This issue could also be named "Failure to remove orphaned/corrupt formatting on
opening"
DEFINITIONS: I'm using RTF files and italics for the example, but the issue
concerns any mark-up file format, viz. RTF, DOC, ODT etc. In the following,
"tag" and "tags" refers to the encoding used to define the hard formatting or
style of a text. For instance, the tags in RTF for italic are \i for the
opening, and \i0 for the closure.
THE PROBLEM: Some OCR engines and word processors produce invalid but readable
files which contain more closing tags than opening tags for one or more
formatting styles (eg. bold, italic, underline etc). The files open correctly in
OOo Writer for most purposes, and are visually correct, too. However, when
finding or fing/replacing all instances of ".*" (Regular Expression) with a
specified format (for example, italic), OOo will hang. The problem persists even
if the original file is saved into another format (eg from RTF to ODT) and is
reopened.
THE CAUSE: (invalid) files that contain more closures than openings for one or
more formatting tags send OOo's Regular Expression engine into a loop when
parsing for styles.
TEST CASE: The following snippets are barebones RTF test files (copy each one
into a text editor and save with an RTF extension)
***VALID***
{\rtf1\ansi\ansicpg1252\deff0
\viewkind4\uc1\pard\fs20
\i Eleutheromania\i0}
***INVALID*** (contains an orphaned "\i0" italic closure)
{\rtf1\ansi\ansicpg1252\deff0
\viewkind4\uc1\pard\fs20
\i Eleutheromania\i0 \i0}
Open the files in OOo and start the Find & Replace dialog. Settings are these:
Search for .*
Format... Italic
Regular Expressions checked
"Find All" or "Replace All" will hang OOo if the open document contains an
orphaned italic closure.
PROPOSED SOLUTION: The most elegant and desirable solution would be to strip
orphaned closures from files when opening them. This should not impact
noticeably on file opening times, and may also solve a heap of other open
issues. Incidentally, whilst it's not OOo that's causing the corrupt files, the
corruption persists when exporting or saving to another format, which is O0o's
problem.
I've marked this as P2 for three reasons: it completely hangs OOo; it causes OOo
to create invalid files; the solution may be solve a host of other bugs, too.
This is my first bug report, so I hope you'll forgive any noob faux-pas...
-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
