Again, every time I try a new version of Scrivener, I expect that the phrase ‘default font’ will have a single, universal meaning throughout the editor (that’s the portion where you type your document text).
The problem with your explanations are that you have an almost unlimited number of various scopes where ‘default font’ might have a different meaning. But rarely is the manner or extent of how a user has or must make such a applicable selection made clear in any support discussion.
So… if I go to the Top-level Menu: Project/Project Settings, click the Aa icon, select a font name, font face, font size, and line spacing, and then click ‘use a different default font formatting for new documents in this project’, then I would expect that means that for every new document, Scrivener would necessarily use a default font that is ‘different’ from the font settings I just chose, as in ‘different default from what?’.
Moreover, that text instruction would indicate to me that you mean that new documents could have any unknown, unselected, undefined combination of font settings, as long as it was different in one or more ways from the font settings I selected seconds earlier. That is, selecting the ‘use a different default font formatting…’ option will produce any variation of font settings for every new document, except the one I selected. Therefore the result will be non-deterministic.
This is apparently how your application works, because if, after selected a 'default font setting, I apply the '\Documents\Convert\Text to Default Formatting menu item, the result is that the text in any selection of ‘scrivenings’ in the binder changes to a font formatting that always differs in one way or another from the font i selected in the \Project\Project Settings\ font settings I have chosen.
So the unspoken, critical explanation of how to select a ‘default scope’ is required as a PRE-requisite in any discussion regarding ‘default font formatting’. And therefore the explanations from your experts, which also fail to identify the scope issue clearly by using the word scope, or identifying the range of the various scopes that need to be understood as distinct ‘default scopes’ (ever, apparently), produce an inherent misunderstanding of the problem in every explanation of each solution offered.
So my presumption would be that if I go to the project\protect settings, select some font settings, and select the misrepresentative option of ‘use different font formatting for new documents in this project’ and its integrated button, ‘Main text formatting’ -> ‘Use Current’, [Please notice how both these phrases are different from any other description in the docs, are ambiguous as to their references, as well as to sequence, application intent, consequence, content scope, and temporal scope.]
…then I can expect:
- That ALL new documents would have the font settings I chose in Project\Project Settings
- That the \Documents\Convert\Text to Default Formatting would result in all text within all scrivenings that are in a selected state either in the binder or the editor view, since the binder and editor are an integrated component.
Further, in all responses to questions about these aspects of the behavior of the application, you want to obtain a user’s ‘story’ about what has happened to them in their most recent attempt to pick their way through these scattered ambiguities in your documentation. Your responses to these stories are never authoritative, always logically dependent on the uninformed or mis-apprehended perspective of the user, and therefore, at best, useless for other users, or worse, for anyone trying to discern your application’s intent and standard operations.
So… could you please provide a targeted, reliable, detailed description of the interactions of the features in the Project\Project Settings features that will consistently enable the selection of what will be applied to as ‘default text’.
Also, please be sure to include the necessary steps that a user must follow to select scrivenings, headings, and ‘documents’ represented in the Binder as Files and Folders, and their text representations in the Editor, in order to move to the steps in the \Documents\Convert\Text to Default Formatting.
And also provide a similarly accurate set of operations to be able to utilize that Feature, and be confidently, and immediately aware of the full and detailed scope of the files, documents, and headings (pieces of a scrivening) that have been and those that have not been affected by the application of the ‘default text formatting’ which is identified in those two areas of your application: the Project\Project Settings features and the Documents\Convert\text to Default Formatting.
And please note that pointing toward your documentation is not acceptable as an answer because those documents approach the aspects of your application features in a sequential UI-ordered manner and not in an goal-oriented, organized, business-process manner. And only that manner can produce a user-context-aware explication of the specific problem I have outlined here.
Since this question has been asked by me and many, many others over the past ten or more years, and you continue to fail to grasp the meaning or the extent of these repeated questions or how miserably your many half-hearted attempts to provide a ‘back-of-the-match-book’ solution have failed, I would appreciate a serious attempt to review and redress this long-standing confusion between your users and your designers despite our willingness to continue to fund your operation.
Thanks,
Kimball Johnson