Forum Replies Created
-
AuthorPosts
-
Chris Thompson
MemberWhere are you saving to?
I seem to recall a similar problem (probably around CS3 days) saving direct to a mounted Windows server drive from a Mac. Something to do with the server settings, but I can’t remember what.Chris.
MemberDo you mean you want to import the text (auto-flow) into threaded text frames, one per page, and then unthread the text frames before any later edits? With the result that any text added on page 4 has no effect on page 5 et seq, and if there’s too much, it just shows overset text on page 4?
If so, there’s help here:
https://creativepro.com/splitting-up-threaded-stories-into-separate-frames.phpMaybe a change of topic title might bring some more answers – the text is being imported “correctly” after all, but it seems like you want to subsequently break the links between threaded text frames.
Good luck,
ChrisMemberIs the text set to align to baseline grid? Would that help? Then if the text wrap padding is set to be the same above and below, that ought to work out right?
Chris.
MemberWould adding a “discretionary line break” after each comma help – see also
https://creativepro.com/discretionary-line-breaks.php
and (part way down)
https://helpx.adobe.com/indesign/using/editing-text.htmlChris.
March 9, 2015 at 8:21 am in reply to: GREP:Do not break words that begin with a capital and preceded by an apostrophe #73841MemberI’d be very surprised if you’re the first person to be affected by this, but I can’t find anything else about it with a quick google.
Let us know if you find anything else useful, please!Chris.
March 9, 2015 at 5:11 am in reply to: GREP:Do not break words that begin with a capital and preceded by an apostrophe #73830MemberAh I understand now.
Disregard my other reply!And I can also replicate your behaviour, even with a “normal” apostrophe before Université – it still hyphenates, when the option is set to not hyphenate capitalised words.
March 9, 2015 at 5:10 am in reply to: GREP:Do not break words that begin with a capital and preceded by an apostrophe #73829MemberIf it’s a closing quotation mark, would that be the reason for the “false” hyphenation? It thinks that the end of a quotation is a valid point at which to break the line.
Is that even the correct character to use in this situation?Chris.
March 9, 2015 at 2:53 am in reply to: GREP:Do not break words that begin with a capital and preceded by an apostrophe #73826MemberWhen this occurs, are the French words set as French in the Character panel (or in a style)?
One would expect the French hyphenation dictionary to work correctly, but you might expect a non-French hyphenation dictionary to make mistakes.I tried out a bunch of text which included l’Université, and I could not cause it to hyphenate at the apostrophe, even with a text box that was only a few letters wide. The smallest hyphenation I got was:
…
L’Uni-
versi-
té
…Also, it would not hyphenate “d’une” at all.
Good luck,
Chris.MemberEek.
One thing that might help a little:
copy-paste the Excel sheets into Word, where it’s easier to manipulate the tables by merging cells together so that you can copy a story in one action instead of several (e.g. for your list of bullet points, or a whole story).Do the Excel files contain both source and target text? If so, you might possibly be able to use a translator’s CAT tool to match the text segments of the IDML output from the source InDesign files to a translation memory prepared from the Excel sheets. I’ve never tried it, but it’s a possibility. It would eliminate the copy-pasting, and just leave you with layout adjustments to do from the re-imported translated IDML files.
Sorry, I’ve no other useful suggestions at this stage of the process.
I wouldn’t have done it that way back at the start, but of course you don’t have that luxury.Good luck,
Chris.MemberDo you mean for a total of 6000+ brochures?
And are there any existing links between the source language InDesign brochures and the Excel sheets?
What were you planning to do from the Excel sheets – surely not copy-paste into the InDesign stories?
That sounds like the ultimate nightmare workflow to be honest.Chris.
MemberThe PDF linked in the creativepro article in the previous post is a few years out of date (undated in the document, but 2004 according to the PDF file properties).
It doesn’t take into account the availability of plugins to allow the use of the World-Ready and Japanese para composers in “standard” versions of InDesign.MemberIdeally, your translators will have CAT tools (computer-aided translation).
If they do, then you can export IDML from the source document, then they can translate and send back an IDML in the target language. Also send them a PDF so they can see the visual context of the words.
If the translators don’t have CAT tools, you may end up copy-pasting their words, which is a good way of making errors.You will need to adjust the result, as the text will be different lengths to the original, the fonts may not be available in the target language, graphics may not be appropriate for the target audience, etc etc.
And get the translators to look at the final result if you don’t know the target language.
Good luck,
Chris.MemberThe OP is asking if the use of tables in InDesign is viewed in the same way that tables are disliked/not permitted (interdit) in web design.
I’d say that:
1. tables are a very useful tool for page layout / les tableaux me semblent très utiles pour le mis en page.
2. why would you ban them? / pourquoi les interdire?Regards/cordialement
Chris.
MemberHow about a table with invisible borders, and then apply different styles to the 2 columns? Easy to adjust afterwards, and easy if you happen to need a heading longer than your 1.25 inch which would otherwise wrap things awkwardly.
Or did I misunderstand your description?Chris.
December 23, 2014 at 1:46 am in reply to: I need Indesign macro to export and import alt text. #72334MemberHmm, interesting.
I’ve just created a test file with alt text on and object, and exported to IDML. I then opened up the IDML (which is just a zipped archive of XML files), to look through with a text editor.
The alt text IS in fact in the IDML file, under Spreads.In my very simple sample it was in a file called Spread_uc3.xml, and in a section of XML like this:
<ObjectExportOption AltTextSourceType=”SourceCustom” ActualTextSourceType=”SourceXMLStructure” CustomAltText=”Alt text added in the dialog” CustomActualText=”$ID/” ApplyTagType=”TagFromStructure” CustomImageConversion=”false” ImageConversionType=”JPEG” CustomImageSizeOption=”SizeRelativeToPageWidth” ImageExportResolution=”Ppi300″ GIFOptionsPalette=”AdaptivePalette” GIFOptionsInterlaced=”true” JPEGOptionsQuality=”High” JPEGOptionsFormat=”BaselineEncoding” ImageAlignment=”AlignLeft” ImageSpaceBefore=”0″ ImageSpaceAfter=”0″ UseImagePageBreak=”false” ImagePageBreak=”PageBreakBefore” CustomImageAlignment=”false” SpaceUnit=”CssPixel” CustomLayout=”false” CustomLayoutType=”AlignmentAndSpacing”>
The alt text that I added is “Alt text added in the dialog” which appears under CustomAltText=”Alt text added in the dialog”
So it would appear that the filters used by our CAT tools aren’t picking this up as potentially-translatable text.
I wonder if the open source OmegaT with those Okapi filters would be configurable to do this? Sorry, but I don’t have the time or tech knowledge to test this.
Good luck,
Chris -
AuthorPosts