AdamW

Typically we output text as unicode code points, but here because there is no unicode representation of the double letter ligatures included in the font we output them as glyph indexes.
Subsequently we build a 'ToUnicode' map for the font that is embedded in the PDF and which can be used to map glyph indexes to (sequences, if necessary, of) unicode code points for PDF reader applications. This is the part of the export that is causing the issue. One heuristic we employ is to look at the glyph names in the font. Typically / conventionally e.g. an 'fi' ligature will have the glyph name 'f_i'. In the case of CCWildWords it rather unhelpfully names its double uppercase letter ligatures with names such as 'a_A', 'b_B'. This isn't incorrect, but does lead our ToUnicode mapping to represent each ligature as a lowercase / uppercase pair. Currently I see this very much as an edge case as it will only occur with a font with such 'unhelpfully' named ligature glyphs.

Typically we output text as unicode code points, but here because there is no unicode representation of the double letter ligatures included in the font we output them as glyph indexes.
Subsequently we build a 'ToUnicode' map for the font that is embedded in the PDF and which can be used to map glyph indexes to (sequences, if necessary, of) unicode code points for PDF reader applications. This is the part of the export that is causing the issue. One heuristic we employ is to look at the glyph names in the font. Typically / conventionally e.g. an 'fi' ligature will have the glyph name 'f_i'. In the case of CCWildWords it rather unhelpfully names its double uppercase letter ligatures with names such as 'a_A', 'b_B'. This isn't incorrect, but does lead our ToUnicode mapping to represent each ligature as a lowercase / uppercase pair. Currently I see this very much as an edge case as it will only occur with a font with such 'unhelpfully' named ligature glyphs.

Typically we output text as unicode code points, but here because there is no unicode representation of the double letter ligatures included in the font we output them as glyph indexes.
Subsequently we build a 'ToUnicode' map for the font that is embedded in the PDF and which can be used to map glyph indexes to (sequences, if necessary, of) unicode code points for PDF reader applications. This is the part of the export that is causing the issue. One heuristic we employ is to look at the glyph names in the font. Typically / conventionally e.g. an 'fi' ligature will have the glyph name 'f_i'. In the case of CCWildWords it rather unhelpfully names its double uppercase letter ligatures with names such as 'a_A', 'b_B'. This isn't incorrect, but does lead our ToUnicode mapping to represent each ligature as a lowercase / uppercase pair. Currently I see this very much as an edge case as it will only occur with a font with such 'unhelpfully' named ligature glyphs.

Typically we output text as unicode code points, but here because there is no unicode representation of the double letter ligatures included in the font we output them as glyph indexes.
Subsequently we build a 'ToUnicode' map for the font that is embedded in the PDF and which can be used to map glyph indexes to (sequences, if necessary, of) unicode code points for PDF reader applications. This is the part of the export that is causing the issue. One heuristic we employ is to look at the glyph names in the font. Typically / conventionally e.g. an 'fi' ligature will have the glyph name 'f_i'. In the case of CCWildWords it rather unhelpfully names its double uppercase letter ligatures with names such as 'a_A', 'b_B'. This isn't incorrect, but does lead our ToUnicode mapping to represent each ligature as a lowercase / uppercase pair. Currently I see this very much as an edge case as it will only occur with a font with such 'unhelpfully' named ligature glyphs.

Typically we output text as unicode code points, but here because there is no unicode representation of the double letter ligatures included in the font we output them as glyph indexes.
Subsequently we build a 'ToUnicode' map for the font that is embedded in the PDF and which can be used to map glyph indexes to (sequences, if necessary, of) unicode code points for PDF reader applications. This is the part of the export that is causing the issue. One heuristic we employ is to look at the glyph names in the font. Typically / conventionally e.g. an 'fi' ligature will have the glyph name 'f_i'. In the case of CCWildWords it rather unhelpfully names its double uppercase letter ligatures with names such as 'a_A', 'b_B'. This isn't incorrect, but does lead our ToUnicode mapping to represent each ligature as a lowercase / uppercase pair. Currently I see this very much as an edge case as it will only occur with a font with such 'unhelpfully' named ligature glyphs.

