Forum Replies Created
-
AuthorPosts
-
Chris Thompson
MemberHere in the UK, there seem to be plenty of design agencies and similar companies using CS3 among my clients. Even some using earlier versions than that. Hard to put a figure on it though.
February 8, 2011 at 9:31 am in reply to: How to add a paragraph with specified style to master text frame #58679MemberHave you looked at InDesign Tagged Text files? I use these in database-generated text with CS3. Simplest way is to create one element of the structure in InDesign, save as tagged text, and work out from there what tags you need to surround the text coming out of your data source.
There may well be an alternative way of accomplishing the same result with XML, but I'll leave that to an expert.
By the way, I'm not sure the thread title really reflects what you want to do, which might be why there are so few replies so far.
December 31, 2010 at 2:40 am in reply to: cursor moves in opposite direction in middle east versions of InDesign CS5 #58251MemberIf you think that's confusing, just wait until you reach some RTL text mixed with LTR numbers and opening/closing brackets. Story Editor can sometimes be a better way to sort things out in those situations.
MemberSelect the text box that the table's in and rotate that (right-click – Transform – Rotate)?
Although that doesn't help on the second and subsequent pages, so to avoid rotating lots of text boxes, you'd need a text frame on the master page(s), rotated on the master pages, and it should flow through. Just tried with a test file and it does just that.
Good luck, Chris.
MemberDo you mean swap rows for columns?
The only simple “I'm not a programmer” way I've found to do that is in Excel, where it's known as Transpose. You have to select all the table, copy it, and then preferably in a new Excel file, Edit/Paste Special and there's a tickbox “Transpose”.
regards, Chris.
MemberSorry, forgot to add, those remarks above are with real, typed bullets.
If I used Type – Bulleted Lists – Apply Bullets, it just worked straight away. It set a right indent of 6.35 mm, and first line left indent of -6.35 mm, and a left indent of 0 mm. However, if I then try to adjust the first line left indent, it slaps me on the wrist with “invalid indent value” all the while the left indent is still 0. So there's something not quote right about the internal logic I'd guess.
MemberTinkering about with CS4 and “AN Other” plugin for RTL text (sorry, Harbs), I can get bulleted Arabic text to behave correctly* with the indent set at (for example) 5 mm in both left and right indent fields in the regular InDesign Paragraph panel, and -5 mm in first line indent to bring the bullet back. It didn't work with just one of the indent fields filled in.
* i.e. the right hand side of the first line has a bullet, the text after the tab then starts at 5 mm from the right, and the second and subsequent lines all start at 5 mm from the right.
regards, Chris.
MemberAnother tip is to hold shift while pressing the left arrow key, which highlights text back from the cursor position. So long as the text isn't overset, and so long as your highlight colour is nice and contrasty, I find that chunk of highlight easier to spot than the thin I-beam cursor. Works in pretty much every program too, especially Word 2008, which has the annoying habit of not flashing the I-beam cursor sometimes.
MemberOh the luxury of content first! Much of what I do is fixing up translated versions of documents that started in English. Most languages take up more room on the page than English, so by the time the work gets to me, the chance of retaining the original designer's layout has shrunk. Usually the text size and/or leading get the treatment, but other times, they're more relaxed about reducing the size or changing the position of the pictures.
So a plea to all you designers out there: white space is good, not just for aesthetic reasons, but also to allow space for expansion if the document gets translated.
MemberInteresting. The files I have to change are headed
<UNICODE-MAC>
<vsn:5><fset:InDesign-Roman>
and still I have to change the line endings to a Unix-style LF before importing them on a Mac. It took someone ages to work this out, so I suspect there might be some inconsistency within InDesign that means you just have to experiment until it goes right.
MemberInteresting. The files I have to change are headed
<UNICODE-MAC>
<vsn:5><fset:InDesign-Roman>
and still I have to change the line endings to a Unix-style LF before importing them on a Mac. It took someone ages to work this out, so I suspect there might be some inconsistency within InDesign that means you just have to experiment until it goes right.
MemberHad the same thing in CS3 – someone finally worked out that you had to change the line endings to “Unix”. This was despite the fact that the file had never been close to a Unix computer. I used TextWrangler (Mac) to see/change the line endings and which flavour of Unicode encoding.
So, I'd try tinkering with the line endings first.
The settings that worked for me on the Mac are:
Line endings = Unix (LF)
Encoding = Unicode (UTF-16 Little-Endian)
Good luck!
MemberHad the same thing in CS3 – someone finally worked out that you had to change the line endings to “Unix”. This was despite the fact that the file had never been close to a Unix computer. I used TextWrangler (Mac) to see/change the line endings and which flavour of Unicode encoding.
So, I'd try tinkering with the line endings first.
The settings that worked for me on the Mac are:
Line endings = Unix (LF)
Encoding = Unicode (UTF-16 Little-Endian)
Good luck!
MemberBit late to this one, but I tried: creating a file in CS3, with a text box, then opening that file in CS4, typing in “d'entraînement”, export to INX, and then open the INX in CS3.
It worked just fine. Even using Kozuka Mincho Pro.
So, is the French translator doing something strange? Is it a residual Mac/Windows thing where the code pages are different? Not that there's any way I can see to control text encoding in INX files. I'd have expected Unicode throughout anyway.
Can you get the translator to type that word into a fresh CS4 doc, save to INX and see what happens? Also get them to type it into a Word doc, and see if you can place that into a fresh CS3 doc.
Hope you got it fixed anyway.
Chris
MemberBit late to this one, but I tried: creating a file in CS3, with a text box, then opening that file in CS4, typing in “d'entraînement”, export to INX, and then open the INX in CS3.
It worked just fine. Even using Kozuka Mincho Pro.
So, is the French translator doing something strange? Is it a residual Mac/Windows thing where the code pages are different? Not that there's any way I can see to control text encoding in INX files. I'd have expected Unicode throughout anyway.
Can you get the translator to type that word into a fresh CS4 doc, save to INX and see what happens? Also get them to type it into a Word doc, and see if you can place that into a fresh CS3 doc.
Hope you got it fixed anyway.
Chris
-
AuthorPosts