Jump to content

Peter Kahrel

Members
  • Posts

    29
  • Joined

  • Last visited

Everything posted by Peter Kahrel

  1. The important part in ChatGPT's promise is 'analyze, learn'. Before it can actually generate working scripts it needs lots of examples, which must necessarily be written by humans. Compare with InDesign: when you ask ChatGPT for a JavaScript to do this or that in InDesign, it gives you an ExtendScript, not a UXP script, because there are zillions of ExtendScripts around and (by comparison) hardly any UXP scripts.
  2. Sounds very sensible, pleased to hear it. Can you say when there'll be something for us to play with? Thanks, Peter
  3. > Our priority for scripting is Photo and things like developing RAW files, adding meta data, . . . etc. > Creating documents and text processing is 'pretty', but it's of zero interest to us compared to the aforementioned raw and image processing which happens every minute of every day and is where the real time savings are. What complete nonsense. Processing text documents can be as time-consuming (or even more so than) whatever you you do in Photo. If you can't automate various typesetting aspects you'll lose a lot of time.
  4. > Those of us who would love to experiment with it early would send an invaluable feedback to the devs, which in my opinion is as important as the release itself. And those who love living on the edge would start using it early and learn what works what what doesn't. Absolutely. Good point.
  5. > I must say thank you for the great book. Glad to hear it!
  6. @Tim France Many thanks for the progress report. > Naturally we've been exposing more of the apps' functionality to scripts I hope the ultimate aim is to expose all the app's functionality to scripting. Can you say anything about that? When you expose only part of the app's functionality you have to make a choice -- you'll always get it wrong.
  7. That's why a road map of planned features would be useful. P.
  8. That's true. But in InDesign you could do footnotes 'manually' because you could script them.
  9. @GabrielM -- I don't have any particular project file, but it's easy to recreate. In a text frame, type xxx, press Enter/Return, and type zzz (but don't press Enter/Return). Now search .$ (any character at the end of a line). This expression should match first the last x, then the last z. But the last z is not found. Peter
  10. Well, yes, but the ones in Miscellaneous are toggles for panels, not text. P.
  11. Search results of expressions that use lookahead and/or lookaround aren't processed correctly. Search results are displayed in the Find panel, but they are not highlighted in the text and cannot be changed by a replacement text. This is the case with lookahead (?=...), the classic lookbehind (?<=...), and the modern, variable-length, lookbehind, \K P.
  12. Yes, confirmed. The matches are displayed but not highlighted. And i reported the bug. Looks like a general problem with location markers (lookarounds are a kind of location marker). P.
  13. That symbol is the section sign, it indicates the end of the story. P.
  14. Confirmed: the\b shows the match (with context) in the display panel, but the match isn't highlighted, isn't highlighted when you click the displayed item in the panel, and replace doesn't work either. Refreshing the search panel with another search doesn't improve anything. Peter
  15. Thank you, Walt, found it. But since in the interface the item is in the Text menu, I'd have expected it to be in the Text section in the KBSC editor. Miscellaneous would be for things that aren't available in the interface, such as a shortcut (like InDesign's) to activate the last used entry field in panel, a shortcut to close all documents, etc. P.
  16. > There's already an indication. True. But a single button to clear the dialog is still useful. Especially if a previous find/change used a space character as the replace text: you can't see that. P.
  17. In the Keyboard shortcuts editor you can assign shortcuts to a selection of menu items. I think all menu items should be selectable. For example, the Text menu has the useful item 'Toggle unicode'. But that could be made so much more useful if we could assign a shortcut to it. P.
  18. \b works only at word beginning. Given a word 'the' in the text, \bthe matches the\b does not match P.
  19. $ matches the end of a paragraph only when the paragraph ends in a return character. The last paragraph in a story, when it doesn't end in a return, is ignored. P.
  20. Great, thank you. It's incomplete (e.g. no lookahead and lookbehind yet) and still a bit buggy (bug reports submitted), but it's early days and I look forward to a full implementation. P.
  21. > Some search characters get replaced with an icon. I think that is helpful. I disagree. Those icons take a lot of space and you have to select them from a dropdown every time. They should have text equivalents, such as \r for line break. If Affinity get serious about providing scripting support, text equivalents of those icons are needed anyway. > Maybe a little "reset format" button that only shows up when there is a format set. Yes, that would be very useful. P.
  22. InDesign uses the Boost libraries for its GREP. Those are probably Perl-compatible -- InDesign's GREP is very powerful. InDesign's JavaScript (ExtendScript), however, uses standard JS regular expressions, much less powerful than InDesign's (e.g. no lookbehind, no Unicode properties). Peter
  23. Seconded. Optical kerning is useful to a degree, but the ability to add custom kerning pairs is essential. Quark has that possibility, it's a great feature. Zoot quoted Affinity as saying "We provide kerning based on tables in the font file. As these are pretty well supported by fonts, doing anything more isn't a priority at the moment." Well, Affinity, think again.
×
×
  • 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.