View Issue Details

IDProjectCategoryView StatusLast Update
0010539ScribusTypographypublic2019-01-17 16:11
Reportermeho_r Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
Status confirmedResolutionopen 
PlatformLinuxOSDebianOS VersionWheezy
Product Version1.4.0 
Target Version1.5.4Fixed in Version 
Summary0010539: Optical margins, protrusion into the left margin doesn't work
DescriptionActually, there are two issues:

1. When text or text frame is selected and "Both Sides" or "Left Only" optical margin is selected, nothing happens for quotation marks, hyphens, en-dashes and em-dashes on the left side of the text (no matter of text alignment).

2. There is inconsistency regarding character protrusion in general. E.g.:
a) Quotation marks: protruded on the right side, not on the left;
b) Hyphens: protruded on the right side, not on the left;
c) En-dashes: protruded on the right side, not on the left;
d) Em-dashes: do not get protruded neither on the right, nor the left side.

I mentioned only these characters which are most obvious when protrusion takes place, but there are other more subtle cases, like capital letter "A" at the beginning of a non-indented paragraph, exclamation mark at the end of a line, etc., which do not work either.
Steps To Reproduce1. Create a text frame.
2. Place (a) a double left quotation mark at the beginning of the first paragraph; (b) a hyphen at the beginning of the second paragraph; (c) an en-dash at the beginning of the third paragraph, and (d) an em-dash at the beginning of the forth paragraph.
3. Set text alignment to "Justified" or "Forced Justified".
4. Set optical margin to "Both Sides" or "Left Only".
Additional InformationWith Scribus 1.4.0.rc5 on Windows, this issue occurs only for hyphens, en-dashes and em-dashes, which do not get protruded into the left margin, but quotation marks do.
TagsNo tags attached.
Patch

Relationships

has duplicate 0014832 closedjghali Optical Margins (hanging punctuation) misses quotation marks on the left 
related to 0012265 new Optical margins setting too verbose and unintuitive 

Activities

bubu

2012-10-07 19:14

reporter   ~0029020

Last edited: 2012-10-07 19:48

View 2 revisions

I can confirm this bug:
- Ubuntu Scribus 1.4.1 64bit
- Ubuntu Scribus 1.5.0svn 64bit
- Windows Scribus 1.4.2svn latest snapshot on SF (12-10-07)

Pancho

2014-04-23 13:56

reporter   ~0031767

Confirm for 1.4.3.
IMHO more than a minor bug.

nasfarley88

2014-08-20 10:40

reporter   ~0033298

Can confirm for 1.4.4

Kunda

2014-08-20 12:47

updater   ~0033301

upgrading to 'major' severity.

jeff

2016-06-29 01:14

reporter   ~0041743

I would so love to see this work, not only for punctuation but also some letters such as A, T, V, W, Y, C, O. The bottom of https://en.wikipedia.org/wiki/Optical_margin_alignment has a nice table mentioning approximate percentages of justification offsets depending on the type of character.

I'm particularly interested in this to apply to headers; currently there is no way to do have "properly" aligned headers (bigger text) vs body text, other than having separate text frames for everything, which makes the flow mostly impossible to manage.

Scriber

2017-06-28 08:41

reporter   ~0044103

Can confirm for 1.5.3

MZaske

2018-12-01 10:52

reporter   ~0045670

I confirm this for

Scribus Version 1.5.5.svn
07 November 2018
Build ID: C--T-*-C1.16.0-Windows-64bit
Using Ghostscript version 9.22

aka scribus-1.5.5.svn-snapshot-181125-x64.exe

MZaske

2018-12-01 11:14

reporter   ~0045671

I would also like to beg, for this problem to be given some priority. My team is producing an entire batch of childrens' books. Each page has a dominant illustration and typically only 2 - 5 lines of text in huge sizes of 20pt+. So the left margins look very frazzled whereever there is a possessive:


Related feature request, if one of the developers is looking into this:
This is a hint about certain minority languages: There is more possible "punctuation" or "small stuff" which can occur at the beginning of a line (in LTR) than you might imagine. In our case, the possessive on nouns is represented by a word-initial typographical apostrophe (U+2019) >> ’ <<. So a line starting with a "left-weak" glyph like "j" preceeded by an apostrophe looks ragged: ’ jɛŋjɛlɛ a da ada ma ni. (...[previous line] our local danses where happening.)

So what would really help please, would be

- either the option for users to define their custom set of glyphs/characters which get considered for margin-correction

- or to please add the typographical apostrophe U+2019 and the keyboard apostrophe U+0027 to the characters which get treatment on the left-side too

- or some hint in the documentation where in source this "set of gplyphs" is defined or listed, so that brave users can try to hack it.

Thank you.

ale

2018-12-03 15:57

manager   ~0045676

martin, i don't think that there is any promise that the team can do... but if you try to define as well as possible how the feature should work and provide a detailed specification, it's likely that the chances that somebody (or even a member of the team) will program it.

there are a few people in the scribus community who work a lot with the tool and has good ideas about how scribus should work... and it would be nice to see you team up and produce proposal for changes and new features.
ideally, somebody in the group knows how to write specifications.

here are two links about writing software specifications:

- https://codeburst.io/on-writing-tech-specs-6404c9791159
- https://eng.lyft.com/awesome-tech-specs-86eea8e45bb9

imo, we could start a discussion in the mailing list or in the forums to write an how-to for writing specifications for scribus...
the goals would be to avoid both huge proposals that don't lead to any change nor wishes that are too much shaped on the user's workflow to be directly programmed.

Scriber

2019-01-17 16:11

reporter   ~0045803

Are there any news on this issue?

Since the function works properly on the right side of a column, I would appreciate if the developers could make it work on the left side of a column in the same way.

Issue History

Date Modified Username Field Change
2012-01-25 09:22 meho_r New Issue
2012-10-07 19:14 bubu Note Added: 0029020
2012-10-07 19:48 bubu Note Edited: 0029020 View Revisions
2014-04-23 13:56 Pancho Note Added: 0031767
2014-08-20 10:40 nasfarley88 Note Added: 0033298
2014-08-20 12:42 Kunda Severity minor => major
2014-08-20 12:43 Kunda Status new => confirmed
2014-08-20 12:47 Kunda Note Added: 0033301
2014-08-20 12:47 Kunda Target Version => 1.5.1
2016-01-23 17:17 cbradney Target Version 1.5.1 => 1.5.3
2016-04-10 14:36 Kunda Relationship added related to 0012265
2016-06-29 01:14 jeff Note Added: 0041743
2016-12-08 22:04 Kunda Target Version 1.5.3 => 1.5.4
2017-05-29 18:16 jghali Relationship added has duplicate 0014832
2017-06-28 08:41 Scriber Note Added: 0044103
2018-12-01 10:52 MZaske Note Added: 0045670
2018-12-01 11:14 MZaske Note Added: 0045671
2018-12-03 15:57 ale Note Added: 0045676
2019-01-17 16:11 Scriber Note Added: 0045803