Hangman

Hi @Dan C, It is indeed, no issues with Monterey using either method, they appear to have effectively placed the scrollbar outside the text selection area in Sonoma when it appears within the text selection area on Monterey, though that may just be a visual change only...

Could you cite an example scenario...

Hi @DWright, You can test the version I created if it helps which demonstrates the same issue... Placed Artboards.zip

Hi @Rufus Reade, As @Alfred mentions, you are actually editing the PDF, not your original Publisher file which is why you see the text issues and can no longer place images, use text wrap or change your text boxes. If you re-open the original Publisher document all should be back to normal...

I raised the same question in the original thread but thinking about it further I can see why there is a need for both eye buttons...

Hi @Dan C, Many thanks for bumping...

Hi @Rufus Reade and welcome to the forums, This sounds as though you've opened and are attempting to edit the PDF document in Publisher rather than the original Publisher file itself, is that the case? When exporting your file to PDF uncheck the Subset Fonts checkbox just below the Embed Fonts Dropdown in the Advanced section and see if that maintains your ligatures correctly when the PDF is opened in Publisher...

Hi @Jonopen, I don't know if there is an issue with either Sonoma and/or Apple Silicon but this is working as expected with Monterey on Intel... The one thing that isn't working is Page Up and Page Down to navigate to the next 'page' of the font list, this affects the font menus in the Context toolbar, Character panel and Glyph browser but works in the Text Styles font menu though I believe this specific issue is already logged... Glyph Browser.mp4

Hallo @Zotti, Können Sie ein Beispieldokument oder sogar eine Beispielseite des Dokuments hochladen, das das Problem aufzeigt, damit wir einen Blick darauf werfen können? Dies sollte zu einer schnelleren Lösung führen, anstatt dass jeder rät, was das Problem verursachen könnte ... ____________________________________ Are you able to upload a sample document or even a sample page from the document exhibiting the issue so we can take a look? It should lead to a quicker resolution rather than everyone guessing as to what may be causing the problem...

Hallo @Zotti und willkommen im Forum, Könnten Sie einige zusätzliche Informationen bereitstellen, z. B. Wie passen Sie Ihren Zeilenabstand über die Option „Zeilenabstand“ im Absatzbedienfeld oder die Option „Zeilenabstand überschreiben“ im Zeichenbedienfeld an? Ist in Ihrem Dokument ein Grundlinienraster aktiviert? Was passiert, wenn Sie versuchen, den Zeilenabstand anzupassen? ___________________________________________ Hallo @Zotti and welcome to the forums, Could you provide some additional information, e.g., How are you adjusting your line spacing, via the Leading option in the Paragraph panel or the Leading Override option in the Character panel? Do you have a Baseline Grid enabled in your document? What happens when you try to adjust the line spacing?

Hi @Carolina Illanes and another warm welcome to the forums, Could you perhaps provide a little more information in terms of what you want to achieve... You can certainly copy text from an Excel Spreadsheet and paste it as unformatted text in Publisher but the text wouldn't have any direct link back to your spreadsheet so changes made to the spreadsheet wouldn't be reflected in your Publisher document... Publisher does have a Data Merge feature which would link back to your spreadsheet and reflect any changes made but each row and/or column of text would appear effectively in a cell in Publisher though you can still determine the layout of the content so it doesn't have to be a rigid table format, e.g., you could use Data Merge to create Business Card artwork with N-Up per page... Note: Data Merge is an Affinity Publisher option so not available in Affinity Designer or Photo. If you are able to let us know what you are attempting to do we can hopefully, provide some alternative options for you. You can also download a trial of the Affinity apps from the Serif website if you want to try them out to see if they meet your needs.

I'm not sure of the end goal here other than joining the respective nodes and I appreciate that you've deliberately used square caps for demonstration purposes but based on your screen recording alone, would changing these to butt or round caps (depending on your preference), aligning the nodes and then merging the layers not achieve the same end goal where you have all your tree branches as a single layer? Edit: @MEB beat me to it... Tree.mp4

Hi @nemoDreamer and welcome to the forums, This looks like a bug... Balanced strokes up to and including 2.5 pt are being exported as unbalanced strokes Balanced strokes above 2.5 pt are being exported as expanded strokes My understanding is that all balanced strokes should be exported as expanded strokes on export to PDF.

Bonjour @Delphine34140, Portable Network Graphics (PNG, prononcé officiellement /pɪŋ/ PING, prononcé familièrement /ˌpiːɛnˈdʒiː/ PEE-en-JEE) est un format de fichier graphique raster qui prend en charge la compression de données sans perte. PNG a été développé comme un remplacement amélioré et non breveté du Graphics Interchange Format (GIF) - officieusement, les initiales PNG signifiaient l'acronyme récursif « PNG n'est pas GIF ». PNG prend en charge les images basées sur une palette (avec des palettes de couleurs RVB 24 bits ou RVBA 32 bits), les images en niveaux de gris (avec ou sans canal alpha pour la transparence) et les images RVB ou RVBA en couleur sans palette. Le groupe de travail PNG a conçu le format pour le transfert d'images sur Internet, et non pour des graphiques imprimés de qualité professionnelle ; par conséquent, les espaces colorimétriques non RVB tels que CMJN ne sont pas pris en charge. Un fichier PNG contient une seule image dans une structure extensible de morceaux, codant les pixels de base et d'autres informations telles que des commentaires textuels et des contrôles d'intégrité documentés dans la RFC 2083. _____________________________________________ Portable Network Graphics (PNG, officially pronounced /pɪŋ/ PING, colloquially pronounced /ˌpiːɛnˈdʒiː/ PEE-en-JEE) is a raster-graphics file format that supports lossless data compression. PNG was developed as an improved, non-patented replacement for Graphics Interchange Format (GIF)—unofficially, the initials PNG stood for the recursive acronym "PNG's not GIF". PNG supports palette-based images (with palettes of 24-bit RGB or 32-bit RGBA colours), grayscale images (with or without an alpha channel for transparency), and full-color non-palette-based RGB or RGBA images. The PNG working group designed the format for transferring images on the Internet, not for professional-quality print graphics; therefore, non-RGB colour spaces such as CMYK are not supported. A PNG file contains a single image in an extensible structure of chunks, encoding the basic pixels and other information such as textual comments and integrity checks documented in RFC 2083.

