Op vrijdag 14 september 2018 16:55:33 CEST schreef David T. via gnucash-devel:
> Hello,
>
> As I am toiling through the depths of the documentation generation process,
> I am struck by the fact that the base page of the Help is “help.html”,
> while the base page for the guide is “index.html”.
>
Interesting. I’ll investigate. I’ve never had an issue that I’m aware of. If
the server won’t even let you get there due to the directive...?
Regards,
Adrien
> On Sep 14, 2018, at 5:38 PM, John Ralls wrote:
>
> It's my understanding that that's less than perfect. It's standard practice
> in
David,
A couple of points.
Why not put this directly into the new chapter in the Guide, rather than into
the Help? This is precisely the kind of detailed information that belongs IMHO
in the Guide rather than Help. I know it’s not in Maint yet, but it will be
shortly.
Next, in the interest
David ,
I have completed the import section as an addition to the Help manual CH
6. I have put a pull request to gnucash-docs on Github to incorporate it
into maint as the changes for the multiple selection may possibly go into
the next release.
Once it has been pulled into the main Github
We're probably pretty compliant with the Gnome 2.0 HIG, but the Gnome HIG has
changed over the years and GnuCash's UI hasn't. Just switching to Gtk3 probably
got us some updates just because Gtk is what implements the HIG, but that would
have been largely inadvertent.
For the purposes of the
> On Sep 14, 2018, at 9:24 AM, Adrien Monteleone
> wrote:
>
>
>
>> On Sep 14, 2018, at 11:10 AM, John Ralls wrote:
>>
>>
>> We should change the name of gnucash-guide/index.html, but we should also
>> insert an index.html into every directory that raises an error to prevent
>> direct
Hello,
In the course of another arduous and lengthy thread, the question of the Gnome
HIG came up. I attach the text in question below.
My question is whether the Guide needs changing at 1.2.1, where it says:
Easy to Use Menus: GnuCash menus conform to the GNOME Human Interface
Guidelines.
Sure. I defer to you. I was merely trying to anticipate that removal of
“index.html” in the guide would cause some disruption.
> On Sep 14, 2018, at 12:10 PM, John Ralls wrote:
>
>
>
>> On Sep 14, 2018, at 7:55 AM, David T. via gnucash-devel
>> mailto:gnucash-devel@gnucash.org>> wrote:
>>
> On Sep 14, 2018, at 11:10 AM, John Ralls wrote:
>
>
> We should change the name of gnucash-guide/index.html, but we should also
> insert an index.html into every directory that raises an error to prevent
> direct browsing; user access should be via https://www.gnucash.org/docs.phtml
>
> On Sep 14, 2018, at 7:55 AM, David T. via gnucash-devel
> wrote:
>
> Hello,
>
> As I am toiling through the depths of the documentation generation process, I
> am struck by the fact that the base page of the Help is “help.html”, while
> the base page for the guide is “index.html”.
>
>
Ok, ok. You win.
I surrender.
On September 14, 2018, at 11:57 AM, John Ralls wrote:
On Sep 14, 2018, at 8:34 AM, Geert Janssens wrote:
Op vrijdag 14 september 2018 17:13:44 CEST schreef John Ralls:
On Sep 14, 2018, at 7:38 AM, David T. via gnucash-devel wrote:
On Sep 14, 2018, at
> On Sep 14, 2018, at 8:34 AM, Geert Janssens
> wrote:
>
> Op vrijdag 14 september 2018 17:13:44 CEST schreef John Ralls:
>>> On Sep 14, 2018, at 7:38 AM, David T. via gnucash-devel de...@gnucash.org> wrote:
On Sep 14, 2018, at 10:28 AM, Frank H. Ellenberger
wrote:>>
Am
Op vrijdag 14 september 2018 17:13:44 CEST schreef John Ralls:
> > On Sep 14, 2018, at 7:38 AM, David T. via gnucash-devel wrote:
> >> On Sep 14, 2018, at 10:28 AM, Frank H. Ellenberger
> >> wrote:>>
> >> Am 14.09.18 um 15:57 schrieb David T. via gnucash-devel:
> >>> For fullest consistency, I
> On Sep 14, 2018, at 7:38 AM, David T. via gnucash-devel
> wrote:
>
>
>
>> On Sep 14, 2018, at 10:28 AM, Frank H. Ellenberger
>> wrote:
>>
>>
>>
>> Am 14.09.18 um 15:57 schrieb David T. via gnucash-devel:
>>> For fullest consistency, I would opt to have each of the formats placed in
Hello,
As I am toiling through the depths of the documentation generation process, I
am struck by the fact that the base page of the Help is “help.html”, while the
base page for the guide is “index.html”.
For consistency, I suggest naming the guide base page “guide.html”; moreover, I
suggest
> On Sep 14, 2018, at 10:28 AM, Frank H. Ellenberger
> wrote:
>
>
>
> Am 14.09.18 um 15:57 schrieb David T. via gnucash-devel:
>> For fullest consistency, I would opt to have each of the formats placed in
>> their own folder, named for tehir format:
>>
>> epub *
>> html
>> mobi *
>> pdf *
Am 14.09.18 um 15:57 schrieb David T. via gnucash-devel:
> For fullest consistency, I would opt to have each of the formats placed in
> their own folder, named for tehir format:
>
> epub *
> html
> mobi *
> pdf *
*: Why do you want to create a directory for one file?
>
> (adding
John,
> On Sep 14, 2018, at 10:11 AM, John Ralls wrote:
>
>
>
>> On Sep 14, 2018, at 4:49 AM, D via gnucash-devel
>> wrote:
>>
>> That seems odd; the install page at Apache says it's a java app, and
>> installation consists of copying jar files. No mention of /usr/bin...
>>
>>
Frank, Geert,
I am finally following up on this thread, and I’d like to note that the
information that Frank says “got lost,” and which Geert has re-entered on this
page were actually moved to a different page
(https://wiki.gnucash.org/wiki/Initializing_Documentation_Build_Environment
> On Sep 14, 2018, at 4:49 AM, D via gnucash-devel
> wrote:
>
>
>
> On September 14, 2018, at 1:59 AM, "Frank H. Ellenberger"
> wrote:
>
>>
>> Am 14.09.18 um 03:55 schrieb David T. via gnucash-devel:
>>> OK, so I thought it would be nice to look at the changes I am implementing
>>> in
Geert,
> On Sep 14, 2018, at 3:17 AM, Geert Janssens
> wrote:
> This was done to be able to separate html output from the other formats.
>
> pdf, ebub and mobi all output one single file. html outputs a whole series of
> files. Putting those in their own directory creates one entry point per
I saw that option before, but having gone the Fink route in the past, I had
hoped not to incur the overhead (both computing and psychic) that those tools
impose.
I bit the bullet and gave Brew a try. It wasn’t difficult at all, and fop now
works. Thanks for reminding me.
David
> On Sep 14,
David,
fop is available via Homebrew for Mac. I don’t use Fink or MacPorts so can’t
speak for them.
Perhaps that route will prove fruitful.
Regards,
Adrien
> On Sep 14, 2018, at 6:49 AM, D via gnucash-devel
> wrote:
>
>
>
> On September 14, 2018, at 1:59 AM, "Frank H. Ellenberger"
>
On September 14, 2018, at 1:59 AM, "Frank H. Ellenberger"
wrote:
>
>Am 14.09.18 um 03:55 schrieb David T. via gnucash-devel:
>> OK, so I thought it would be nice to look at the changes I am implementing
>> in the documentation in PDF format, since I am rather old school, and like
>> to see
Op vrijdag 14 september 2018 04:05:14 CEST schreef David T. via gnucash-devel:
> Hello,
>
> In trying to deal with compiling the documentation, I have been trying to
> use the newer “make” methods for building the html docs. I am wondering why
> these commands create the output in a new directory
Am 14.09.18 um 03:55 schrieb David T. via gnucash-devel:
> OK, so I thought it would be nice to look at the changes I am implementing in
> the documentation in PDF format, since I am rather old school, and like to
> see the changes in a print format.
>
> I went to the wiki, and followed the
26 matches
Mail list logo