At first I thought your observation made perfect sense, but upon reflection, I do think there is a need for both buttons, and that is because the visible state of the different objects that make up a query could have their visibility changed from the layer panel. For example, let’s say that you have some objects matching a state query that are currently invisible, and some others matching the same query that are currently visible. In that case with mixed visibility, which state should a single toggle show? In the current implementation, the two buttons are effectively “make all visible” and “make all hidden,” and they will both have an effect when the objects have mixed visibility settings.

Are you using English US? If so, it's just a "translation" issue. Not all labels have gone through the translation process yet (even though they mainly the same for English US, they still go through a different process)

@MikeTO - I'll start off by admitting I have not had a chance to read this cover to cover - so far I have merely dipped in and skimmed in a few places. However what I have seen seems very well presented, informative and accurate. I would like to thank you for making this available as a free resource and also take this opportunity to thank you for your contribution on the beta forums which has been both notable and significant.
Adam Whitehouse
Project Manager, Affinity Publisher

Yes, for the purposes of Find & Replace a field is treated as single entity, so you can, for instance, search for all instances of a field and change local formatting, or replace the field with another field, or replace found regular text with a particular field.

Yes, for the purposes of Find & Replace a field is treated as single entity, so you can, for instance, search for all instances of a field and change local formatting, or replace the field with another field, or replace found regular text with a particular field.

@MikeTO - I'll start off by admitting I have not had a chance to read this cover to cover - so far I have merely dipped in and skimmed in a few places. However what I have seen seems very well presented, informative and accurate. I would like to thank you for making this available as a free resource and also take this opportunity to thank you for your contribution on the beta forums which has been both notable and significant.
Adam Whitehouse
Project Manager, Affinity Publisher

@MikeTO - I'll start off by admitting I have not had a chance to read this cover to cover - so far I have merely dipped in and skimmed in a few places. However what I have seen seems very well presented, informative and accurate. I would like to thank you for making this available as a free resource and also take this opportunity to thank you for your contribution on the beta forums which has been both notable and significant.
Adam Whitehouse
Project Manager, Affinity Publisher

@MikeTO - I'll start off by admitting I have not had a chance to read this cover to cover - so far I have merely dipped in and skimmed in a few places. However what I have seen seems very well presented, informative and accurate. I would like to thank you for making this available as a free resource and also take this opportunity to thank you for your contribution on the beta forums which has been both notable and significant.
Adam Whitehouse
Project Manager, Affinity Publisher

@MikeTO - I'll start off by admitting I have not had a chance to read this cover to cover - so far I have merely dipped in and skimmed in a few places. However what I have seen seems very well presented, informative and accurate. I would like to thank you for making this available as a free resource and also take this opportunity to thank you for your contribution on the beta forums which has been both notable and significant.
Adam Whitehouse
Project Manager, Affinity Publisher

@MikeTO - I'll start off by admitting I have not had a chance to read this cover to cover - so far I have merely dipped in and skimmed in a few places. However what I have seen seems very well presented, informative and accurate. I would like to thank you for making this available as a free resource and also take this opportunity to thank you for your contribution on the beta forums which has been both notable and significant.
Adam Whitehouse
Project Manager, Affinity Publisher

@MikeTO - I'll start off by admitting I have not had a chance to read this cover to cover - so far I have merely dipped in and skimmed in a few places. However what I have seen seems very well presented, informative and accurate. I would like to thank you for making this available as a free resource and also take this opportunity to thank you for your contribution on the beta forums which has been both notable and significant.
Adam Whitehouse
Project Manager, Affinity Publisher

@MikeTO - I'll start off by admitting I have not had a chance to read this cover to cover - so far I have merely dipped in and skimmed in a few places. However what I have seen seems very well presented, informative and accurate. I would like to thank you for making this available as a free resource and also take this opportunity to thank you for your contribution on the beta forums which has been both notable and significant.
Adam Whitehouse
Project Manager, Affinity Publisher

@MikeTO - I'll start off by admitting I have not had a chance to read this cover to cover - so far I have merely dipped in and skimmed in a few places. However what I have seen seems very well presented, informative and accurate. I would like to thank you for making this available as a free resource and also take this opportunity to thank you for your contribution on the beta forums which has been both notable and significant.
Adam Whitehouse
Project Manager, Affinity Publisher

