Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

547 profile views
  1. Yes, there are of course possible workarounds using find and replace. But this is not a clean workflow, and very error-prone. Let me tell you a real-world example for this feature. This was a situation I had to deal with: For a cruise company I had to do a lot of catalogs. The font I used had the ligature “ff”. Now we wanted to have ligatures enabled, buuuut: German has this wonderful long word “Schifffahrt” (cruise), which has a triple-f. Now there would be a ligature ff followed by a normal f. And the client didn’t like how this looked. So we had to avoid ligatures on triple f’s. Due to the nature of a shipping company, this word would appear considerably often in their catalogs. Having worked with a reasonable amount of paragraph styles (that inherited from each other), I was able to apply a GREP style to texts that use this font. The GREP style applied the character style “no ligatures” on every occurrence of “f{3,}”. And as we copied our styles from document to document, I was able to just forget about this problem forever. InDesign handled it for me in dozens of documents that I made for this client. This may sound like a very particular case, but I use GREP styles very often in my daily work. It’s a very helpful feature. So they’re definitely something worth working with. I couldn’t really just replace that practice by using search and replace.
  2. So, why are we discussing Inkscape Mac Port Alpha Bug Fixes in this threat? That’s kinda off-topic.
  3. This is a PowerPC software. I think this doesn’t run on any OS that is also capable of running Affinity.
  4. I can’t really answer that, because I really don’t understand the question. REGEX has nothing to do with the operating system. It’s a way to describe complex searches. I suppose it is implemented for almost any operating system (Windows, macos, linux derivates, …), but I also guess that Affinity uses its own modified regex-engine, so it wouldn’t be dependent on the OS and so it can access all the information about the text (like styles). correct
  5. Thank you very very much for your detailed explanation! I now see clear, why my pattern didn’t work, and understand your correction. Thanks for taking the time!
  6. Thank you very much! This pattern does work now although I still don’t understand why. Would you be so kind to explain (?-s) to me? Does this have a name? I couldn't find it in my regex cheatsheet. Is it something specifically for AP? I’d like to understand it, so I can prevent similar mistakes in the future. Also does this mean $ not matching a paragraph ending is intentional behavior? Or is it a bug? It seems pretty odd to me. I would totally understand if it doesn’t match a wrapped line obviously, and also if it would not match a line break. But not matching a paragraph break seems absurd to me, I simply don’t understand this behavior.
  7. Thanks for your answer. I should’ve mentioned that at point 3: I actually tried making the operators lazy like in your pattern, but it doesn’t work either, as $ doesn’t match the paragraph ending. Now it strangely selects only one line of text and one line of chords, although every line has a it’s own paragraph ending.
  8. Thanks for your answer. Sadly, it still doesn’t make sense to me: I have a paragraph break after every line (in the result you can even see the pilcrow signs). So as you stated the $ should match that. This is pretty normal for grep, as . matches every character (if it’s not in one-line mode) I understand, that the standard is greedy. But even if I make the operation lazy as you suggested, the problem is still, that $ doesn’t match the paragraph break, as it should. If I’m still misunderstanding the concept, could you maybe write me a pattern that does the job correctly, so I can understand how AP’s GREP interpreter is different? Edit: I attached the file for testing purposes. Chords Test.afpub
  9. When I use GREP search, and define that I only want to find whole lines by using the ^ and $ signs, this will get ignored. In my case, I try to format guitar chord sheets, and give all the chords a pre-defined format. I try to detect the chord lines using following GREP pattern: ^.* {4,}.*$ Although this may not be a perfect pattern, it mostly works, as the chord lines include a tremendous amount of whitespace. This pattern works perfectly in another GREP search I tried. As I specified, I only want to match one line from the beginning (^) to the end ($). When I use search and replace in AP, I get the whole text as a single result, because it includes all the line ends. See attached screenshot.
  10. I would also prefer templates over write-protection. Sadly, mac os handles write protection pretty strangely. E.g. you can't move a folder that has a protected file inside. It’s not like write-protection but more like a complete lock inside the file tree.
  11. I couldn’t find something about this. Is it possible to hide the pink outline of text in AD? I know it is hidden when pressing the spacebar, but I don’t need it at all, and it always distracts me.
  12. I think scripting support would be a wonderful feature. I would love a good documented API, maybe even a well done scripting environment (persona?) with an included library/documentation. As of languages I would prefer something fast to write and easy to read like python, maybe even something eloquent like ruby. Javascript has a hideous code structure (things like }); are completely normal), though there are also many pros for JS. But maybe think about making scripting more accessible for the average user. There definitely are ways of doing this, if one is willing to go there. Drag and dropable scripting may be possible, or even node-based programming like NodeBox. Well, this should of course not replace normal scripting, but extend it and let more users be able to use the capabilities of scripting.
  13. This is definitely not one of the most important features, but as a GREP-engine is already implemented: may we hope for something like GREP-Styles? This is a feature I don’t use on a daily basis, but it is something I’m very very glad to have from time to time.
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.