Jump to content

Optische Ausrichtung

Members
  • Posts

    79
  • Joined

Posts posted by Optische Ausrichtung

  1. 28 minutes ago, Ldina said:

    Agreed...key word here..."constructive!"

    An example: Affinity Publisher was not able to handle German quotation marks correctly from the beginning of version 2. This was a very annoying bug, because with every text change you had to proofread a document from the moment the change was made right through to the end. The problem was only fixed with version 2.6. I don't remember exactly, but perhaps from version 2.3 (or about one years after the problem was recognized as such by Serif) my criticism was perhaps no longer entirely constructive.

     

  2. On 7/2/2024 at 10:45 AM, Herby49 said:

    Ja, es ist leider so, dass das Problem immer noch besteht. Aber vielleicht besteht ja noch die Hoffnung, dass die Entwickler aufgrund der neuerlichen Posts doch noch mal tätig werden. Es kann doch nicht so schwer sein, maschinenlesbaren Code für die Regeln bei Satzzeichen zu entwickeln.

    Es scheint schwer zu sein und das Problem besteht nach wie vor. Nach fast zwei Jahren finde ich auch den Hinweis unter den aktuellen 2.5-Release-Notes etwas deplatziert:

    Quote

    If you have reported a bug and it is not yet fixed, please do not report it again. More fixes will be made in the forthcoming beta cycle.

    Keine Sorge, ich reporte diesen Bug nicht mehr. 🙄

     

  3. 6 hours ago, dddddd said:

    Ich habe das Problem auch gerade. 🙁 Anderthalb Jahre später! (V2.5.3)

    Ja. So wie sich das Unternehmen zu diesem bestätigten Bug verhält, wird es auch so bleiben. Offensichtlich hat man keine Lust, einen derart lächerlichen (aber extrem lästigen) Fehler zu beheben. Vielleicht geht man aber auch ganz einfach davon aus, dass im deutschsprachigen Raum ohnehin niemand das Programm für ernsthafte Arbeiten einsetzt.

     

  4. 18 hours ago, PaulEC said:

    I do understand that there are some new features that many people want, but is it worth having them if the bugs make the software so difficult to use?

    The Affinity Suite has established itself on the market without these "new features". It would be nice if it didn't lose this place now because of these "new features", wouldn't it? 

    18 hours ago, PaulEC said:

    some bugs just go on forever, from update to update, version to version, and are never addressed!

    Interesting perspective: existing bugs remain, new ones are added ... One can only hope that the new owner can do the math.

     

  5. 22 hours ago, PaoloT said:

    There aren't bugs, there!

    At least no ridiculous bugs. And if there are, then not for years.

    Why I'm slowly but surely getting annoyed with Affinity: The Affinity suite could be so wonderful and cover almost 100% of my needs if Serif had a different culture of dealing with bugs. Programs that have serious colour management bugs for months on end are - I'm sorry to say - not fit for serious use. I don't need a spiral or QR code tool if the software can't set closing quotes correctly. And so on. 

    In short, and in the spirit of the original question, it would be really nice if Serif, under new ownership, would finally work through the list of annoying bugs instead of inventing new features. 

     

  6. 4 hours ago, Mainecoon364 said:

    Is it possible to do this?

    Yes.

    Bildschirmfoto2024-01-07um16_16_26.webp.2a12f7242a4858a1f05d73fe4b427ef6.webp

    1. The black curve is present.
    2. Duplicate this curve and set a contour width of 6 cm (yellow in the image). 
    3. Select the "Expand Stroke" function.
    4. Delete the points marked blue in the image. 
    5. The result is a closed curve that can be opened with the Break Curve tool, adding a point if necessary.
      (In the image, this is approximately the light gray part.) Delete the superfluous points. 
    6. The result is the red curve. 

    I hope you get it to work on the iPad.

     

  7. 55 minutes ago, k_au said:

    IIRC, you're on a Mac?

    Yes, you remember correctly. Mainly Mac, but also a bit of Windows.

    8 hours ago, k_au said:

    I'm not sure this was the case before the update.

    Unfortunately, things sometimes get worse with Affinity software. What just worked doesn't necessarily have to work after the next update. But: I think Serif is on the right track overall ... even if the mills sometimes grind very slowly. 

     

  8. 3 hours ago, Dan C said:

    Can you please confirm for me, are you using the Affinity Store or Mac App Store version of the Affinity apps?

    Thank you, I use the versions purchased from Affinity (as »Universal License«). Just for interest: How does the 'roll back' work?

     

    2 hours ago, loukash said:

    you do have a Time Machine backup, right…?

    Oh, yeah, good idea. That is exactly what it is for. I could have thought of that myself, and I might try that. On the other hand, the update will hopefully come soon as well. 

     

  9. 19 minutes ago, woefi said:

    Can you repeat this with AfPublisher

    Done. Here, too, the special character is found in front of the profile name. Although "Publisher", unlike "Designer", does not show the rest of the strange behavior, a queasy feeling still remains. The character certainly doesn't belong there, and no one knows what consequences it will have in finishing or prepress.

    Let's hope that programmers can quickly find the place in the code where a bracket was left open or a semicolon was forgotten. ;-)

     

  10. Perhaps a helpful hint: When I compare the PDF standards of two Affinity-Designer-PDFs exported with the profile "ISOcoated_v2_300_eci.icc" using Acrobat Reader, there is a difference under "Kennung" (Identifier?) for this profile (see screenshots). The special character "ÿ" (Lower case letter Y with Diaeresis) certainly does not belong in front of the profile name and is not found when using other profiles or in PDFs written with an earlier version of Affinity Designer. The profile used is the normal and not renamed profile from the file "eci_offset_2009.zip".

    Actual PDF:

    image.jpeg.1dc3ccd69ceee17381d1a71643002e9f.jpeg

    Older PDF:

    image.jpeg.6163b896c557497d5d7e7e9fb89eddc1.jpeg

     

  11. 47 minutes ago, Hangman said:

    That's the exact same .zip I downloaded as per the instructions on the eci.org website for that specific profile, though interestingly @Dan C mentioned above that he likewise downloaded the same profile from the same source and he's not experiencing any issues...

    Yes, I'm afraid I have no idea how to pull the chestnuts out of the fire. I've tried it with newly created user, reinstalls, selected profiles in many possible variants and much more. Something went pretty wrong there. Maybe I'll switch back to version 2.1 this weekend. The alternative might be to temporarily try replacing Designer with Publisher or switch to the Windows version. The universal license has to be good for something. ;-)

    Edit (and asked by the way): Is it possible to downgrade the Universal license from 2.2 to 2.1 under macOS?   

     

×
×
  • Create New...

Important Information

Terms of Use | 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.