Thomas Ganter
-
Posts
23 -
Joined
-
Last visited
Posts posted by Thomas Ganter
-
-
Haha – and us AppStore users will have to wait until … when exactly?
-
9 hours ago, Wosven said:
the app can import fonts if they are in a special folder named "Document fonts" and placed with the document
d’accord.
I was thinking about this as well – there's the PRO and CON to weigh with Assets.
That approach would be obvious (and should be supported in parallel!) but then there is always the chance of just missing to send those documents along when sharing the file. Also, there is always the Font license issue -- having the fonts in plain sight makes piracy so much easier (don't want to use the word „encourages“ though).
Having fonts embedded could be a one-way route (i. e. not make them "exportable" again) and all rights are maintained (assuming you have a license for the font in the first place).
But, for the avoidance of doubt, a "document fonts" folder should be supported as well.
-
Hello world!
I do publishing as a hobby. Pro bono as a volunteer for parishes and communities.
But as a result of that I have many different established "identities" to support, all with their own Colour Schemes, Layouts and typography.
Colour Schemes and Layouts I can manage using Paletes, as can I typography -- but not associated fonts.
Current solution is to either have all fonts always installed on the system.
This is a mess, and it slows down my system and makes the font dialogs unwieldy.
Alternative is using a font manager.
This is also a mess, since none integrates well with Publisher and it is a painful manual exercise every time.
Also, both solutions are not "portable" in the sense of "trans-portable".
Thus, after long intro, here my proposal:
Make Fonts "importable" like any other asset.
Just import document fonts and make Publisher (and the other Affinity Studio applications for that matter) retain the font files in the document bundle so they are sent along onto other platforms. And they are automatically enabled when the document is open. And automagically do not show up anywhere outside the document.
Clean, simple solution.
Transparent to the user.
Failproof.
Robust.
Intuitive.
Community -- what do you think?
Greetings,
--Thomas
-
49 minutes ago, elmonopascual said:
There is a studio panel Styles
Yes, I know about this Studio panel, but never understood it's purpose because the "styles" in there are immutable.
And they are way uuuuggggllllyyyy.
IMHO, that is.
-
As found out in this question over in the Q&A forum, Publisher does not support an equivalent to what InDesign calls "Object styles".
However, to produce quality output that is consistent, this is a mandatory must-have -- styling would otherwise be so much more tedious and error-prone.
- U. Dinser, Wosven and elmonopascual
-
2
-
1
-
On 8/27/2019 at 9:51 AM, Callum said:
There is no way to change a style and have the edits you made appear on all existing cases of that style I'm afraid.
OK, then, please make this a very urgent feature request.
This is mandatory if one wants to create a publication with a consistent look.
UPDATE: Feature Request posted here.
-
Hello world,
In laying out a newsletter I have a load of elements that should look “the same“, i.e. consistent.
Like the Layer Effects (shadow, glow, blurr), or the stroke thickness/style of a Frame or Box.
So that, once I decide that a 10px shadow is too bold, I only would need to change one style instead of 30-odd individual boxes.
In InDesign these were ObjectStyles, and they were powerful …
in Affinity Publisher I fail to understand how the same could be achieved.
Please advise/ help.
Thanks!
--Thomas
-
Hi,
maybe this is also a misunderstanding becaue I am so much InDesign-indoctrinated, but I have problems managing colors.
I have created a color swatch palette for the CI colors of our parish and use that to assign to elements in Publisher (text, frames, fills, stokes, ...).
Now, in InDesign, once I change the swatch all objects that use the swatch will be automatically updated.
In Publisher, this does not work.
So, either my expected behaviour is wrong (user defect).
Or the expectation is justified and I'm too dumb to correctly use it (user error).
Or it is indeed a bug.
Which one is it?
--Thomas
-
11 hours ago, thomaso said:
Sounds magic but works.
Indeed!
Thanks!
-
On 7/18/2019 at 11:36 AM, stokerg said:
will warn you about hidden text
just for clarification (because I get these warnings exery single time):
How would I *find* these instances of hidden text?
Especially in a large document with a lot of frames ...
-
7 hours ago, Dave Harris said:
I'm sorry you've been having this problem. It is triggered by the interaction between the drop cap, text flow and the text wrap. I've attached an example file that demonstrates it. This is about the simplest document I could make. In your file the key text wrap was around the heading frame that flows into the main frame. We do have a fix for this internally, but it probably won't be included now until 1.8. In the meantime, a workaround for this type of layout is to resize the main text frame so it doesn't overlap the object that has the text wrap.
Hi Dave,
thanks for the update -- and briliant that you have a fix (assuming 1.8 is not too far into the future).
I *think* have have worked around all these issues (found a few more along the way but was to pressed to post here -- maybe I will once I have reproduced it).
Now I need to just carefully review all 48 pages visually to ensure no unwanted side effects allear.
Greetings,
--Thomas
-
1 hour ago, thomaso said:
For inspection: Could you upload the document, possibly only a few pages and not embedded images, and/or with different text in case yours should not become public yet?
Hi thomaso, I did upload the file and all the fonts used (without the graphics) for Jon P from this forum a few days ago.
I am happy to re-upload the current version of the file if you send me a dropbox link.
This is a parish newsletter, so no secret content or anything.
-
Some more experimentation here, and it seems to be driven by
a) either the fact that I use text frames from the master page, or
b) re-flowing text around another, linked text frame (heading text frame accross the full spread, copy text frame being reflown)
See Video for a demonstration.
-
19 hours ago, Jon P said:
wouldn't expect it to prevent you from finishing the project?
OK, I have to revert my previous statement.
This now is a production-blocker for me.
See the attached video for a demonstration, this is utter ridiculous and I fail to see how I would be able to work around this other than *manually* flowing text (but then I can also switch to PowerPoint for my Publishing needs – there would be not much difference).
Please *urgently* help.
-
26 minutes ago, Jon P said:
That being said, this bug can be worked around so I wouldn't expect it to prevent you from finishing the project? Unless I've missed something?
Hi Jon P,
no, I can simply move the superfluous Text Frames out of the Document and onto the Canvas – but the lagging feat of course is that there is some lingering duplication in the document that all scrutiny and careful manual/ visual proofreading will not spot.
It's not like export is broken (at least I hope not ... *grin*).
Thanks and greetings,
--Thomas
-
1 hour ago, MickRose said:
You could create 2 master pages. apply both to page. Then just move the layers.
WOW -- AWESOME.
I was not aware of this, maybe I skipped this in the documentation (TLDR'd over it).
And my brain obviously is still too much hard-wired to think how "old" Publishing Apps work (a long legacy of InDesign and a short detour to Scribus here) …
Will immediately give it a try.
Thanks for the help!
-
2 hours ago, Jon P said:
It seems to be due to the picture, but I can't see exactly why, but either way it looks like a bug so I've logged it.
Thanks
Thanks – will I get notified when this is fixed in the next beta, or must I scrape through release notes?
Is there a Bug ID I can look for?
As mentioned in the Video -- I need to ship the finished product to the printer very latest on August 25th, and for this Issue we made the bet on Affinity Publisher.
Thanks once more,
--Thomas
-
Hello world,
I seem unable to place page content in between the elements of the master Page, i.e. have some Master Page layer always on top of Page elements/layers, and other Master Page layer always below Page elements/layers.
This is easily achieved in e.g. InDesign (and Scribus for that matter), so I am curious whether I am doing something utterly wrong or whether this is a missing feature (which I hereby request).
Greetings,
--Thomas
-
2 hours ago, Jon P said:
Can you upload the document here and i'll take a look.
Thanks
OK, just posted another Video on the other topic, and uploaded Document plus Fonts (all open Source License) to your DropBox).
-
2 hours ago, Jon P said:
I've responded to your other thread, if you want to upload the file to the link there I'll take a look at this as well.
Hi Jon P,
no, this thread just works fine as long as I get responses.
So, this is a recording demonstrating the very same behaviour with the beta I just downloaded.
There is also nothing secret about the document, if it helps I'll upload it here (or, can I DM it to you?) if I gete instructions on how to package/ upload a document with Fonts and all?
Greetings,
--Thomas
-
Hello world,
My last week's Bug is not yet answered upon, today I stumbled accross an even weirder behaviour which I captured on Video.
AP 1.7.1 duplicated a large chunk of text at the very bottomn of my text frames and reflows it into the next frame if I create one.
This is reproducible on frames where it appears, and no changing the text / editing / re-formatting that i do removes this problem.The original and duplicated text are in symc, If I change it it changes in both frames …
Please help – text management should be more relilable in an Publisher …
Thanks,
--Thomas
-
I reproducibly see spellcheck underlines one line off when using baseline grid and paragraph spacing (see green arrows in attached image).
Also in certain case the last line of text is repeated into the next column (only if it is the really last line) -- see big red arrow in attached image.
Publisher File is too large to attach but I could provide a download link if of interest.
Seems not to be fixed in 1.7.2 (is there a beta BTW?) since it is not mentioned in the 1.7.2 post on this page.
Please adivse.
Thanks!
--Thomas
No History or Undo
in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
Posted
OK, ITM German App Store is updated as well … Thanks though.