Hi @stokerg, Are you able to clarify whether the requirement for an abbreviation to be added to the Abbreviation Settings to prevent a word from being capitalised after the use of a full stop followed by a comma is expected behaviour (see three posts up) or whether this is effectively the issue logged under AF-2340 with a view to this behaviour being changed?

I'm unsure whether this would be considered to be by design or should be logged as a potential bug or an improvement... Switching between the Wheel and Slider Colour Panel Models will display Hex values in Base 16 when the Wheel is displayed with no option to change this but as Percentage values when the RGB Hex sliders are displayed if the document has previously set the RGB slider values to be displayed using percentages in the Colour Panel Preferences... When displaying the RGB Hex sliders it is not possible to switch from Percentages back to 8-bit or 16-bit because the option isn't available which means the Hex Values displayed can initially appear to be incorrect (despite being correct) because: The Hex value displayed in the RGB Hex Sliders differs from the Hex Value displayed in the Wheel because the former displays the values as percentages, the latter in Base 16 It's not possible to change the RGB Hex slider values back to Base 16 without first reverting to the RGB sliders Questions Should both the Colour Wheel and Sliders adopt a uniform display method, i.e., Base 16 or Percentage Should the option to switch from Percentage back to 8-bit or 16-bit be available when displaying the RGB Hex Sliders

Good point... It appears that so long as you have an abbreviation set for the relevant term then Publisher doesn't capitalise the following word when followed by a full stop or a full stop and comma... Publisher has etc. as a default abbreviation and subsequently, I don't see the issue @MikeTO sees, i.e., when I type either apples, etc. and or apples, etc., and Publisher doesn't capitalise 'and'... If I delete the etc. abbreviation when typing either apples, etc. and or apples, etc., and Publisher will capitalise 'and' if I type a space after the word 'and' but it doesn't capitalise 'and' if I hit return with no space after the word 'and'... So unless the abbreviation is included the word typed following both a full stop or a full stop followed by a comma will be capitalised... It appears that the abbreviation dictionary automatically considers a comma after a full stop in the same vein as a full stop on its own, though I'm unsure if that is the intended behaviour... The same is true of e.g. and i.e. along with all other abbreviations, R.S.V.P. and P.S. and so on...

It was fixed in the beta build 2.4.0 (2256)... Here's a list of the bugs which have been fixed in the beta build 2.4.0 (2256) Changes/Bugs affecting all platforms Malformed names of ICC profiles could be embedded in PDF-X exports AF-1883

I think the show/hide buttons should at the very least indicate the selection, currently there is no visual feedback as to which state is shown or hidden... A simple visual change would make a world of difference.

a with a macron (ā) is not available for that font, they only exist as independent glyphs...

Hi @AV-Architects, I see the same issue you're seeing... it appears to affect all apart from the first artboard in the Designer layer stack... If you switch the artboard layer order in the Designer file, only the first (lowest) artboard in the layer stack works correctly when hiding and showing layers once placed in the Publisher file... I have a feeling this may already be logged as a bug but I can't locate the bug reference. Hopefully, someone in the moderation team will be able to confirm and if not, log it as such... Placed Artboards.mp4

Hi @NathanC, That's perfect, thanks for logging this as an improvement... I was curious as to whether this may (or may not) help in situations of possible file corruption and/or 'failed to save' error messages by allowing the problematic file and/or containing folder to be renamed while the file is still open effectively creating a live copy of the original?

One use is to isolate and restrict Select All to the selected artboard rather than selecting items across all artboards...

Layers are a very constructive way of working as they give you a lot of flexibility. You can Group logical objects to keep everything organised or use Layers (Capital L) as mentioned above if you wish to control the visibility of different elements in an exported PDF file... As also mentioned above you can Merge Curves or use Add New Curve To Selected Curves Object though based on the example you provided these options aren't going to work... I would advise keeping everything in logical Groups or Layers and also taking a look at things like Global Colours along with Select Same and Select Object as options which may be helpful when constructing your map... https://affinity.help/designer2/English.lproj/index.html?page=pages/Clr/globalClr.html&title=Global colours https://affinity.help/designer2/English.lproj/index.html?page=pages/ObjectControl/selectByAttribute.html&title=Selecting objects by attribute If you have any specific, 'How do I do?' questions please feel free to ask as there are many here willing to provide help and suggestions as to the best way to achieve things... Layers in Affinity Designer Translated into Toggleable Layers in a PDF File Map.mp4

Hi @MEB, Thanks for confirming and for logging...