SirPL

In Affinity Designer, is it possible to create a box with various stroke thickness on each side? I need to create a frame around a text that has 1px stroke from all sides, except for the bottom which should be 3px. In addition all corners should be rounded, like this: I created this with HTML/CSS.

Hi @stokerg. Sorry for the delay in response. I saved the music score first as PDF and then imported into Designer. Out of curiosity I decided to export it as SVG instead and here's the code for the tie: <path xmlns="http://www.w3.org/2000/svg" class="TieSegment" stroke="#000000" stroke-width="2.48" stroke-linecap="round" stroke-linejoin="round" fill-rule="evenodd" d="M575.239,423.833 C743.713,470.457 1249.13,470.457 1417.61,423.833 C1249.13,476.409 743.713,476.409 575.239,423.833"/> It's a path made of two Bézier curves. It's not against SVG specification. Full SVG, as exported by music notation software, in the attachment. tie.svg

Designer v2.5.5, Windows 10 x64. I'm working with music sheets. Certain music elements generated by notation software have both fill and stroke. I realized that expanding stroke of long ties (concave line joining two notes) gives odd results. Here's a tie before expansion: And after: I'm also attaching a part of the original score with the tie in question for further inspection. expand_stroke.afpub

But what stopped those people so far from purchasing Affinity? Like what changed for those people? They never heard of Serif and Canva will make the product more recognized? Googling for "Photoshop alternative" gives various Top 10 rankings where Affinity Photo occupies 1st place. To be honest I've never heard of Canva before, even though I can be described as an amateur user. I can venture to say that APhoto has higher recognition than Canva itself. I'm not saying you're wrong, simply that I still don't see a direct benefit for Canva, unless Serif is not fully transparent when stating that "nothing will change for current users".

There's one thing I don't get. What does the Canva has out of this transaction? Like for real, they put 1B $ on the table for just a logo on a splash screen? How Canva profits from this acquisition?

Steps to reproduce: Copy the N'Ko script name written in N'Ko script: ߒߞߏ Paste it in a text frame of a new document Result: Crash If for some reason copying the text from here doesn't cause crash, copy it from the following WIkipedia page: https://en.wikipedia.org/wiki/N'Ko_script Reproducible with Publisher 2.1.1 on Windows 10 Pro 22H2 (compilation 19045.3324)

If I first remove the hyperlink from the outter textbox, then I can remove the "whitespace" hyperlink without crash.

@roundedhexagon Check out the Window menu:

Welcome aboard! First load your data with Window > Data Merge Manager. Then use Window > Reference > Fields panel to insert placeholders in your document. Once you're good with the placeholders use the Manager to generate final document.

How to reproduce crash: Create a textbox with some text. Open Hyperlinks panel from the Window menu. Each text line in APub ends with an white character (possibly a new line character). Highlight it: Having the white character selected create a new hyperlink (i.e. to a webpage) Select the textbox containing the text (and the hyperlink) and create another hyperlink I done steps 1-5 in the attached afpub file. In the Hyperlinks panel select the inner (white character) hyperlink and delete it. Reproducible with Public Release 2.0.0 hyperlink_delete_crash.afpub

The fact there's one convention doesn't mean there's no room for other. And - as I wrote - I'm not expecting to have this implemented with the very next release of Publisher. I'm only providing a context which proves that more flexible approach to Footnotes may be beneficial for some users.

If I still can have two wishes regarding foot/side/end-notes, let me express them: Right now I'm working on a document which has following numbering of footnotes: ... 15, 16, 17, 17bis, 18, 19... (that's because in 2nd edition a new footnote was added and it must not break old references), so I wish Publisher supports that in some way. Also, I wish there were an option to define margins of a footnote and to make them dependent on previous character (i.e. make smaller left margin if the footnote occurs after a punctuation mark): I know, those are very specific cases and I am aware they're very unlikely to be supported right away. But maybe some day...?

I'm facing the same problem, but I'm working with a document which contains hundreds of embedded PDF graphics and it annoys me so much. Hopefully one day somebody adds proper option in properties

Steps to reproduce: Select multiple PDF files in the explorer (at least three) and drop all of them into Designer window to import In the PDF Options window the "Group lines of the text into text frames" is ticked by default. Untick it. Click OK to import the first file Another PDF Options window appears. This time the "Group lines of text..." option is unticked - OK Click OK to import second file. Third PDF Options window appears. In this window "Group lines..." option is automatically ticked again. - Questionable/NOK Designer 1.8.5.703

