View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001680 | Scribus | General | public | 2005-02-17 15:00 | 2006-12-21 23:42 |
| Reporter | ExScite | Assigned To | avox | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | duplicate | ||
| Platform | n/a | OS | n/a | OS Version | any |
| Product Version | 1.3 | ||||
| Summary | 0001680: Automatic Kerning by user-defined pairs wanted | ||||
| Description | True kerning refers to adjustment, usually removal, of space between two adjacent characters for aesthetic reasons. Commercial DTP programs include automatic kerning, which allows the user to definine in Kerning Tables pairs of letters and the amount of space to be adjusted. This must be done for each font | ||||
| Tags | No tags attached. | ||||
| Patch | |||||
|
|
You can already do that, just install the .afm file for you Type1 Font. Dunno how that's solved in TrueType fonts. An example done with URW Palladio: http://wiki.scribus.net/index.php/Kerning |
|
|
Please have a look at the kerning options of QuarkXPress and InDesign. Users need to have the opportunity to manually set kerning pairs for each font separately. It is also important to be able to import and export those kerning pairs! I think louisdesjardins would be interested in this. Can someone send a reminder? |
|
|
TomK32, afaik TrueType and OpenType have kerning tables included within the font. |
|
|
Christoph, I don't have InDesign or QuarkXPress, so I don't know how they handle it. IMHO kerning pairs for fonts should be defined by the font designer, not the user. fontforge lets you do that. OTOH it should not be too hard to implement that in Scribus if it is really needed. Just pairs or also glyph classes? In addition to font's kerning value or totally replacing it? Note that OTF fonts have special kerning tables which are not used by Freetype/Scribus yet. Those tables allow arbitrary context dependent glyph repositioning, so don't expect Scribus to override that with manual kern pairs (unless you can supply a very clear and unambigous specification how interaction between GPOS tables and user kerning should work). |
|
|
Popping this up, is this similar to that feature from Quark? http://www.creativepro.com/img/story/121703_fg4.gif |
|
|
Also, if implemented Avox, the preview window should have a Text Size setting, this looks pretty lame to me haha. |
|
|
Is it questionable wether this feature is useful or not. It is time consuming and restrictive : you have to set each font. Unless a font is very badly designed... In that case, you might as well edit it directly into a font editor and let others benefit of your work as well. Or use another font. This feature has been into Quark for years. I can't remember when it was introduced but it might have been as early as in version 2.x. Does that give the user more control? Certainly. At the same time, I'd be very interested in knowing how many people are using it. In all my years in this business I can remember only one client who modified those pairs. It was for a very specific use [they actually used it to create a "thin space" with French punctuation] and they used very few fonts (and maybe they used only one font, actually). I never thought this was the way to go although I must say the result was, to a certain extent, fine. We don't use it at all and I will not use it in Scribus either. My own personnel opinion is a very small percentage of users will actually need such a feature. The absence of it wouldn't prevent me to use Scribus on a professionnal basis. There are other weak areas that would retain my attention long before this. :) FYI, the screenshot provided by PLucAuclair is exactly that. I checked in Quark 6.5 and the interface is just about the same. You type in any combination of 2 glyphs of a font, and you enter a kerning value (pos. or neg.). The viewer lets you see the result. You can import/export a table from a text editor. Each font is different so each font has its own kerning table. Unless it is very easy to implement, I would leave that as an open RFE and give it a low priority. |
|
|
I'd say the same, if it's hard to do I'd postpone it for implementation after the new text engine. I can definitely see a use for it, a bunch of fonts have some lacks, especially kerning between caps is often poor (especially in free fonts lots of people use, just take Bitstream Charter). |
|
|
I wouldn't set the priority to low, although it certainly isn't high. There are always some fonts with kerning pairs that look better after a (minor) tweak. Being able to save the adjusted kerning for use in other docs seems quite useful to me. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-02-17 15:00 | ExScite | New Issue | |
| 2005-02-18 12:15 | TomK32 | Note Added: 0003736 | |
| 2006-04-14 14:48 | mhanski | Relationship added | related to 0001851 |
| 2006-04-14 14:56 | mhanski | OS Version | => any |
| 2006-04-14 14:56 | mhanski | Product Version | => 1.3 |
| 2006-04-17 01:03 |
|
Status | new => assigned |
| 2006-04-17 01:03 |
|
Assigned To | => avox |
| 2006-04-17 01:03 |
|
Relationship deleted | related to 0001851 |
| 2006-04-17 11:03 | mhanski | Relationship added | related to 0003661 |
| 2006-04-17 11:04 | mhanski | Relationship added | related to 0001851 |
| 2006-04-22 00:40 | christoph_s | Note Added: 0010284 | |
| 2006-04-22 16:30 | PLucAuclair | Note Added: 0010319 | |
| 2006-04-25 00:32 | avox | Note Added: 0010447 | |
| 2006-04-25 07:20 | mhanski | Relationship added | related to 0001425 |
| 2006-05-24 13:00 | PLucAuclair | Note Added: 0011438 | |
| 2006-05-24 13:08 | PLucAuclair | Note Added: 0011439 | |
| 2006-05-24 16:15 | louisdesjardins | Note Added: 0011442 | |
| 2006-05-24 16:30 | PLucAuclair | Note Added: 0011445 | |
| 2006-05-24 22:43 | christoph_s | Note Added: 0011460 | |
| 2006-12-21 23:35 | avox | Relationship added | duplicate of 0004645 |
| 2006-12-21 23:35 | avox | Duplicate ID | 0 => 4645 |
| 2006-12-21 23:35 | avox | Status | assigned => resolved |
| 2006-12-21 23:35 | avox | Resolution | open => duplicate |
| 2006-12-21 23:42 | avox | Status | resolved => closed |
