Jump to content

garrettm30

Members
  • Posts

    1,410
  • Joined

  • Last visited

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thank you for your comments. I would like to suggest this minor tip in regard to what you said here: Pasting into TextEdit is one extra step than needed. You need only copy from Publisher (or from wherever) and then use the “Copy corrected text” command (or its shortcut) from Antidote’s menu bar menu. I guess it depends on which platform you are, but this is what I am referring to (from Druide’s manual): It’s still a big difference from the integration we are asking for, but maybe one fewer step will help until better things come along. And for those that seem to think we are asking for Serif to cater to a niche group, please understand we are not really asking for Serif to provide Antidote integration but rather a general API for third-party integration, so Druide can do their part, as they have already indicated they are willing to do. This way, many different niche and not-so-niche needs can be met while Serif moves on to other things.
  2. Quite right, and thank you for pointing it out. I always enjoy your comments on language, even those you label as “pedantry” (or perhaps especially those).
  3. Hi all, Not that any defense of Antidote is really necessary in the context of an Affinity forum, but I have found Antidote so very helpful over the years that I feel it worth a little time to put in my “two cents” on its behalf. First, it may be helpful to know that French is Antidote’s forte, and in fact it supported French only until English was added more recently. It seems that most of us (if not all) who are asking for integration are using it for French. Despite Druide’s very hard work, it may be that their English side has not yet come to the same level of maturity, though from what I have seen there is tremendous value in even the English side. Knowing that this software starts with French can also explain the nature of the text on the website, as it almost certainly started in French (and translations, for those who do not know, can often read like translations, depending on the skill of the translator and how freely he is permitted to amend the text for the benefit target language). For example, the sentence Old Bruce pointed out makes more sense to me in its French original: “Après l’orthographe et la grammaire, corrigez la typographie et le style, dont les répétitions et les verbes ternes.” The problem is with the use of the word “correct” in English, and that brings me to the point of what Antidote is and what it is not. The Antidote corrector* is a tool and a resource, but it is not an editor. It helps identify numerous errors of the sort that computer programs can be good at: think not only spell-check but things such as conjugations and agreement, both of which are more complex in French than in English and so mistakes are easy to make and overlook in proofreading. These kinds of mistakes are not corrected by spell-check alone but are something that computer software can be good at. What people in this thread have drawn attention to are matters of style, and there, it is harder to make software do a good job. Antidote does offer tools of style, such as identifying repetitions, excessive passive voice, etc., but it can’t really tell you whether a sentence reads correctly. That is where human editors come in. *(The corrector is only part of Antidote. Not to forget that the value of the resource side of Antidote is massive and replaces multiple expensive printed volumes on several grammatical, lexical, and stylistic matters, but the integration with Affinity mostly has to do with the corrector.) Let’s return to the problem sentence identified by Old Bruce: As a computer program, Antidote could understand that as a perfectly grammatical sentence. But as humans, we find it awkward because of the ambiguity of the word “correct,” which is spelled identically as either an adjective or as a verb (here as a 2nd person imperative). If it is an adjective, it has this meaning: After spelling and grammar, typography and style that are correct, including repetitions and dull verbs. If that is the meaning, then there is no verb in the sentence. As our mind goes along, it encounters a hiccup of understanding where it may well be inclined to first parse “correct” as an adjective and then stumble with an incomplete sentence and have to back up and try again by understanding “correct” as a verb: After spelling and grammar, make corrections to typography and style, including repetitions and dull verbs. Indeed, the French original makes clear that “correct” is to be understood as a verb, for in this case there is no ambiguity between “typographie et style corrects” and “corrigez la typographie et le style.” So in this case, a less literal translation would aid in removing the ambiguity for the sake of readability, and Antidote can serve as a helpful resource, but only to a skilled editor who knows how and when to use it as such. But now, if I may return the discussion to how Affinity relates to Antidote: it is admitted that those who use both Antidote and Affinity (especially Publisher) are comparatively few, and so it makes sense that we could not, in my view, reasonably expect Serif to go to great lengths to specifically accommodate Antidote. But that is not really what we need. Instead, we need and are asking for some general framework by which third-party integrations may be made possible. That could be with a plugin system, or it could even be with scripting (which, as you know, has been one of the longtime hot requests), so long as it is built in such a way that it can call external scripts and receive their results. This thread about Antidote really only represents one specific use case for a general framework where countless niche requirements among the many various use cases could be met.
  4. Wow, we've taken quite a turn, but at least it is something we haven't covered before in this 43-page thread!
  5. I should add that before my time (in this forum), Alfred observed a similar mistake in an early Designer beta:
  6. I am viewing Publisher 1.10.5 with language set to “English (United States).” Two misspellings related to the word misspelled itself (oh, the irony!): In the Edit->Spelling submenu, the item “Ignore Misspelt Word” is spelled in its British form rather than as is suitable for the set locale. In US English it should be “Ignore Misspelled Word.” When the spelling of a word is ignored, the History Studio logs it as “Ignore mis-spelt word.” This variety, with the hyphen, is not correct in any variety of English, as best as I am aware, but in any case it is not in the US English locale.
  7. Leading override is useful in character styles when the character style uses a different font with different leading metrics, and when the paragraph it is used in has leading defined as anything other than fixed units. Leading override can then be tweaked to match the surrounding text.
  8. Thanks for the explanation. In the U.S., there are a couple of common standardized tests called the SAT or the ACT that I think serve a similar purpose. Different universities have different requirements as to which test is recognized or even required. Many, for example, require a certain minimum score on one of these tests for entrance, and often very high scores can result in offering of scholarships.
  9. Yeah, I was confused about that too. I just guessed that maybe it was a certain type of educational requirement different from what we have in my own country (U.S.A.). As for William’s example of the word, to me it looks like what one would describe as an “abstract” in research papers.
  10. Wow, what a turn this thread has taken! I might as well throw myself into it, why not? As a native English speaker who speaks French as a second language, I did recognize the word précis from French, but it so happens that I was entirely unfamiliar with it as an English term. The “TL;DR” label, on the other hand, made sense to me. Perhaps this goes with the territory: talking about software on an Internet forum is more in the technical realm, and the latter term is more likely to be recognized. Perhaps the former would be more recognized in academic circles (I do not know). As a practical matter: I do not have any personal interest in the request of this thread, but I do like to see what my fellow forum members are interested in, and as such I do try read even those threads that don’t involve me directly. In such a circumstance, Alfred’s “TL;DR” was quite helpful: it would not be a good use of my time to chase down extra links for things that don’t concern me, so otherwise I would have just skipped them, but thanks to the summary Alfred gave, I was able to glean the key points and follow the conversation, and I did appreciate that he did that. In any case, I see no reason at all why Alfred should edit his “TL;DR,” especially now that if anyone has any doubts at all at what he meant, one needs only read on a few more posts where it is made abundantly clear.
  11. I really like Typeface and use it with Publisher and the others. It does work well, and I have heard it from the developer of Typeface that they also like to use Affinity apps.
  12. I actually ran across a reason to use leading override a few days ago, and I thought about this thread. I, for one, like to keep leading as a paragraph attribute (which seems the logical choice) all while having the potential to override for specific, albeit rare, cases.
  13. I remember listening to an interview of Ashley Hewson wherein he talked about the early days of development for the Affinity line. If I remembered correctly, development actually started on iOS, and as hardware was considerably weak then as compared to today’s standards, the current efficiency of Affinity (at least in Apple hardware) has a lot to do with those early experiences. Ash was talking about how they had to get graphics working well with very limited memory. The point is that iPad was not really an additional platform, but Affinity was developed with it in mind right from the beginning, even though the iPad apps did come out later than the Mac versions. Windows was an additional platform (though I can only assume that Serif probably did intend to make Windows versions from the beginning), and it no doubt took a considerable amount of effort to bring the apps to that different platform. However, the profit potential for that market made the effort worth it when weighed against the resources available to Serif. I would not be surprised if Android does eventually get some apps from Serif. In my estimation, it is just a question of timing. As a company, it is reasonable that they will go where the money is. As the company grows, and as sales of their existing offerings starts to reach saturation, they will naturally ask where they can go next and whether they have or can get the resources to launch off into new territory. Right now, they still do not have Publisher on iPad, and as that is one of their existing markets and an easier goal to obtain than launching any of the Affinity line on additional platform, I would expect that they would prioritize rounding out the trilogy on iPad as their next step. These are all just observations from the outside. You can be sure that Serif has had discussions about which platforms to support and their roadmap for when or if they hope to support such and such a platform. I have merely tried to suggest what seems to be a plausible explanation for what we have seen so far.
  14. A couple of questions: 1. When you quit Publisher, do you first close the documents? In that case, it would not reopen them. Save the documents but do not close them when you quit if you want it to reopen the documents. 2. If you are sure you are leaving open documents when quitting, then it might be worth checking out this system setting indicated below, to see if it makes any difference. Normally apps should follow this system setting, but since Affinity has a setting of its own, I am not sure what the relation between the two will be. It doesn’t hurt to look.
×
×
  • 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.