Issue 2491 - Not capitalizing a word following an abbreviation
Summary: Not capitalizing a word following an abbreviation
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: 641
Hardware: Other Other OS
: P5 (lowest) Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords:
: 10447 (view as issue list)
Depends on:
Blocks:
 
Reported: 2001-12-10 09:37 UTC by simonbr
Modified: 2003-09-08 16:56 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description simonbr 2001-12-10 09:37:02 UTC
Hi Stefan, 
It would be nice if exceptions could be made to the autocorrection "Capitalize 
each word of a new sentence", to handle the case when the period occurring 
before the word is part of an abbreviation, e.g. "e.g." instead of the end of a 
sentence. 
Best regards, 
Simon
Comment 1 simonbr 2001-12-10 10:49:12 UTC
Correction: I found it is already implemented:  
(Tools>autocorrection>exceptions>"abbreviations (no subsequent 
capital)".
However, there appear some peculiarities in its operation.

Earlier today, I typed "e.g. walk", which was autocorrected to "e.g. 
Walk" which I changed back by CTRL+Z. Although I am not completely 
sure at this point, I seem to remember that when I tried this again, 
it was again autocorrected, so the exception had not been 
autoincluded. 

When I looked in the dialog box Tools>autocorrection>exceptions, the 
language was "English (UK)" (probably because I have an UK English 
version of Windows) and nothing was shown in the list of 
abbreviations. Autoinclude was set enabled, but it did not appear to 
work. I could add an abbreviation to the list using the dialog box, 
and then the exception was applied correctly.

After changing the language to "English (USA)" I found that there 
were abbreviations in the list, and that autoinclusion worked.
Autoinclusion also remained working after having changed back 
to "English (UK)". However, new abbreviations appeared in the list 
with "English USA" instead of the "English (UK)" one. The USA list of 
abbreviations was applied under the UK language setting.

In conclusion:
1) There is some confusion in the distinction between English (UK) 
and English (USA) where this function is concerned
2) the function and the autoinclusion appear not to work when 
language is English (UK) on installation and not subsequently changed 
(not completely sure on this point).

Best regards, 
Simon.
Comment 2 simonbr 2001-12-10 11:37:27 UTC
Another correction: I checked by uninstalling OOo, specifying "remove 
all files", and finding some files left in the installation 
directory, removing that directory myself, then reinstalling. 
Point 2 is not the case after all. Autoinclusion works, although the 
exception is added to the English (US) list instead of the English 
(UK) list.
Comment 3 stefan.baltzer 2002-01-07 11:27:36 UTC
Reassigned to Michael.
Comment 4 michael.ruess 2002-01-07 12:35:22 UTC
Yes, indeed, you misunderstood something...
When you choose a certaion language in the Autocorrect-dialog, it does
not mean that the selected list is used. Which list actually is used
by the program is dependent on the language you use in the document
(have a look in Format.Character or the Standard-paragraph style).
Comment 5 michael.ruess 2002-01-07 12:35:38 UTC
Closed, because not a bug.
Comment 6 prgmgr 2003-06-14 14:12:49 UTC
*** Issue 10447 has been marked as a duplicate of this issue. ***