Thread View: adobe.typography
18 messages
18 total messages
Started by Matthew_Wallis
Wed, 25 Apr 2007 16:26
opentype no break property
Author: Matthew_Wallis
Date: Wed, 25 Apr 2007 16:26
Date: Wed, 25 Apr 2007 16:26
1 lines
682 bytes
682 bytes
I'm wondering if anyone knows if Opentype has a "no break" glyph property, so that Indesign will not break lines either before or after a character?
Re: opentype no break property
Author: Neil_Keller
Date: Wed, 25 Apr 2007 19:55
Date: Wed, 25 Apr 2007 19:55
3 lines
644 bytes
644 bytes
Isn't that an application issue rather than a font issue? Neil
Re: opentype no break property
Author: Matthew_Wallis
Date: Wed, 25 Apr 2007 20:00
Date: Wed, 25 Apr 2007 20:00
1 lines
823 bytes
823 bytes
I think you're right. As far as I can see, Unicode/opentype apps just use the unicode values of the character to decide whether they can break the line or not, but I was just hoping opentype might offer a way to change the default behaviour.
Re: opentype no break property
Author: Thomas_Phinney
Date: Fri, 27 Apr 2007 06:07
Date: Fri, 27 Apr 2007 06:07
5 lines
732 bytes
732 bytes
This is an app issue rather than an OpenType issue, but InDesign does have a way of doing this. Apply "no break" character formatting. Cheers, T
Re: opentype no break property
Author: Dominic_Hurley
Date: Mon, 30 Apr 2007 21:36
Date: Mon, 30 Apr 2007 21:36
1 lines
953 bytes
953 bytes
Unicode specifies values for at least two no-break spaces - the standard no-break space (U+00A0) and the zero-width no-break space (U+FEFF). Then there are all the fixed width spaces (em, en, 3-to-em, 6-to-em, etc) that are usually treated as no-breaking spaces by apps.
Re: opentype no break property
Author: Thomas_Phinney
Date: Mon, 30 Apr 2007 23:27
Date: Mon, 30 Apr 2007 23:27
3 lines
689 bytes
689 bytes
Right, but the non-breaking spaces don't help if what you want is for a word not to get hyphenated.... T
Re: opentype no break property
Author: Dominic_Hurley
Date: Tue, 01 May 2007 22:56
Date: Tue, 01 May 2007 22:56
1 lines
885 bytes
885 bytes
True, and in some apps (like ID) a discretionary hyphen before a word will do the same as the no-break attribute, but the way I read Matthew's post, he was asking after a no-break space rather than a way to suppress hyphenation.
Re: opentype no break property
Author: Matthew_Wallis
Date: Wed, 02 May 2007 12:41
Date: Wed, 02 May 2007 12:41
1 lines
981 bytes
981 bytes
Thanks for the replies. I was talking about backslashes actually, which Indesign breaks lines after. I know you can apply no-break, or type a discretionary hyphen, but I was hoping opentype might offer a way to avoid manual intervention.
Re: opentype no break property
Author: Neil_Keller
Date: Wed, 02 May 2007 16:52
Date: Wed, 02 May 2007 16:52
5 lines
676 bytes
676 bytes
Matthew, Do you mean backslashes (\) or slashes (/) ? Neil
Re: opentype no break property
Author: Matthew_Wallis
Date: Wed, 02 May 2007 20:36
Date: Wed, 02 May 2007 20:36
1 lines
801 bytes
801 bytes
Can't remember which was the problem now - I think it was backslashes. But Indesign breaks lines after both of them regardless of the hyphenation setting, and as far as I can see there is no preemptive way to control this.
Re: opentype no break property
Author: Neil_Keller
Date: Wed, 02 May 2007 21:36
Date: Wed, 02 May 2007 21:36
3 lines
791 bytes
791 bytes
The only reason why I even ask is that the backslash (\) character is so rarely used. Going off-topic for a moment, I cringe every time I hear a commercial or promo that gives a Web address with backslashes. Neil
Re: opentype no break property
Author: Dominic_Hurley
Date: Wed, 02 May 2007 22:00
Date: Wed, 02 May 2007 22:00
3 lines
1374 bytes
1374 bytes
> But Indesign breaks lines after both of them regardless of the hyphenation setting I don't think it does, unless IDCS3 has changed this. I may be wrong, and I do recall some discussion about how different versions of ID handled URLs when it came to breaking them, but my quick trial shows that IDCS2 doesn't break after the forward or back slash. It will, of course, break if you're putting spaces around them, but then you can use U+00A0. Note, however, that these NB spaces will not flex with justification, so the best approach is to use a normal space with a no-break attribute. Because you don't want manual intervention, I assume you're importing from a database or from some source and you want it all precoded. Can you code to include a no-break character style around the spaces?
Re: opentype no break property
Author: Matthew_Wallis
Date: Thu, 03 May 2007 10:56
Date: Thu, 03 May 2007 10:56
1 lines
1107 bytes
1107 bytes
The problem is actually arising when working in Indian languages and having to use non-unicode roman-encoded fonts which contain glyphs for the Indian script in all the font's available slots (you have to use a separate font for roman text). So Indesign is breaking Indian words at what it thinks are backslashes or slashes. I've checked it again and it's definitely doing it (Quark doesn't do it incidentally). If it's not doing it with you Dominic there must be some difference in our setup and I'd like to know what that is.
Re: opentype no break property
Author: Joel_Cherney
Date: Thu, 03 May 2007 21:01
Date: Thu, 03 May 2007 21:01
3 lines
1038 bytes
1038 bytes
I just did some experimentation with a few of my (obsolete, yet still useful every day) proprietary-encoding Indic fonts. In each case, I found that all I had to do was turn off hyphenation, and apply No Break to the glyph that was encoded as a slash. Once I'd done that, ID respected the No Break attribute, and no longer tried to break the text on glyphs that occupied codepoints on which ID would usually be permitted to break. What font are you using?
Re: opentype no break property
Author: Matthew_Wallis
Date: Thu, 03 May 2007 21:58
Date: Thu, 03 May 2007 21:58
2 lines
1112 bytes
1112 bytes
Are you saying that if you apply no break to a glyph once, ID will not break on that glyph anywhere else in the document? As far as I can see, no break applies only to the text selected. The fonts that were causing a problem were the Shree-Lipi ones. Unfortunately they seem to have put commonly-used glyphs on the slash codepoints, whereas the other fonts we often use put rarely used glyphs there.
Re: opentype no break property
Author: Dominic_Hurley
Date: Thu, 03 May 2007 22:59
Date: Thu, 03 May 2007 22:59
3 lines
831 bytes
831 bytes
No-break applies only to the text its applied to. But you can easily do a search and replace to apply no break to all slashes. Today ID is breaking after slashes. It wasn't the other day, but I don't know what the difference between the files is.
Re: opentype no break property
Author: Joel_Cherney
Date: Fri, 04 May 2007 00:27
Date: Fri, 04 May 2007 00:27
12 lines
1664 bytes
1664 bytes
Are you saying that if you apply no break to a glyph once, ID will not
break on that glyph anywhere else in the document? As far as I can see,
no break applies only to the text selected.
Whoops! No, I wasn't trying to say that at all. Of course, you'd need to either do a find/replace, or perhaps automate the process with a script. Most of the fonts for the languages I handle (notably Khmer, Lao, and Burmese) have odd proprietary encodings, much like your Shree-Lipi. Because each font family has its own quirks and hassles, I've actually written my own rudimentary text-cleanup scripts to automate the process of applying No Break to particular glyphs, replace spaces, fix problems with discretionary hyphens, and so on. I've gone so far as to include my translator's favorite typos in these scripts.
If you spend a lot of time processing Hindi text, you may want to investigate scripting ID to take the text-prep busywork off your shoulders.
Re: opentype no break property
Author: Matthew_Wallis
Date: Fri, 04 May 2007 10:00
Date: Fri, 04 May 2007 10:00
1 lines
678 bytes
678 bytes
Good thought, thanks
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads