Dave Harris
-
Posts
2,454 -
Joined
-
Last visited
Everything posted by Dave Harris
-
I'm afraid not. PDF doesn't have a notion of grouping purely for organisation. -
Yes, it will be added to the documentation soon.
-
There is more on this here.
-
Export for PDF is broken?
Dave Harris replied to Pixelplucker's topic in [ARCHIVE] Designer beta on Windows threads
Do you have File > Export > PDF > More > Allow advanced features checked? Unchecking it produces simpler PDFs which may help Corel to load them. -
"+10" is too ambiguous. It might might 10 of the default units. You can use "x +10" if you prefer. x, y, w, h refer to the current position and size.
-
Updates for the paid applications will be free until 2.0. We hope to implement all the features on the roadmap before then, however long that takes.
-
Unchecking the Set viewBox option should prevent that.
-
Thanks. It looks like they aren't self-contained EPS. They use some resources with names like Adobe_packedarray. The library we use for importing EPS doesn't have definitions of them. We'll have a look to see if we can do anything about this, but no promises. We can export in EPS, which may work.
-
The export failure should be fixed in the next beta, hopefully later today.
-
Yes, it's a very popular request.
-
Your two example lines look the same to me. Have you tried changing File > Export SVG > More > Set viewBox ?
-
Thanks. I can reproduce the export failure with that.
-
Affinity should read either the PDF or the EPS stream from AI files already. Do you have an example of an old-style EPS-like AI that won't load, so we can take a look?
-
Could you attach a simple Designer file that does not export, so we can take a look at that problem? I suspect there may not be much we can do to make the ones that do export, more palatable to your cutting software.
-
No. The After space is independent of the text height. However, both have default values, which both happen to be 12pt as shipped. At least for Frame text. Art text has a default of 0pt for After. This is because Art text doesn't line-wrap, so people tend to use hard line breaks, and wouldn't want a gap after every line. Frame text does line-wrap. It's better to use After space to separate paragraphs than to put a blank line. Of course, you can also use a first line indent to mark where new paragraphs start, in which case you might not want the After space. We had to pick one scheme or another for our defaults and we went with After space rather than left indents. I think it's the more common style - it's what we naturally use in this forum, for example. Feel free to change it for your documents. I describe above how you can set new defaults.
-
Have you tried the 1.5 beta? Some work was done on embedded documents so they should usually export as vectors in 1.5.
-
Switch to Affinity from DrawPlus?
Dave Harris replied to jlittle's topic in [ARCHIVE] Designer beta on Windows threads
See https://forum.affinity.serif.com/index.php?/topic/22334-affinity-designer-is-not-serif-drawplus/ for more on this. -
We don't currently support text avoidance areas, but we do support shaped frames. If you create a rectangle, use Layer > Convert to Curves, then reshape the curves so its interior avoids the image, then use Layer > Convert to Text Frame and enter the text. You can continue reshaping the frame with the Node tool.
-
If you change it, it should become the default for new text objects in that document. If you then use Edit > Defaults > Save, it should become the default for new documents, too. That will save all the object defaults: text ones like font, and also shape ones like stroke weight and fill.
-
Thanks for the feedback. We don't currently support auto-hyphenation. That's something we'll have to add for Publisher. In the mean time you can use soft hyphens to hyphenate manually. We have several ways of setting paragraph leading. If you click the leading popup, the top few entries should be Default, Exactly, % Height, At Least, Multiple. Which of these is selected affects how what you type into the box is interpreted. When the displayed value is in brackets, it means it's a calculated value. For example, set Exactly and 12pt, and the display will show 12pt. Set % Height and 100%, and the display will show (12pt), because 100% of a 12pt font is 12pt. That's how it should work. I'm surprised to see the 1pt displayed for what does not look like 1pt leading. That's probably a bug - it looks like this is the Windows version and it may be getting the units wrong. Can you remember what you typed to get it into that state? Which items are ticked in the popup?
-
Make sure Preferences > General > Import PSD as text rather than bitmap is checked. This is an option because we can't guarantee our text engine will flow the text the same as Photoshop's.
-
And to scale Frame text, use the extra handle at bottom right of the selection box.
-
We aim to have the same kind of consistency across the Affinity range (Designer, Photo, Publisher) as we have across the Plus range. Actually more, because all the Affinity apps share same document format and much of their code. Being able to open an Affinity Designer document in Affinity Photo and be able to work on it with the same UI is very important to us. However, Affinity is a different suite to Plus, not an extension of it, and having a clean break is part of what enables us to innovate and make Affinity the best we can.
-
[Multi] RTL language text support
Dave Harris replied to lungful's topic in Feedback for the V1 Affinity Suite of Products
We plan to add r2l scripts eventually, but not for a long while. Sorry. The app already supports contextual alternates and much more. Have you seen the Text > Show Typography panel? Inserting a glyph from a font is something we plan to add. The languages in the Character panel are currently those for spelling, and depend on what dictionaries are available. However, that language is also used to select OpenTyp features, and will affect hyphenation when we implement that. Are you wanting more spelling languages, or are you wanting to set OpenType to a language even if you don't have its spelling dictionary? -
We do support tabstops, via a section in the middle of the Paragraph panel. That will let you set a numeric position, with alignment options. We don't currently have a proper text ruler, but it's something we will need for Publisher and then I expect the other apps will inherit it.
