Wosven

For this, you need to use the Basic brushes with pressure curves (you'll be able to save the settings in a style):

Hi, I know it was already improve once, but it's not enough. The overflow red dot (or triangle for flowing to another frame) is only visible depending of the height of the frame: if we zoom out to create and adjust a new frame, it disappears. And the level of zoom needed for it to appear can be important! For example, if I need to flow ±325 footnotes on 250 pages, needing sometimes only 1 line at the bottom, I'll have to zoom in/zoom out 500 times! Second bug with this: it's impossible to find overflow in small frames if the zoom level doesn't allow enough space between the blue nodes of a frame to display the red dot. Looking for overflow with a zoom of 270% on a document isn't a good workflow. While in text mode those indicators should be displayed, and perhaps bigger when zooming out, so it's easier to click on them. They should be shown with other tools too, but smaller.

For sure, but the line composer won't process again all the text, only this modified line and depending of result, try to find a solution. If the new no-break-styled text is longer than the line: it's pushed to the next line (we agree on this). Lines should be reprocessed from the start point of modifications, to the last line that's been modified because of this modification, or the ones following. I didn't check precisely, but I don't think that APub is able yet to reprocess left/right aligned text to try the best combinations to have even lenght lines. This look like APub is applying justification's letter spacing on the text to fit more than the line width. What are your parameters for those? Or perhaps it's a problem with this font, does it happen with other fonts? My "s" is half out too, but I had to apply a lot of "no_break" style here and there to get this result.

@John Rostron, No problem, I didn't think it was so advanced!

Sorry, I tested earlier with the PNG from the link, and only tested with first the green colour and second with the red from matte export. In fact, I never use the Tool Colour Picker but the one on the palette or the modifier key Alt, so I didn't notice this "Apply to selection" option. Checked or not, this behavior will happen with all the apps (AD, AP, APub), when pacing or droping an image in a new file. It will happen with picked colour with the Colour picker Tool, and also when using other tools and selecting a swatch (Pantone or not) or a gradient. Was this happening with older versions like 1.6? I can't remember it, but it can be usefull…

You can copy-paste between InkScape and AD too.

You're not limited to the DPI values in the drop down menu, you can manually enter 1200 or another one before exporting.

It's only happening if you click on the colour use as matte when exporting a transparent PNG to have a PNG without transparent background but a selectable and special colour that is used for the pixels that should be ignored/considered as transparent. That's the same as the use of this green colour to select and delete easily a background on an image when taking picture or filming, the difference is that it's an option and colour you choose while exporting a PNG. When I was talking of switching foreground/background, it was before clicking on the colour, since it's only one of those that modify the entire image's colour, the other one don't.

Another way is to switch the foreground/background colours, (key X). I don't know if there's a foreground and a background colour, but it seems to colorize the picture only when one of them is selected while picking the colour.

Today, you can save a PNG with transparency, but before, and perhaps with other file formats like JPG, there wasn't trasnparency and a trick was to use a special colour (a vibrant and barely use colour like the green above or RVB magenta), and the app would distinguish this colour and use only the parts that aren't this colour. It was used to design skins or set of icons for programs like Winamp, with all the parts in the same file separated by this colour. You only needed to specify the colour as we do with the "matte" option, or use the colour specified in a documentation. It's possible some apps can't read alpha channel and keep on using this. It doesn't explain why AD behave this way when selecting this colour, but why the matte colour is a special one and behave strangely differently. (But I would expect it to not be displayed when opening such a file => transparency as intended instead, and the area covered by this colour to be shown in the alpha channel).

You need to look at the Text styles panel: Here, there's a [no style] for paragraphs and characters styles. That's the ones you want to erase the formatting. In the same panel, you can create text styles, and once you've create your new paragraph style, you'll only have to select another paragraph and click on the paragraph style to apply it.

It's happening because this color is use as "matte" in a paletized PNG, and should represent transparency. If I save a transparent screenshot wiith red as "matte" (or "cache" in French, another localisation problem, this mean nothing here ), and click on it after placing the PNG in a document: [Edit] Oups, the file with "red matte": [/Edit]

Ha! I need more than a keyboard then, it was easier this way than learning how to pronounce it (I just hope it doesn't mean or look like a bad word).

Why before? It will add hyphenation before or after depending of... perhaps when we modify a line, it's recalculating this line, and if there's too much text or enough space for the next word it'll modify accordingly?

That's because "N Ha ynNUe" can't stay on the upper line (it's strange in the first frame that the "e" is out of the column), and I suppose "ynNUe" is too short for hyphenation? I thinks it depen of the line composer, if it calculate again or not the line. I can't have text overflowing like you, but if I add "pink_no-break" style, "des" comme to the upper line (even when it seems there's no place for it!).

You can convert to curves when exporting to PDF: Perhaps resetting the OS font cache and re-installing the fonts will be enough.

You can downgrade or wait, perhaps the dev will come back from holidays and debug the apps and give a new version next week (sorry guys, I hate it too when I come back to work and it seems everything went awry while away ).

Hi @John Rostron Not sure if it can help your test: ligne_complexe.svg ligne.svg losange.svg

If it's a book, the text should be linked, you can specify some headers only begin at the top of the next page. Did you tried pasting in Word? When I try in Libre Office, there's a problem and each paragraph begin on a new line. I don't know why, when I tried with my own document, the 250 pages were nearly perfect but the drops caps that needed adjusting.

It seems the problem occur when using Adobe Reader to convert the PDF to .doc. Copying-pasting from APub to Word or Libre Office would be more logical.

It seems AD can't understand multiple <svg> tags with different positions x and y: <?xml version="1.0" encoding="utf-8"?><svg width="216" height="192" viewBox="0 0 216 192" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"> <svg width="24" height="24" viewBox="0 0 24 24" id="ic_add_location_24px" x="24"><path d="M12 2C8.14 2 5 5.14 5 9c0 5.25 7 13 7 13s7-7.75 7-13c0-3.86-3.14-7-7-7zm4 8h-3v3h-2v-3H8V8h3V5h2v3h3v2z"/></svg> <svg width="24" height="24" viewBox="0 0 24 24" id="ic_beenhere_24px" x="96" y="120"><path d="M19 1H5c-1.1 0-1.99.9-1.99 2L3 15.93c0 .69.35 1.3.88 1.66L12 23l8.11-5.41c.53-.36.88-.97.88-1.66L21 3c0-1.1-.9-2-2-2zm-9 15l-5-5 1.41-1.41L10 13.17l7.59-7.59L19 7l-9 9z"/></svg> <svg width="24" height="24" viewBox="0 0 24 24" id="ic_directions_24px" y="24"><path d="M21.71 11.29l-9-9a.996.996 0 0 0-1.41 0l-9 9a.996.996 0 0 0 0 1.41l9 9c.39.39 1.02.39 1.41 0l9-9a.996.996 0 0 0 0-1.41zM14 14.5V12h-4v3H8v-4c0-.55.45-1 1-1h5V7.5l3.5 3.5-3.5 3.5z"/></svg> <svg width="24" height="24" viewBox="0 0 24 24" id="ic_directions_bike_24px" x="24" y="24"><path d="M15.5 5.5c1.1 0 2-.9 2-2s-.9-2-2-2-2 .9-2 2 .9 2 2 2zM5 12c-2.8 0-5 2.2-5 5s2.2 5 5 5 5-2.2 5-5-2.2-5-5-5zm0 8.5c-1.9 0-3.5-1.6-3.5-3.5s1.6-3.5 3.5-3.5 3.5 1.6 3.5 3.5-1.6 3.5-3.5 3.5zm5.8-10l2.4-2.4.8.8c1.3 1.3 3 2.1 5.1 2.1V9c-1.5 0-2.7-.6-3.6-1.5l-1.9-1.9c-.5-.4-1-.6-1.6-.6s-1.1.2-1.4.6L7.8 8.4c-.4.4-.6.9-.6 1.4 0 .6.2 1.1.6 1.4L11 14v5h2v-6.2l-2.2-2.3zM19 12c-2.8 0-5 2.2-5 5s2.2 5 5 5 5-2.2 5-5-2.2-5-5-5zm0 8.5c-1.9 0-3.5-1.6-3.5-3.5s1.6-3.5 3.5-3.5 3.5 1.6 3.5 3.5-1.6 3.5-3.5 3.5z"/></svg> ... </svg>

Yes, and it's better with references for notes if you need to keep them (they disappear with RTF import). This way, you'll import the styles, (if you already created them in APub, APub will import them again and appends a number, it can be annoying. You'll need to search/replace each Word style by the correct APub one). If you import them in a document with no styles, you'll have to check and correct them, since not all is implemented. You can do some tests with smaller books than the Bible, since without scripting and some bugs,such text will be a real challenge.

Does the problem occur on the area of your leaves image's frame? If so, perhaps it's a problem with transparency.

That's Josh Randall! <3 Damn, another comment one of my young co-worker would need explanations… and I would feel sooooo old

Same as you. For work, I use at work ID, and AD (producing PDF I'll import in ID, or using JPG+path if I need to import a curve) and AP. For files other users will need, I'll use Adobe' app, since I'm the only one testing Affinity products. A PDF version to access the content fast if needed. For personnal use, or everyday notes, texts, etc. I'd rather use good old plain TXT or HTML files produced in my favorite text editor. I can open then on any device and easily when I need, without installing anything. At work, we use ID, export as PDF, and archive all with IDML. In the worst case scenario, I would use some HD PDF to get back images and text if I wasn't able to open the original file and original images (but we use TIFF format, PSD can be opened in other apps… problem would be with .AI files if there's no PDF embedded). When we switched from QXP to ID, we needed a script to convert them, and we kept a Mac with QXD for emergency cases, but today, I only convert 1 QXD file by year, or less…). If one day we switch to full Affinity, it'll be the same: keep at least 1 Adobe licence, everyone else on Affinity apps. For the ones that can't keep a licence, it'll be more difficult, and need planning ahead: exporting IDML (for when APub will be able to import them) or exporting text content to DOC or other formats, exporting PDF of the contents and PDF of the master pages, and why not PDF with examples of each text styles used in a document (one document doesn't always use all at the same time). Using scripts to do part of this is possible in ID. ------------------------------ About the current problem: that's strange, I don't create section in the text, but selecting pages in the panel, it should be selectable and deletable if not palatable