Jump to content

Wosven

Members
  • Content Count

    2,415
  • Joined

  • Last visited

Everything posted by Wosven

  1. Thanks! (the last time I wanted to show it to a co-worker, I wasn't able to find it... I tested it when begining with the app, and mostly forget about it. I'll try next time.)
  2. Run them once while APub is runing too so it could detect them.
  3. When you do this (applying those options on 1 of your 2 frames), there's a conflict between styles and different options between frames. On such error in ID, all the text would disappear (all paragraphs staying together in the overflow part since they can't be together in the same frame). How can you have all the paragraphs together in the same frame if it's not of sufficient height to contains them? Prhaps at some point the last valid rule is kept and the other are ignored. Applying this type of rule to a frame don't seems usefull. I would apply rules to specific paragraph styles (mainly because I need standardized styles applied and knowing how they should interact, usually with the same set of rules for headers, different ones for body, etc.). Perhaps APub should handled user's errors in a different way: all text should disappear if you set the rule "keep paragraphs together" when there's not enough room in a frame. But it can be confusing (it happens when I set no-breaking rule to some paragraph in ID by error, and it's always a pain to correct: enlarging the frame, selecting and disabling no-break style, etc.). On your example, the last rule applied seems to be "keep with previous paragraph"+"keep paragraph together" => the last line of the paragraph in Frame_1 run away with the other paragraphs to Frame_2 [edit] I suppose rules are applied one after the other, and this is the result. [/edit]
  4. Using the designer font value is better than a default one that don't take in account th design of the fonts. Some fonts are made for using high leading, other small ones, because they were design with a specific usage in mind. For example, Uncial and similar calligraphies were made for writing few text in a page, needing lot of space between lines and characters to be readable, when blackletters calligraphies were condensed to put lot of text in a page. Fonts today keep on using those rules and needing more or less space, and a generic leading as in Word (120%) is rarey a good setting. For example: on a header of 2-3 lines, they should look/feel together, as one paragraph (if it seems that it's 2 different lines/sentences, decrease the leading).
  5. It should be this way with those setting in your example. Did you only modify localy (using the Paragraph panel) one of your headline (and not the last one), forgetting to update the general Paragraph style?
  6. That's strange since the only "real" style was the "intertitre" one, the body text was set to [none]. (And it was an example to show the headline following the next paragraph, to avoid headline at the bottom of a column, or begining at the bottom of one and ending at the top of the next one. Usually I would play with the text and illustrations to have full columns of text and avoiding headers at the bottom or top of columns.)
  7. Read again my previous post and screenshot (your options are for the wrong paragraph style, your headline = my intertitre) [edit] Unless Abstande mean Headline, but the headline/intertitre was behaving -- following the next paragraph -- for me after setting this line to 1 [/edit]
  8. Once you've downloaded your profile, you only need a right-click and select "install the profile", and restart AD.
  9. Did you add "1" in the last option? Seems to be the needed option to have the text following the other paragraph in the next column, for example.
  10. Optically, it always "feel" smaller or higher than the baseline (because of lighter colour than the black or dark text), I usually correct this decreasing the baseline of the object until it "feels" right and use a special character style if needed.
  11. Or, if you don't need transparency but the colour at 50%, I would put the arrow at 50% transparency, pick the colour with the colour picker, apply it at the arrow and get back the object at 100% opacity.
  12. Hi, First, I would say it's more difficult to add fire and smoke on this image, it would be easier on one taken at night. Perhaps you can find this tutorial helpfull: Few minutes ago, I would have said I don't have in mind images of fire in daylight... and i just remembered Notre-Dame... You'll find a lot of pic about the flames and the smoke searching for this.
  13. You don't have to add font to APub, it will use the installed fonts onyour system, and if it's open and you install another font, it'll tell you soon about this new font. If the font is already installed, APub should reconize it, unless the font on your system is different from the one used for the PDF (or it's possible that the PDF use a different way to name this font, but you should be able to replace the missing fonts when you first open the PDF in APub). Usually Photoshop rasterize fonts when opening a PDF, that's not usefull when we want to modify the text.
  14. I can't remember if by default the applications are installed in our language or in English (at the beginning, it was English, but usually I keep the official releases in English for screenshots and helping if needed in the forum), and the Bêtas in French. In APub, you can have the Base paragraph style (and different Base styles, or paragraph styles) in the languages you need for spellchecking (I don't use Paragraph styles in AD or AP, but you can find a Language > Spelling option in the Character panel). The system/app/styles's language settings are and can be different.
  15. You can have different languages in a document, and by default the "Base" style should be set to your app/system language. (It's what I've got in French).
  16. Did you check the Paragraph style and the option (at the bottom): Decoration? Perhaps you've got a line above by default on you text.
  17. I didn't test a lot, but I don't have good result with French hyphenation. And some parameters are in millimeters, this means that hyphenation is dependant of column width, it would be easier to use percentages for all purpose hyphenation and specific ones (for example, for books I'd rather have at least 1 third of text on the last line, no less, on magazine, no hyphention on the last word and if possible more than 1 word on the last line unless I've got narrow columns, etc.). I hope people who know better will help with some examples as we had for QXP or ID, to better understand and fine tune hyphenation. I'm fond of straightforward options as "(no) hyphenation for capitalized word", "(no) hyphenation for last word"...
  18. Because "image" retains all the data as an embedded file, and you can resize it more than once, it'll use the original image datas. If you rasterize at a smaller size, you won't be able to enlarge it at its original size and get back the original datas, but enlarged pixels that can look ugly.
  19. Interesting to know where the bug come from. I already mentioned this and others bugs when opening some PDFs.
  20. Keep the score to 0 or 1, or there won't be hyphenation.
  21. Hu, you can try with only 7%, it should be enough without massacring the design of the font too much
  22. Everyone is a beginner at some point. When at school there weren't PC or Amiga or Mac for student, we had to learn buying books (it was the beginning, they described all the menus and features without being Bibles, easy to buy and read for the 3 mains apps: QXP, Photoshop & Illustrator). And when we can have a computer and those apps, and better, someone that can give advices, it was better. It's the same today, but there's Internet, forums, video, etc. to learn. It should be easier. But we need to spend time reading documentations if we want to learn a new app.
  23. It's possible with some javascript code and fmbling with SVG's XML. But I had to use inkScape to get more human readable code an simple SVG... In the zip archive, there's a HTML page with a form. There're input for begining and end of SVG code, and the part that's be repeated (128 times here). The script repeat 128 times the code, giving different IDs to each paths, etc., and calculating the growth of the rectangle with the gradient. It was a fun puzzle, and as usual, I suspect it take as much time creating the script as it would take doing the sliders manually But it's more fun. I end up with code for a SVG file containing the 128 sliders, but AD wasn't able to open it properly (only one slider). I had to create 2 SVG files: one with sliders from 1 to 64, one with sliders from 65 to 128. It looks like a bug. Once those SVG files opened in AD, I only had to create slices and export them to PNG, and I used Gimp to import those 128 sliders as layers and export them as GIF. sliders_project.zip
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.