Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by anweid

  1. Just for reference: The official version again crashes at trying to load the document.
  2. Done. I copied the fonts that Publisher shows in its font manager. You probably have 'Symbol' and 'Wingdings' already installed, anyway. The rest should be either bought, self-made or both... And: If you write 'to investigate the layout issues', does that mean that the document can now be loaded without crashing, so that you are able to detect 'layout issues'? With best regards, Andreas Weidner
  3. Done. Inside the ZIP file, you'll find EAGLEInANutshell.afpub (plus hopefully all necessary images), which I'm in the process of updating from an old InDesign document (not imported as IDML, but newly created from scratch and using copy-and-paste) to a new version with Affinity (currently, Affinity is still missing some functionality). The corresponding PDF file was created with version and shows how the document should look like. The document gets messier the farther one gets to its end, and for the time being, I did not include the fonts, so please don't get a shock when seeing it. If for some reason, you need the fonts, I can also provide them via DropBox (would that be the same link, or a different one?). With best regards, Andreas Weidner PS: Even in the PDF file, the main font looks rather strange. This is due to extremely bad kerning of that font, which I'm also in the process of updating...
  4. A rather complex document (50 pages, several linked images, lots of pins, table of contents, index) created with Affinity Publisher just refuses to work properly with any later version: The beta versions 1.8.x prior to the official version 1.8.0 are able to load the document nicely, but always crash reliably on trying to either update the table of contents, or doing a preflight check. The official version 1.8.0 utterly fails to load the document, and always crashes reliably when trying to load it. The new beta version reverts to the 'old' behaviour: It can read the document, but always crashes on updating the table of contents or doing a preflight check. Therefore, I reverted to the old version again, ignored the current official one, and stopped using Publisher for the time being (which is sad), until a bug fix is available... Since the problematic document is currently not for public distribution, it would be useful to get the possibility for a private upload or something - thanks. With best regards, Andreas Weidner
  5. In Affinity Photo, it works. Wonderful - thanks. Andreas Weidner
  6. Please ignore the above post. The issue already seems to be corrected in the current beta (I should have checked that before posting). Andreas Weidner
  7. In the German Affinity Publisher (Windows), underscores in file names are not correctly shown in the Resource Manager: Instead of showing the underscore as a separate character, the character following the underscore is underlined (as is usually the case with keyboard shortcuts). Andreas Weidner
  8. That's an idea. Let's try... Andreas Weidner panorama.zip
  9. After downloading the picture attached to the above post, I also cannot read it with any program anymore, because it seems to have become corrupted either by uploading or by downloading. Please tell me how to send you the original file, bypassing this forum. I managed to read the original image with SnagIt, Directory Opus, ImageGlass, Paint, Edge, LibreOffice, XnViewMP, InDesign CS5.5, PDF24. I had problems with Serif products, FireFox, TextMaker. Andreas Weidner
  10. The German Affinity Photo (and its predecessors, and all other Affinity programs, and in fact all other Serif programs including PhotoPlus 8) simply dies silently when trying to load the attached JPG image of size 12128*1888. All other programs that I ever tried can load it without any problems (including Microsoft Paint). It would be nice if Serif programs could also manage that. Andreas Weidner 20191027_115327.jpg
  11. Well... Of course you could reduce the abbreviations list, but that would still leave the bug that some character combinations might be capitalised that do not appear at the beginning of sentences. The above auto-correction should only capitalise words that really do appear at the beginning of a sentence, but not elsewhere. Andreas Weidner
  12. This is quite probably by design, but I still call it a bug, because it represents a painful user interface: Affinity Designer (Windows) is loaded with a long table of words to auto-correct in various languages. A few 'words' are useful, like '(c)', '1/2' or 'mm2', but the overwhelming majority is rather useless. Trying to auto-correct every typo that might possibly happen is not such a good idea. Therefore, I want to get rid of 95% of that list. Unfortunately, it's impossible to select more than one entry at the same time, neither the Add nor the Delete button seems to have any keyboard shortcut, and after selecting an entry by clicking on it, and clicking Delete, the selection does not move up or down, but just disappears. This means that I have to click hundreds of times to get rid of most of that list. It would be much nicer if the above three things were implemented (multi-selection, button shortcuts, selection moving). Additionally, the same behaviour could be implemented for the other lists of the Settings dialog (abbreviations, title exceptions). Andreas Weidner
  13. The German Affinity Publisher for Windows, when used in conjunction with German language text, behaves as follows when using auto-correction: When the option Capitalise the first character of sentences is switched on, the character combinations 'fr.', 'sa.' and 'so.' are capitalised anywhere in the sentence (into 'Fr.', 'Sa.' and 'So.'). The first two are not so problematic, because words like that don't exist in German, but the latter is a valid word that can end a sentence. E.g., the correct sentence 'Das ist so.' (which translates into 'That's so.') is auto-corrected into 'Das ist So.', which is not correct. It might be that this is due to the above three combinations being abbreviations of some German days of the week, but the others ('Mo.', 'Di.', 'Mi.' and 'Do.') do not behave that way. When the option Capitalise the first character of sentences is switched on, the character combination 'apostrophe + lower-case s + dot' ('s.) is auto-corrected into 'apostrophe + upper-case s + dot' ('S.). Independent of the fact that this combination is very rare in German (as opposed to English), the auto-corrected result is never used in German. When switching to British English, no correction is done (which is wonderful and should also be the case for German). Both of the above corrections are wrong, anyway, but they also do their corrections at a place that is not the first character of any sentence, which seems to be additionally out of place here. Andreas Weidner
  14. This not only happens with a slash, but also with other characters. The German Publisher under Windows hyphenates also directly before bullets. The attached screenshots (never mind the bad justification and kerning) tells the reader of the original document which menu entries to select, and I decided to separate the menu levels with bullets. The strange hyphenation comes from Publisher. For the second image, I also tried the characters ¼®¥Φϖ☺ (instead of the bullet) just for fun, and each and every one of them makes the same hyphenation happen. Unfortunately, since standard hyphenation algorithms normally only look up the probability of hyphens between pairs of characters, and the above characters probably never appear in any pair list, I don't have any idea how to solve this. The problems with the slash should be solved somehow, though, because slashes appear rather often... Andreas Weidner
  15. This is what I meant with (3) above: This button should better be called Ausrichten to be consistent. I realised this problem exactly because suddenly, two groups with the same text appeared in the toolbar... Andreas Weidner
  16. The document where the problems mainly occur uses some fields in the master page's footer (author, savedate, filename, pagecount), and nowhere else. Publisher also crashed once when trying to open this document, but I also couldn't force that error again... Andreas Weidner
  17. This of course would be the best possibility: Everybody could get their own wonderful settings... Andreas Weidner
  18. Affinity Publisher 1.7.3.x seems to always display all defined text styles in its Text styles studio. This often makes styles show up there that I will never need again, e.g.: I define header and footer styles for the master pages, but after the master is defined, I don't need those styles anywhere else in the document. I define index and contents styles once to make things look nice, but will never use such styles myself outside the index or the table of contents. It would therefore be nice if the text style dialog would also support the hiding of text styles in the studio, so that this doesn't get cluttered up so quickly. Thanks. Andreas Weidner
  19. As a matter of fact, I liked InDesign up to version 5 and stopped using it after an update to 5.5, because it was extremely buggy and crashed around 50 times a day. But - and this was a good thing - it never, ever corrupted any of my files, even with the largest number of crashes I had in any program I've ever seen... Andreas Weidner
  20. The German Affinity Publisher (Windows) makes it sometimes very difficult to select pinned objects (see video): The file contains a bit of text, a bitmap pinned as a character, a pinned text on top of it and two vector objects at the right. The vector objects can easily be selected via mouse clicks (0:00-0:08). Fine. With Alt+Click on the circle, Publisher nicely cycles through all objects at that position (0:08-0:20). Fine. When selecting the bitmap, Publisher changes the cursor to a black one, which apparently makes it possible to move the image like a character. Selecting the topmost text is not possible anymore, because clicks on the small text frame are now consistently ignored (0:20-0:30). Though this might be by design, I would find it more logical if a click on the topmost object would select it properly. Unfortunately, even Alt+Click on the topmost text frame (or even the bitmap itself) does not cycle through any objects anymore. The selection is thus stuck. The only possibility to get out of this sticky mode is to select something different, and then click on the topmost text again (0:30-end). It would be nice if at least Alt+Click would cycle through objects under these circumstances, and even better if a click on the topmost object would again select it as usual. Andreas Weidner PinSelection.mp4
  21. With the German Affinity Publisher (Windows), as soon as I do lots of things to make pinned objects behave properly (mainly in a double-sided document with mirrored margins), I get random crashes: Publisher just vanishes without trace, without error message, without anything. And the reason why I sometimes have to do lots of things with pinned objects is that there seems to be a number of odd tweaks in the implementation that make pinned objects behave strangely or unexpectedly, so lots of fiddling is involved. Since this happens randomly and on more or less all files I tried, I cannot send you an example file, but just rant a bit. Documents without pinned objects don't regularly produce crashes (as far as I remember). Andreas Weidner
  22. Aha. Then I don't understand that button at all: This button seems to be the only possibility to make the 8 circle handles around an object (meaning adjustable) to change into crosses (meaning non-adjustable). This is not a global setting, but one that is defined for each pinned object, because an object that I define as adustable stays adjustable (circled), and a non-adjustable one also stays that way (crossed). The only way I can understand this is that it is an object property. The eight handles around an object always appear to correctly reflect the current status of this object's adjustability, independent of the state of the checkbox. It's just that the state of the checkbox does not reflect any selected object, which sometimes makes it necessary to change the checkbox twice in order to change the object's state. But anyway: This property is definitely not saved on disk, because after saving and loading, everything is adjustable again. This is all excruciatingly complicated and illogical for me. I suggest the following: If the adjustability should be a property (I would like that, as it can prevent accidental moving), please make the checkbox correctly reflect the selection, and save and load the property to file. If the adjustability should not be a property, please don't make objects keep their adjustability independent of the current state of the checkbox. Andreas Weidner
  23. Please don't remove that button - that's exactly the wrong direction! It would simply be wonderful to decently be able to edit embedded files (PagePlus could do this). Andreas Weidner
  24. Here it is. It uses several styles of a bought font called 'TheSans', which I may not post here. In case it's necessary please tell me how to send this privately. Andreas Weidner Test-Elektrotechnik.afpub
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.