View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001540||Scribus||Story Editor / Text Frames||public||2005-01-13 14:33||2012-01-05 01:02|
|Target Version||Fixed in Version|
|Summary||0001540: Issue with stylesheet and emphasis like italic or bold fonts|
|Description||Say you have a text that includes some words in italic or bold.|
You want to edit those emphasized words.
From within Scribus, there are 3 ways to do that.
1. You edit directly into the text frame
2. You use the Story Editor
3. You use the Search/Replace dialog
Also, there are 2 ways to format the text
1. Freely format text
2. Use stylesheet
The issue occurs while using the stylesheets.
Once you try to edit your emphasized text, you will discover that while using Story Editor and/or Search/Replace, all will be fine and the editing process really straight forward.
But when you edit directly in the text frame, which is lots more convenient for that kind of last-minute-editing, the new text retains the formatting of the style sheet no matter if you add a letter or type on a selected one.
|Steps To Reproduce||1. Create a stylesheet, create a text frame, put some text in and apply the stylesheet.|
2. Then, using any method, put a word in the boldface of the font, or any other font.
3. Once you're done, leave the text frame, get back to it, and try to edit that emphasized word. Any letter you type, in add or replace mode, will retain the original formatting of the stylesheet, not the font you used to emphasize.
|Additional Information||This has consequences in production.|
It's time consuming to have to re-apply locally the proper formatting for such small editing tasks. Also, the other 2 methods that work have drawbacks : Story Editor is not wysiwyg (and I don't say it should be) and you typically need wysiwyg here or some way of finding rapidly where that misspelled word is. The other possible method is the Search/Replace dialog but although being a useful feature, it's not efficient in all situations.
In the end, the most intuitive way cannot be used efficiently.
|Tags||No tags attached.|
|would be nice to see if this can be fixed in 1.2.2|
|Louis, Can you post a simple test case to look at this ? Thanks...|
bug1540.png (81,181 bytes)
bug1540.png (81,181 bytes)
bug1540.sla (11,077 bytes)
Here you are! Just uploaded example files.
I agree, this is an annoyance. However, fixing it will require the new file format stuff in 1.3/1.4.
Thanks for the good test case file. It realy helps to understand the issue.
|Is this still an issue in 1.4 ?|
|2005-01-13 14:33||louisdesjardins||New Issue|
||Note Added: 0004153|
||Product Version||1.2.1 => 1.2.2cvs|
||Note Added: 0004264|
|2005-04-16 17:36||louisdesjardins||File Added: bug1540.png|
|2005-04-16 17:36||louisdesjardins||File Added: bug1540.sla|
|2005-04-16 17:37||louisdesjardins||Note Added: 0004274|
|2005-04-16 17:38||louisdesjardins||Note Edited: 0004274|
||Note Added: 0004522|
||Status||new => acknowledged|
||Product Version||1.2.2cvs => 1.3|
||Note Added: 0027457|
|2015-09-17 20:08||Kunda||Category||Story Editor / Text Frames => Story Ed/Txt Frames|
|2015-09-17 20:12||Kunda||Category||Story Ed/Txt Frames => Story Editor / Text Frames|