I do grasp this distinction, at least. With *Save As*, when the save is done you end up in the saved outline, which would have a different name or path from the original. With *Save To*, you stay in the original outline. I don't know an alternative wording to suggest, but I don't think this usage speaks for itself very clearly.
On Wednesday, January 12, 2022 at 2:52:46 PM UTC-5 viktor....@gmail.com wrote: > Minor correction: It should be SQLite. - See https://www.sqlite.org/ > > 3. Is there a difference between *Save As...* and *Save to...*? If so, *Save >>> To ...* needs some wording to make it clear what it will do that's >>> different. >>> >> >> "Save As" and "Save To" are different. I think the terminology is fairly >> widespread. >> >> "Save As" saves the outline to a different name, and also changes the >> name of the outline to that new name so that a later "Save" will save the >> outline to the new name. "Save To" saves the outline to a different name, >> but leaves the name of the outline unchanged. >> >> I don't want to change the name of these menu items. >> > > Searching for "Save As [and/or/versus] Save To" does not return any > relevant results for me ... > > I re-read your explanation multiple time - but - failed to get the use > case, when & why "Save To" is really needed :-( > > Can you please explain the need for it once more. - TIA! > > With kind regards, > > Viktor > > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/a92b8d5d-8426-439e-83b7-278cf5817981n%40googlegroups.com.