This is a very specific problem, which many users may never face. But this is an example which Illustrator handles perfectly, but Designer (and Publisher too) fails to handle. Sometimes I edit music sheets and so I need to import PDF with scores. Each score (note) is a glyph of a specially designed font. The typeface has one problem - it does not have whitespace characters. In result the imported PDF is full of nodef glyphs. Apparently it doesn't matter whether during import I uncheck "Favor editable text over fidelity" and "Group lines of text into text frames". Illustrator, on the other hand, produces clean result: PDF file and the music font are attached. Font of the lyrics is copyrighted, but has no matter in this case. ad_te_levavi.pdf GRECILIAE.TTF

Steps to reproduce: Start Publisher Create any new document In Pages panel click on Page 1 Close document (not the app) Result: Duplicate Selected Pages and Delete Selected Pages buttons are active. When pressed Publisher freezes. Reproducible with Publisher 1.8.0.584, Windows x64 Edit: The same happens when in point 3 a Master page is selected - then Clone and Delete master pages buttons are active instead.

EDIT: Just found an other thread with similar issue; the advise to break links seems to work. ------- Hi, I created a new project using Publisher 1.8, so the document is not some conversion from beta or some older version. It contains some linked Designer objects and uses document color pallettes. I saved the .afpub file successfuly, but I am unable to open it again -- the publisher closes right after the file is opened. It's not a crash, but rather a graceful shutdown of the app. I just cleaned cache and all preferences, but the issue persists. Affinity team - please provide a way to share the faulty files privately for further inspection.

On my machine the issue is persistent. May you please check the document I created in 1.8.0.499? What I also found is that the shift is getting bigger as the left column width is increased. test.afpub

Steps to reproduce: Create a new document Create text frame Increase number of columns to 2 Expected result: User should be able to adjust columns' width proportion by dragging the gap between columns Current result: User is able to adjust the proportion, but has to drag and drop some invisible handler which is placed to the left of the gap The drag&drop zone is indicated by the left-right arrow cursor - please check the image:

That's a good point and needs to be unified. Even if it's counterintuitive, the OpenType specification does not restrict enabling super- and subscript at the same time. Each OpenType font has a list of features which order is determined by its author. The specification states that features should be applied one by one according to the order. An OpenType feature can be applied to a whole paragraph, so if some font provides superior variant only for digits and inferior variant only for letters you may want to turn both features on (for some unknown reason ). Also, for those specific features, OpenType specification says clearly: To sum up: using both features is counterintuitive, but not forbidden. According to the specification superior variants main purpose are footnote markers (besides digits also: * † ‡ § ‖) and abbreviations, i.e. latin Mˢˢʳ or french ones:

Fully agree - I apparently did not get the point of your previous post. My apologizes. To compare the terminology used elsewhere: Application Position superscript Position subscript OpenType superscript OpenType subscript InDesign Superscript Subscript Superscript/Superior Subscript/Inferior QuarkXPress Superscript Subscript OpenType > Position > Superscript OpenType > Position > Subscript Scribus Superscript Subscript Superscript (sups) Subscript (subs) So maybe the typography features can be renamed to Superior variants and Inferior variants?

So as for now Published does not support allonges (various size pages) in facing pages mode. The rootcause of your problem is more or less the same as that one:

Can you prepare a new document with some dummy content that reflects your problem? I am not sure if I understand it correctly - such document would definitely help.

Edit: I complelety edited my reply as it sounded rude and that definitely wasn't my intention. I feel the sections clearly distinguish those two features - Positioning and Typography. Publisher's help tries to distinguish between those two, but I must admit - the explanation isn't informative.

The Super- and Subscript buttons turn on typography features that are provided by the font you are using. For what I found if proper OpenType features (namely subs and sups) are not supported then Unicode defined super/subscript glyphs are used. In case of Arial there's only one superscript letter defined - n (Unicode glyph U+207F; for other glyph code points checkout out this post). Hence it's the only modified character. The same applies to subscript. What you want to do is to use superscript positioning instead: Note: if your font supports ordinal suffix (ordn OpenType feature), you may enable it with the button: