Pyanepsion

Hum. 🙂 The question about the Regex is just a consequence of wanting to solve a peculiarity of Czech typography. For typing in the Affinity suite, I would rather see an auto-correction option in the preferences that would allow to replace one-letter words then space by the letter itself followed by a non-breaking space. This would solve most of the problem and could even be generalised to other situations. It should be possible to specify any sequence of characters. A bit like Word which allows you to automatically replace " with <nbsp>» where <nbsp> is a non-breaking space, or (c) by ©. To this can be added the knowledge of Unicode, that it understands for example that U+00C9 corresponds to É. When it comes to rectifying a text already present in Affinity Publisher, I suggest the following sequence to be run as many times as necessary. It works with the Replace All function, whether there is one or more successive one-letter words: Search: [ |<nbsp>]([a|i|k|o|s|u|v|z|A|I|K|O|S|U|V|Z])[ ]+ Replace with: [ ]$1<nbsp> 🔴The Online help does not provide direct links! I'm modifying it with a workaround.

I misspoke in English. I meant that sometimes, rarely, it can be useful to save the history and it is possible.

Oh well! So you need to ask the Good Fairy Affinity to consider adding this rather important feature to the iPad.

The initial question is about the malfunction of the Czech language software, which therefore requires not to leave single-character words at the end of a line. There is definitely a bug in the Regex handling of Replace All. Even if this bug is solved, it will not solve the original issue. Systematically pasting the one letter word to the word that follows is completely irrelevant, as it will create an inevitable malfunction in the justification. Perhaps the solution is to add the Czech language to the dictionary of languages and hyphenations? Here: https://affinity.help/publisher2/English.lproj/index.html Search: Hyphen Select Managing hyphenation dictionaries Then: Hyphenation What does it look like?

For reference: The threshold of detail perception for the human eye is generally considered to be about 1 arc minute (1/60 degree) of angular distance between two points. This means that if two points are less than 1 arc minute apart, they will be perceived as a single point by the human eye. The closest the human eye can see depends on a number of factors, such as the vision of each individual, but it is generally estimated to be about 25 cm (10 inches). To calculate the distance between two points that form an angle of 1/60 of a degree with the eye located 25 cm away, we need to use the similarity relationship between an angle and distance: distance = (distance to the eye) x (tangent of the angle) So, using this relationship and substituting the given values, we have : distance = (0.25m) x (tangent (1/60 degree)) = 0.25 m × 0.00029088821 = 0.0747205 mm ≈ 0.1 mm However 1 pt = 0.3527777 mm. So: 0,20 pt = 0.07054 mm ≈ 0.1 mm 0,25 pt = 0.088175 mm ≈ 0.1 mm 0,30 pt = 0.1058331 mm ≈ 0.1 mm There is therefore very little difference. Solving the problem I imagine the iPad should work in much the same way as the Mac and Windows versions. If so, just go to Preferences and set the precision and then click on the line to determine the thickness. This value is then transferred to the next open file.

I don’t know anything about Czech, but reading the explanations, I think it’s more a problem with the Czech hyphenation dictionary than with Regex. I’d have to see what the creators of this dictionary on FireFox think about it.

Saving the history of work sessions is not as good an idea as it sounds. When you work all day on a document with many additions, it can end up saturating the memory and slowing down the actions in the software. On the other hand, it may be nice to be able to save the history on demand (for rare use cases) in a single external file that can be loaded on demand. The history should certainly not be stored in the work file itself. In this case, the previous choice of whether or not to save to an external file is, of course, preserved from session to session, but only for each individual project: for example, I would want to save the history of a complicated or long job, but certainly not of all jobs; checking or unchecking another project would not change my choices on the current project.

Exporting a text from Affinity Publisher to Word is a very important step in the process of checking a text before publishing it. For example, it allows you to check with the comparison tool with the original text in Word that the changes required by DTP in Affinity Publisher do not distort the author's thinking. It also allows you to check the spelling and wording of additions and deletions made in Affinity Publisher with third-party extensions in Word (these extensions are also available in Adobe Indesign and QuarkXPress), which are real correction tools unlike what the Affinity suite offers.

Compare the Word version (in green) and the 2 Affinity Publisher versions (in orange). A new line has been added below Purple. Look at the Affinity Publisher versions (in orange). Underline 7 is cut and goes to line as well as Superscript and Purple on the File version.

