Bug 66914 - EDITING Writer does not recognize fields as part of a sentence and applies autocorrection (capitalize first letter)
Summary: EDITING Writer does not recognize fields as part of a sentence and applies au...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version: 3.3.0 release
Hardware: All All
: medium minor
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
: 76139 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-07-15 05:56 UTC by János Néhrer
Modified: 2014-06-04 04:53 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments
Test document. The isse can be seen on the third page, in the line with a field at the beginning. (118.40 KB, application/vnd.oasis.opendocument.text)
2013-07-15 05:56 UTC, János Néhrer 		Details
View All

Description János Néhrer 2013-07-15 05:56:10 UTC 
Created attachment 82431 [details]
Test document. The isse can be seen on the third page, in the line with a field at the beginning.

Enviroment
LibreOffice 3.6-4
Operating system: Windows 7 x64 and OpenSUSE

Steps to reproduce
1. Choose 'Insert'-> 'Fields' (choose any field)
2. Press space after the field and start typing...

Results
The first written word after the field will be autocorrected to have a capital
letter at the beginning.

Expected results
LibreOffice should handle the field as part of the sentence, so the text after
it should start in lowercase by default.
Comment 1 János Néhrer 2013-07-15 05:56:56 UTC 
The issue exists in 4.0.4 as well.
Comment 2 Cor Nouws 2013-07-15 08:37:53 UTC 
Hi jános,

thanks for the report. I confirm the behaviour.

Is already present in 3.3.0, so set the version accordingly. 
And I add some words on Autocorrection to the summary

Cheers,
Cor
Comment 3 tommy27 2014-06-04 04:53:17 UTC 
*** Bug 76139 has been marked as a duplicate of this bug. ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.