trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: April 2012

Re: [trinity-devel] kate - misc Naming and File Selector issues needing fixes

From: Darrell Anderson <humanreadable@...>
Date: Wed, 25 Apr 2012 16:32:35 -0700 (PDT)
>   While waiting on the rebuild of tdelibs and tdebase
> with full symbols, I was poking around in kate and came up with another couple of
> fixes that are needed.
> 
>   The first is a simple khelpcenter name change for
> Settings > Application > File Selector. The khelpcenter name for this section is 'The
> Filesystem Browser Page' instead of being the 'The File Selector Page'.
> 
>   It looks like there was a name change somewhere along
> the way that was never implemented in the help files. Looking at the other entries
> in the help file, they correspond fairly closely to the settings dialog. Here
> are some other changes for the help file needed just to dot [i]s and cross
> [t]s:

All help files need a thorough review. As a group I don't know how we are going to perform those reviews. There is a lot of grunt work involved. People need to read, compare to the actual app settings, validate statements and claims, etc.

Not to mention that the translated versions are in worse shape.

I have done a bunch of cleanup, yet we have no style guide to guide everybody.

I want to implement a simple policy of not updating the docbook sources to use the new version/date entities unless the contents have been reviewed and updated. The entities provide a dynamic means of reflecting the current release number (R14) and release date.

That means each handbook retains its static version and release date information, such as version 0.1, released Jan. 2001. That will be our notice to ourselves (and users) the document has not bee reviewed and updated.

I'm using the entities for three or four help files. I have started reviewing those documents. Under my proposed policy I should not be using the entities, but I need a few files using those entities to ensure they are working and compiling correctly.

There really is no way to update the help guides unless everybody in the entire Trinity community decides to help. There is too much for only three or four of us to handle. Doesn't matter who picks which document to review and validate --- they all need desperate attention.

Darrell