To tell the truth, I did not understand why you asked for an additional reduction on top of the existing one the day before the launch reduction was to end. There are countless new features in version 2 (of Affinity Photo, but also of other Affinity software). See here, in Affinity Photo, Full feature list, New features. So: You have no use for it and will never exchange files with other users. There is no point for you in buying the new version. This is not a rental. Your version 1 will continue to work. You need one or more of the many additional features in version 2 and want to support Affinity. You must wait for the launch promotion to the end (tomorrow). You need one or more of the many additional features in version 2, but you want to save money. Then you should take advantage of the last few moments of the discount.

Hello @fisherman7071, After 25 January 2023: Affinity Photo Mac = 84,99 € + Affinity Photo iPad = 23,99 € Total = 108,98 € (instead of €63.98, launch promotion). Until 25 January 2023: Affinity Photo Mac + Affinity Designer Mac + Affinity Publisher Mac + Affinity Photo iPad+ Affinity Designer iPad + Affinity Publisher iPad + Affinity Photo Windows + Affinity Designer Windows + Affinity Publisher Windows Total = 119,99 € (instead of € 554,91 retail price, and € 199,99 bundle price).

indesign-type.mp4 It seems that you always come back to the Print type, no matter what you do and what initial preset you use.

What Affinity lists by default is fine, but I would actually like to add more links to image banks, paid or free, to have them directly at hand.

Hello to all. How to add your own favourite image banks in the Stock sub-window? Thank you for your explanations.

The reappearance of spaces does not work on my Windows 11 Affinity Publisher v2.0.3.1688. It works on: Windows 11 Affinity Publisher v2.0.3.1670 (same computer). Windows 10 Affinity Publisher v2.0.3.1670. Windows 10 Affinity Publisher v2.0.0.1640.

If I refresh the index to version 2.0.3.1670 (betas), I find the En spaces followed by a thin space. If I take this modified version and switch back to version 2.0.3.1688, the spaces disappear again when I refresh the index.

😉I said:

We cannot change either of the two separators (hyphen ‘ — ’ and comma ‘,’), p. 65. index-separator.afpub

So I haven’t figured out how to put ‘comma space’ between the two numbers. If I do it by hand once the index is done, it makes the index invalid.

Hello, @Frédérique B, If it is a MacOS 10.15 Catalina, it should work unless your computer is even older. 2019 is very old for a Mac! You should still have read the product specifications or at least tried the trial version before your purchase. With your old Mac computer, you’re going to run into more and more problems anyway. You should therefore take advantage of this mishap to update your Mac or to change your system. I’m using an old Windows 10 from 2015 with no problems. I just changed the graphics card a few months ago.

v 2.0.3.1688. Hello everyone. The comma separating the referenced page numbers does not respect the usual typographical standard and the referenced sequence is then put on 2 lines instead of one. There should be a space after each comma. Of course, the bug can be easily worked around by adding a space at the end with a Regex. The index is then no longer compliant. It would be nice if we could choose the separation sequence ourselves (here comma space), especially as this can sometimes be another separator depending on the point standards.

@Fritz_H, read it again. All updates to perpetual versions of Microsoft Office are included until the next upgrade. After the upgrade there are no more updates except for security updates. It is important to understand that the perpetual version freezes the version at a given level. It is exactly the same product as the rental version existing at that time. An old file of the rental version produced at that time will have the same incompatibility problems. Pšenda is right. The incompatibility is common in computing except when the data storage format is fixed, and even then, there is frequently data loss when you go from one level to a lower level and back to the level. This can be seen for example with DOCX files. If you use, for example, advanced formatting features in a recent version of Word that do not exist in earlier versions, these features may not be displayed correctly in earlier versions. Word is never just a texter. Between DTP and a text editor, it is obviously night and day and therefore the incompatibility are much greater. Whether or not v1 allows v2 to be read is therefore a financial choice. Its cost is generally very high and the result will be poor anyway, whatever the software and whatever the manufacturer, even though it can often be circumvented. In my humble opinion, it is therefore not really justifiable. The money is better spent on new features and improvements.

According to Microsoft, there are no differences between the 365 and vintage versions. Here are the new features of Word 2021 compared to Word 2019 : https://support.microsoft.com/en-us/office/what-s-new-in-word-2021-for-windows-8f0b9117-8cf4-4677-8cd5-d848dd0e1ac9

Hello @Fritz_H, The functionality and updates of the Microsoft Office perpetual and rental applications are completely identical. In the rental version, the software Office 365 remains active as long as you pay. It stops working when you stop paying. In the perpetual version, the software Office [Vintage] remains active even after the upgrade has been completed.

The example is completely irrelevant! Microsoft Office 365 is the same software as the vintage version of Microsoft Office except that it is only available for rent. Pre-2007 versions of Microsoft Office do not open versions created in 2007 or later. Post-2007 versions can open the news versions, but they lose many features and when you get them back you have to redo everything.