View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000428 | context | public | 2010-07-16 14:50 | 2017-03-27 17:14 | |
Reporter | Peter | Assigned To | Hans Hagen | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Summary | 0000428: problem with \setcharacterspacing | ||||
Description | Hello, The setting is lost in the header: \setcharacterspacing[frenchpunctuation] \setupheadertexts[bla: bla] \starttext bla: bla \stoptext Workaround: \setupheadertexts[{\setcharacterspacing[frenchpunctuation]bla: bla}] Cheers, Peter | ||||
Tags | No tags attached. | ||||
|
The same is true for a lot of settings (like alignment) and makign an exception is confusing. An option is to introduce a new key (say: scope=global) for this but then someone needs to identify the settings that make sense as we need to introduce a bunch at the same time. |
|
It's easy: everywhere! (headers, footers, margins, footnotes, heads, lists, bookmarks, etc.) Just math is another thing... Peter |
|
It's never that easy. The 'where' is not the point as it would be 'running text' or 'running text and page ornaments'. The question is: what settings would need it. French spacing is just one. |
|
I don't know the other settings. For "frenchpunctuation" it's 'running text and page ornaments', really everywhere. At least it must be coherent. Take for example: \setcharacterspacing[frenchpunctuation] \setupheadertexts[chapter] \starttext \chapter{bla: bla} bla: bla \stoptext The head is right, but not the header-text. Peter |
|
keep in mind that characterspacing is a generic feature, and although it can be used for french punctuation this does not mean that all spacing should always happen globally, so this is why i want to introduce the scope key .. and believe me, there are many more such features: alignment, mirroring, textcolor, and just as we reset these (as well as all kind of things like leftskip and so) we also reset all attributes (only a few are currently global, like colorspace, making exceptions is not going to happen randomly also, it becomes really messy when this is used locally (can be active then during a pagebreak) and there is no way to distinguish between local and global then ... actually, context tries really to isolate these issues (otherwise you get lots of unwanted side effects that are hard to turn off if needed) ... so it has to be explicit |
|
maybe I'll add text|page as keyword (meaning: page too or text only) |
|
The frenchpunctuation is a language thing, nothing to do with alignment, mirroring, textcolor and so on. So perhaps it would be better to split the code and trigger the frenchpunctuation on "\fr" ? Peter |
Date Modified | Username | Field | Change |
---|---|---|---|
2010-07-16 14:50 | Peter | New Issue | |
2010-08-02 15:33 | Hans Hagen | Note Added: 0000576 | |
2010-08-02 23:29 | Peter | Note Added: 0000587 | |
2010-08-03 02:03 | Hans Hagen | Note Added: 0000589 | |
2010-08-03 23:09 | Peter | Note Added: 0000594 | |
2010-08-03 23:21 | Hans Hagen | Note Added: 0000597 | |
2013-04-05 21:49 | Hans Hagen | Note Added: 0001068 | |
2013-05-31 22:20 | Peter | Note Added: 0001092 | |
2017-03-27 17:14 | Hans Hagen | Status | new => closed |
2017-03-27 17:14 | Hans Hagen | Assigned To | => Hans Hagen |
2017-03-27 17:14 | Hans Hagen | Resolution | open => fixed |