Forum Replies Created
-
AuthorPosts
-
joelcherney
MemberIt’s not quite accurate to say that “hebrew is supposed to be supported now in both of these programs.” You can get RTL behavior at the character, paragraph, story, and document levels in a variety of different ways in a variety of different apps, going back to CS4.
If you wind up subscribing to Creative Cloud, you can set your language to English (Hebrew) in the Creative Cloud app, then uninstall InDesign and reinstall, and the new install will have all of the RTL tools – because you will have downloaded the ME edition. That will have binding direction toggle in the, um, Page Setup window. If you subscribe, you’ll always have access to both plain-vanilla English and Middle-East versions of ID.
In InDesign CS6, the Middle East edition would be a separate purchase. Sounds like you already have a standalone licence for CS6. I suspect that you can still buy a separate CS6 ME license. Or you can use World Tools, as David suggests – a much cheaper option. Personally, I prefer the World Tools interface in CS6 to the CC Middle East edition, but that’s just a matter of taste, I suppose.
joelcherney
MemberNumber lists in translation in InDesign are somewhat awkward. One of my file-preparation techniqes for all InDesign documents is to replace automatic numbering with manual numbering. I have quite a few raw-text files with different kinds of enumerated lists so that I can compile numbered lists in a number of languages – sometimes with a script, sometimes with other techniques.
I used to allow InDesign to auto-number for languages which it does support, but it was confusing in 20-language jobs to have multiple source files, some with numbering managed by ID, some with numbering managed by Trados, some with numbering managed manually by yours truly. It was much faster to just tell everyone in our translation department “Never use auto-numbering in ID without thus-and-so conditiions.”
October 27, 2011 at 3:35 pm in reply to: InDesign adding unnecessary spaces — how to disable or work around? #60934joelcherney
MemberWow! Now that is a really cool script. I'm not terribly suprised that I don't remember seeing it in the past; West African scripts are a weak point for me. If someone had told me that it composed like hangul I am sure I would have paid closer attention. :)
As far as this issue goes: I'd strongly suggest defining that non-whitespace single-dot word divider someplace that is not 0020. Fonts for scripts that have non-whitespace word dividers, like Ge'ez, typically encode them elsewhere. (x1361 “ETHIOPIC WORD SPACE”) Fonts that have spaces that would diverge significantly from a generic ASCII space (e.g. fullwidth and halfwidth spaces for East Asian scripts) also encode those spaces someplace that is not 0020. I'm no font designer, so I wonder what “best practices” are here, but I can't think of an argument against leaving the ASCII space for ASCII. Sorry, but it looks like we (“we” being “people who care about complex scripts” here) will be working around the ethnocentric assumptions of mid-20th-century computing wonks for, well, for as long as Western Civ exists.
I've just tested a custom font that contains ligatures and an outline in the space glyph and got the same problem in InDesign CS 5.5 as described by quinyu.
I can't see it as an InDesign issue, really; it's an ASCII issue, and you can expect other apps besides InDesign to be picky about what is encoded in ASCII. It's the kind of thing that software developers assume to be set in stone.
and you might need World-Ready Paragraph Composer turned on
Pretty sure that the Japanese composer will respect all of the relevant OT methods. :) However, quinyu, you should probably go and learn how to turn the WRC on and off so that people who aren't you might be able to use your font in non-JP ID at some point in the future.
October 26, 2011 at 1:37 pm in reply to: InDesign adding unnecessary spaces — how to disable or work around? #60916joelcherney
MemberAre you using a font that has a proprietary encoding, or is it a Unicode font? I only ask because I don't recognize the script, at all… which is unusual, I thought I could identify any living language by eyeballing a few glyphs.

If you don't know what I mean, just select any one glyph in InDesign, then go to Type -> Glyphs. Your one highlighted glyph will show up; if you mouse over it, a popup should identify the glyph name. If the glyph is not named correctly in that mouseover popup, then you are using some kind of non-Unicode font. In that case, I'd suggest looking at the kerning setting and making sure that it's not set to Optical. If you're using an old-fashioned proprietary-encoding font, then you'll mouse over a glyph and it will say something like “LATIN CAPITAL A WITH DIAERESIS.” InDesign will follow suit by treating your supposed-to-be-combining glyph as an a-with-diaeresis, which will generate spurious spaces.
Lastly, in case this is not helpful: please do post again with more details. What's the name of the font you are using? Do these ligatures work correctly in other OpenType-aware applications? And please, please do tell us what language that is!
Edited (for typos)
-
AuthorPosts