Okay, so I'm running an instance of the 1790 build with OpenCL disabled on my Windows computer right now, and I have to say that so far it's a remarkable improvement over the lagging I got in 1781—probably at least as fast as version 1 or close to it. Granted, it's only been running for a few hours, but I'll let this instance run overnight and see if I find anything different the next day.

FYI the cross reference menu commands are still listed in Shortcuts.

Status: Beta
Purpose: Fixes and updates
Requirements: Licensed Affinity Publisher 2 (registered to an Affinity ID account)
Mac App Store: Not Submitted
Download: ZIP Download
Auto-update: Not Available
---
We are pleased to announce that the first Affinity Publisher 2 Customer Beta 2.0.3.1674 is now available as a download from the link above.
This beta is an update to the 2.0.0 version recently released to all customers and will form the basis of our first patch for 2.0.0. We recommend that you use this beta in preference to the release version if you are affected by any of the issues listed below.
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
---
- New Document: Custom Document Preset order is not retained between app sessions
- afpackage fails to find Resources on Open
- Fixed spurious future version error under certain circumstances
- Improvements with PDF Import and Layers
- Fixes for RTF import - font name discrepancies, fields in footnotes
- Update for HEIF importer
- DWG Import scaling improvements
- Fix for export of Books with Bleed
- Preview exported PDF fails on book exports
- Opening and closing chapters in a book can leave the files locked / read only
- Crash opening a bunch of chapters from a book simultaneously
- Export Panel UI fixes
- Fix for Booklet printing model
- Fixed some tool drawing issues relating to selections across spreads etc
- Pen tool tweaks and fixes
- Fixed hang that could occur composing vertical centre aligned text
- OpenType handling does not respect lookup flags such as IgnoreMarks
- Hit box of scaled text could be incorrect
- Gradients on text strokes don't render unless the fill also has a gradient
- Fixes for line breaking in some odd cases with punctuation
- Merge runs of tabs using leaders
- Resource Manager updates
- Fixed various issues involving handling of placed document files
- Placed documents with bleed can fail to render the bleed correctly
- Fixed Help menu links
- Light UI Improvements
- Fix for disappearing rulers
- Many and various Layers Panel updates and fixes
- Auto flow place: Added an option to auto-flow place to replace the content of already populated picture frames
- More attributes are retained when replacing images in frames
- Pages Panel, double clicking does not zoom page to view
- Ensure global colour edits update live
- Select Same Name should only select objects with user supplied names
- New clearer icons for stroke properties (cap, join, align)
- Localisation updates
---
To be notified about all future Mac beta updates, please follow this notification thread 
To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this release announcement thread

Status: Beta
Purpose: Fixes and updates
Requirements: Licensed Affinity Publisher 2 (registered to an Affinity ID account)
Mac App Store: Not Submitted
Download: ZIP Download
Auto-update: Not Available
---
We are pleased to announce that the first Affinity Publisher 2 Customer Beta 2.0.3.1674 is now available as a download from the link above.
This beta is an update to the 2.0.0 version recently released to all customers and will form the basis of our first patch for 2.0.0. We recommend that you use this beta in preference to the release version if you are affected by any of the issues listed below.
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
---
- New Document: Custom Document Preset order is not retained between app sessions
- afpackage fails to find Resources on Open
- Fixed spurious future version error under certain circumstances
- Improvements with PDF Import and Layers
- Fixes for RTF import - font name discrepancies, fields in footnotes
- Update for HEIF importer
- DWG Import scaling improvements
- Fix for export of Books with Bleed
- Preview exported PDF fails on book exports
- Opening and closing chapters in a book can leave the files locked / read only
- Crash opening a bunch of chapters from a book simultaneously
- Export Panel UI fixes
- Fix for Booklet printing model
- Fixed some tool drawing issues relating to selections across spreads etc
- Pen tool tweaks and fixes
- Fixed hang that could occur composing vertical centre aligned text
- OpenType handling does not respect lookup flags such as IgnoreMarks
- Hit box of scaled text could be incorrect
- Gradients on text strokes don't render unless the fill also has a gradient
- Fixes for line breaking in some odd cases with punctuation
- Merge runs of tabs using leaders
- Resource Manager updates
- Fixed various issues involving handling of placed document files
- Placed documents with bleed can fail to render the bleed correctly
- Fixed Help menu links
- Light UI Improvements
- Fix for disappearing rulers
- Many and various Layers Panel updates and fixes
- Auto flow place: Added an option to auto-flow place to replace the content of already populated picture frames
- More attributes are retained when replacing images in frames
- Pages Panel, double clicking does not zoom page to view
- Ensure global colour edits update live
- Select Same Name should only select objects with user supplied names
- New clearer icons for stroke properties (cap, join, align)
- Localisation updates
---
To be notified about all future Mac beta updates, please follow this notification thread 
To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this release announcement thread

