Metalhead
-
Posts
21 -
Joined
-
Last visited
Reputation Activity
-
Metalhead reacted to Thomas Geist in Global Layers (in Publisher)
Just revitalizing this huge thread from the 1.x version since this crucial (but rather complex) feature still has not made it into Publisher. 😢
The original discussion is here.
-
Metalhead got a reaction from Claudio60 in Congratulations! And a fantastic offer at launch.
US: 99 $ = 98,50 €
UK: 89 GBP = 101,50 €
Europe... 119 €
I'm not happy with this regional pricing...
-
Metalhead got a reaction from Getxoblues in Congratulations! And a fantastic offer at launch.
US: 99 $ = 98,50 €
UK: 89 GBP = 101,50 €
Europe... 119 €
I'm not happy with this regional pricing...
-
Metalhead reacted to Robert Laskey in Affinity Publisher Customer Beta - 1.9.0.742
However you only see how it really looks like when you export it. While viewing a passthrough pdf placed on the Publisher Artboard, if there are missing fonts, you will get a wrong font representation (replacement) as if you are editing it. Correct viewing as in Indesign will be much appreciated.
-
Metalhead reacted to cpoh in Word count in Affinity Publisher
I too need this on a daily basis and am missing this feature a lot while transferring from InDesign to AP.
My use case is layouting a small newspaper and getting the texts from about 6 different people.
I have to go on a layout after content principle. This means the writers don't care much about the correct length of their articles and after the first layout run i do have to tell them "this could be xx characters longer" or "this have to be 234 characters shorter" etc.
For the last years there is the handy "info tool" in indesign which i use for:
- See the total count of characters in the text's columns (linked)
- See the count of characters in marked text
- see the count of overflowing text (that's for me the most helpful part)
As stated above, this whole counting is a feature in almost every software that deals with text and should be in AP as well.
-
Metalhead reacted to postmadesign in Tables are a problem in Publisher!
I am sorry to be negative on this forum, as in general I like most of the things in the Affinity Suite, but the tables function in Publisher just leaves way to much to be desired. I have commented on this issue before, but besides some small bug fixes it is still generally the same deal. I have a project I am working on that includes many specifically formatted tables which occur many times in the report, each with different data, but the same setup. I started this recurring project in Indesign 2 years ago and was hoping to transfer it to Publisher, as I still work with an old Indesign version and it is not very smooth. Publisher is much smoother overall. However I cannot get the tables to work as they do in Indesign, however way I try. I have several problems.
First thing is that it is very hard to get the column widths as i want them. It works very different from indesign and I just find it very frustrating. When I create a table with a specific nr. of rows and columns the entire table has a specific width and each column has a uniform width. Now I want to make specific column to right of the one I widened gets squished... When I try instead to first change the width of the right most column, the table as a whole changes size...? I have no idea why this makes any sense at all. I have been working with tables in indesign for years, so perhaps I just don't understand what Publisher is doing? The only wy to archieve the result I want is to drag the width of the table wider then I will use it in the end, and then change the width of each column from left to right. But this is very inflexible, and if I want to change the width of a column later it will always affect the other columns. I find this highly frustrating.
The other big problem is the text formatting within the table. I have use several text styles within the same table, so I have created a basic table in the way I want it to look. Now I will paste the data from Excel into the table, but this is where the problem occurs: All the pasted text will have the style of the upper left most cell. It completely ignores all the local formatting I have done. This creates a lot of unnecesary work to adjust the table the way I want it to be again. The only partial solution was to use the table style dialog and create a separate style for each table with text style assigned to the right cell. So when I have my table defined in this way I can paste the data and apply the table style. But this is quite unintuitive and gives me new problems with regards to lines. If I have have certain cells with and certain cells without border lines, it will not retain these local formatting. I have no idea why these things have to be so complicated.
It is these things that keep me from using Publisher for this project, which is a great shame. Can you tell me if you are working on improving the tables in the near future?
-
Metalhead reacted to muelli75 in PDF Import font issues remain
It would be nice, if AP dont touch the content of a PDF/EPS. Just import as it is.
Im wondering why this isnt possible.
I would like to work with AP instead of A InD, but this PDF-"Feature" is deadly for our company.
We have to use PDFs from our customers in 80% of our work. With every occurrence of an PDF we must fear for the result.
Please add a "leave untouched"-function, as requested a year ago.
Hopefully ... Martin
-
Metalhead reacted to Steaming T in Affinity Publisher for macOS - 1.8.1 (was 1.8.0)
Great update! The new Preflight option has already been very useful. But I am still missing global layers as in InDesign. I have documents with different versions of text and graphics. Without global layers in Publisher I am forced to continue using InDesign for these docs. So please: Global Layers!!!
-
Metalhead got a reaction from deeds in How to change angle in Gradient Stroke?
Thanks god, I'm not the only one.
This.
First I think this behavior is a bug in Publisher, not a feature. It makes no sense at all.
-
Metalhead reacted to deeds in How to change angle in Gradient Stroke?
This would be miles better if the Gradient tool recognised that the user was in stroke editing mode and editing a stroke rather than always defaulting to Fill and needing to be changed to stroke in order to edit the stroke's gradient. Perhaps renaming the tool to just "gradient" rather than fill gradient would help discoverability, too.
-
Metalhead got a reaction from Patrick Connor in Reporting Localisation Issues in Mac Publisher beta #384 (#376 #371)
Inconsistency: it has to be 12,5 – not 12.5
-
Metalhead got a reaction from Patrick Connor in Reporting Localisation Issues in Mac Publisher beta #384 (#376 #371)
My favorite topic, keyboard shortcuts - now Mac OSX edition. ;)
Comma and semicolon are on the same button... so "Show Guides" does not work and open "Preferences". "Show Grid" (cmd + ') does nothing.
Angle brackets are one the same button.
So cmd + > and cmd + < are basically the same. ;)
Right and left square bracket:
ALT + 5 = [
ALT + 6 = ]
There is no way to get square brackets to work as a keyboard shortcut.
-
Metalhead got a reaction from Patrick Connor in Reporting Localisation Issues in Windows Publisher Beta #384 (#376 #371)
The textframe window opens still too narrow by default.
-
Metalhead got a reaction from Patrick Connor in Reporting Localisation Issues in Windows Publisher Beta #305 - #337
Endkunden-Lizenzvereinbarung - a looooooong beautiful word only the German language can create
And whatever the unreadable small text about Pantone have to say...
The use of "Zyan" instead of "Cyan" is very uncommon.
Missing translations:
Maybe "Teiltonung" is better
Window size - it's possible to make a window smaller than needed:
Some words are too long (and one translation is missing):
Keyboard shortcuts - as I mentioned two or three times before: < > | [ ] are never gonna work, no matter if I use a PC or a Mac. Please get yourself a German keyboard and test the shortcuts or "borrow" the shortcuts from InDesign...
-
Metalhead got a reaction from Patrick Connor in Reporting localisation issues in Windows Publisher beta #292 & 293
As I said at the last localisation thread, those keyboard shortcuts won't work.
A German keyboard look like this:
You have to change shortcuts with <, >, [ and ]
Not translated yet:
