On 5/17/26 03:09, Georg Zotti wrote:
> I don't see the problem. If a previous Mac bundle was found "guilty" of including an outdated Guide, just make sure to build the current PDF before packaging the next bundle. Some Makefile rules can probably be helpful. But I don't pack Mac bundles, so have no details. In any case, a current Guide is always available also as separate download.
> ...
Alexander has a valid concern of "ability of simple use". If it is desirable for
performance and economy of bandwidth to keep guide.pdf locally, then
the Help.>About window should contain a hyperlink:
<file:///Applications/Stellarium.app/Contents/Resources/guide/guide.pdf>
That's Mac-specific. It would be different for each platform.
If it's preferred to leave guide.pdf on the web site, that
hyperlink in the Help.>About window should be:
<
https://stellarium.org/files/guide.pdf>
For users who desire a local guide.pdf in a Documents folder, many
browsers and other tools support downloading given a URL.
My long-standing concern with "ability of simple use". has
been the Command Line Interface for Mac OS. Guide.pdf
has only hyperlinks to the sparse:
5.1.2 macOS
installation directory This is found inside the application
bundle, Stellarium.app. See The Anatomy of macOS
App Bundles4 or Bundle Programming Guide5 for more
information.
The instructions should be complete.
>
alex....@gmail.com schrieb am Sonntag, 17. Mai 2026 um 11:02:45 UTC+2:
>
> In any way - if someone can share documents for correct incorporation the PDF files within macOS bundle with ability of simple use that PDF - pleas do it!
>
--
Thanks,
gil