Status: Beta
Purpose: Fixes and Updates
Requirements: Licensed Affinity Publisher 2 (registered to an Affinity ID account)
Windows Store: Not Submitted
Download: MSIX Download
Auto-update: Not Available
---
We are pleased to announce that the first Affinity Publisher 2 Customer Beta 2.0.3.1670 is now available as a download from the link above.
Please note: We are working on an equivalent MSI/EXE installer to ALSO be available before the time this 2.0.3.x beta cycle finishes, and becomes a public release.
This beta is an update to the 2.0.0 version recently released to all customers and will form the basis of our first patch for 2.0.0. We recommend that you use this beta in preference to the release version if you are affected by any of the issues listed below.
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
---
Known Issues
- PDF Layers can failing to import for opened and placed PDFs. This is a regression over the 2.0.0 release.
---
Updates and Fixes
- New Document: Custom Document Preset order is not retained between app sessions
- afpackage fails to find Resources on Open
- Fixed spurious future version error under certain circumstances
- Improvements with PDF Import and Layers
- Fixes for RTF import - font name discrepancies, fields in footnotes
- Update for HEIF importer
- DWG Import scaling improvements
- Opening and closing chapters in a Book can leave the files locked / read only
- Crash opening a bunch of chapters from a Book simultaneously
- Export Panel UI fixes
- Preview exported PDF fails on Book exports
- Fix for export of Books with Bleed
- Fix for Booklet printing model
- Fixed some tool drawing issues relating to selections across spreads etc
- Pen tool tweaks and fixes
- Fixed hang that could occur composing vertical centre aligned text
- OpenType handling does not respect lookup flags such as IgnoreMarks
- Hit box of scaled text could be incorrect
- Gradients on text strokes don't render unless the fill also has a gradient
- Fixes for line breaking in some odd cases with punctuation
- Merge runs of tabs using leaders
- Resource Manager updates
- Fixed various issues involving handling of placed document files
- Placed documents with bleed can fail to render the bleed correctly
- Light UI Improvements
- Many and various Layers Panel updates and fixes
- Clipboard: 32 bit DIB support added
- Auto Flow Place: Added an option to auto-flow place to replace the content of already populated picture frames
- More attributes are retained when replacing images in frames
- Pages Panel, double clicking does not zoom page to view
- Ensure global colour edits update live
- Select Same Name should only select objects with user supplied names
- New clearer icons for stroke properties (cap, join, align)
- Localisation updates
---
To be notified about all future Windows beta updates, please follow this notification thread
To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this release announcement thread
 

