Issue 109876

Summary: Unwanted line break if "New (text only)" autotext inserted
Product: Writer Reporter: mmartin_bln <martin.meitzner>
Component: editingAssignee: writerneedsconfirm <swneedsconfirm>
Status: CLOSED DUPLICATE QA Contact: issues@sw <issues>
Severity: Trivial    
Priority: P3 CC: issues
Version: OOo 3.1.1   
Target Milestone: ---   
Hardware: PC   
OS: Linux, all   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---

Description mmartin_bln 2010-03-06 15:16:49 UTC
First: I'm sorry to open another issue on this one, but I am completely dissatisfied with the 
classification of the problem as "Enhancement" for OOo v2.1 in Issue 79861.

Please read on before you consider marking this one as duplicate.

What's the issue about? As reported in79861, when an AutoText entry is created using the "New 
(text only) option in the AutoText dialog, the expected behavior would be that the AutoText entry is 
stripped from all formatting and saved. When you insert the AutoText again, you'd expect it to 
behave like unformatted text, taking the formatting of the paragraph you're inserting it to.

What happens instead is that the AutoText is inserted, followed by a newline or carriage return. I my 
case I was trying to create AutoText entries for the THIN SPACE als well as the HAIR SPACE 
characters, because I use them frequently in my typsetting works. When I insert the AutoText, I want 
it to adapt to the respective formatting of the text I am editing. 

Having these characters inserted with a succeeding line break makes the feature unusable for that 
purpose. And since "normal" AutoText behaves the way I expect it (inserting in-place WITH the 
formatting of it's own, without a line break), I reckon the behavior of the "text only" AutoText to be 
inaccurate. BTW: it is _not_ possible to remove the newline by editing the autotext entry. It is inserted 
again after saving the changes.

To me it seems evident, that the issue reported is a DEFECT, since the behavior that can be 
observed is different from what you expect the regarded function to do in the first place. The 
Problem also ist still present in v3.1.1 (ubuntu5), and as I suppose in more recent versions also. 
Please tar and feather me if it's not. I don't have the possibility to install a higher version on the 
computer I'm using right now. But it should be easy for someone else running latest OOo to confirm 
or to dissent.
Comment 1 eric.savary 2010-03-06 16:23:47 UTC
duplicate

*** This issue has been marked as a duplicate of 79861 ***
Comment 2 eric.savary 2010-03-06 16:23:59 UTC
closed