Status: Beta
Purpose: Fixes and Updates
Requirements: Licensed Affinity Publisher 2 (registered to an Affinity ID account)
Windows Store: Not Submitted
Download: MSIX Download
Auto-update: Not Available
---
We are pleased to announce that the first Affinity Publisher 2 Customer Beta 2.0.3.1670 is now available as a download from the link above.
Please note: We are working on an equivalent MSI/EXE installer to ALSO be available before the time this 2.0.3.x beta cycle finishes, and becomes a public release.
This beta is an update to the 2.0.0 version recently released to all customers and will form the basis of our first patch for 2.0.0. We recommend that you use this beta in preference to the release version if you are affected by any of the issues listed below.
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
---
Known Issues
- PDF Layers can failing to import for opened and placed PDFs. This is a regression over the 2.0.0 release.
---
Updates and Fixes
- New Document: Custom Document Preset order is not retained between app sessions
- afpackage fails to find Resources on Open
- Fixed spurious future version error under certain circumstances
- Improvements with PDF Import and Layers
- Fixes for RTF import - font name discrepancies, fields in footnotes
- Update for HEIF importer
- DWG Import scaling improvements
- Opening and closing chapters in a Book can leave the files locked / read only
- Crash opening a bunch of chapters from a Book simultaneously
- Export Panel UI fixes
- Preview exported PDF fails on Book exports
- Fix for export of Books with Bleed
- Fix for Booklet printing model
- Fixed some tool drawing issues relating to selections across spreads etc
- Pen tool tweaks and fixes
- Fixed hang that could occur composing vertical centre aligned text
- OpenType handling does not respect lookup flags such as IgnoreMarks
- Hit box of scaled text could be incorrect
- Gradients on text strokes don't render unless the fill also has a gradient
- Fixes for line breaking in some odd cases with punctuation
- Merge runs of tabs using leaders
- Resource Manager updates
- Fixed various issues involving handling of placed document files
- Placed documents with bleed can fail to render the bleed correctly
- Light UI Improvements
- Many and various Layers Panel updates and fixes
- Clipboard: 32 bit DIB support added
- Auto Flow Place: Added an option to auto-flow place to replace the content of already populated picture frames
- More attributes are retained when replacing images in frames
- Pages Panel, double clicking does not zoom page to view
- Ensure global colour edits update live
- Select Same Name should only select objects with user supplied names
- New clearer icons for stroke properties (cap, join, align)
- Localisation updates
---
To be notified about all future Windows beta updates, please follow this notification thread
To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this release announcement thread
 

Status: Beta
Purpose: Fixes and Updates
Requirements: Licensed Affinity Publisher 2 (registered to an Affinity ID account)
Windows Store: Not Submitted
Download: MSIX Download
Auto-update: Not Available
---
We are pleased to announce that the first Affinity Publisher 2 Customer Beta 2.0.3.1670 is now available as a download from the link above.
Please note: We are working on an equivalent MSI/EXE installer to ALSO be available before the time this 2.0.3.x beta cycle finishes, and becomes a public release.
This beta is an update to the 2.0.0 version recently released to all customers and will form the basis of our first patch for 2.0.0. We recommend that you use this beta in preference to the release version if you are affected by any of the issues listed below.
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
---
Known Issues
- PDF Layers can failing to import for opened and placed PDFs. This is a regression over the 2.0.0 release.
---
Updates and Fixes
- New Document: Custom Document Preset order is not retained between app sessions
- afpackage fails to find Resources on Open
- Fixed spurious future version error under certain circumstances
- Improvements with PDF Import and Layers
- Fixes for RTF import - font name discrepancies, fields in footnotes
- Update for HEIF importer
- DWG Import scaling improvements
- Opening and closing chapters in a Book can leave the files locked / read only
- Crash opening a bunch of chapters from a Book simultaneously
- Export Panel UI fixes
- Preview exported PDF fails on Book exports
- Fix for export of Books with Bleed
- Fix for Booklet printing model
- Fixed some tool drawing issues relating to selections across spreads etc
- Pen tool tweaks and fixes
- Fixed hang that could occur composing vertical centre aligned text
- OpenType handling does not respect lookup flags such as IgnoreMarks
- Hit box of scaled text could be incorrect
- Gradients on text strokes don't render unless the fill also has a gradient
- Fixes for line breaking in some odd cases with punctuation
- Merge runs of tabs using leaders
- Resource Manager updates
- Fixed various issues involving handling of placed document files
- Placed documents with bleed can fail to render the bleed correctly
- Light UI Improvements
- Many and various Layers Panel updates and fixes
- Clipboard: 32 bit DIB support added
- Auto Flow Place: Added an option to auto-flow place to replace the content of already populated picture frames
- More attributes are retained when replacing images in frames
- Pages Panel, double clicking does not zoom page to view
- Ensure global colour edits update live
- Select Same Name should only select objects with user supplied names
- New clearer icons for stroke properties (cap, join, align)
- Localisation updates
---
To be notified about all future Windows beta updates, please follow this notification thread
To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this release announcement thread