On 07/30/2018 10:29 PM, Matthew R. Trower wrote:
Chase via cdesktopenv-devel
writes:
The reason I chose opensp instead of sp is simply because when I tried
installing sp on Lubuntu, it gave me an error saying "Package sp has
no installation candidate", although it is in the debian repos, so I
Yes, what Matthew said below is the way to go - you don't have to throw
everything away and start over from scratch -- though you will need to
start a new, clean branch from master and "construct and maintain" it
properly as Matthew outlines below.
It is important to rebase from time to time a
I guess we should at some point discuss the whole SGML infrastructure in
CDE.
http://tldp.org/HOWTO/DocBook-Demystification-HOWTO/sgml.html
This link provides a decent 'demystification' of docbook and where it is
going.
http://tldp.org/HOWTO/DocBook-Demystification-HOWTO/
XML is the current
On Tue, 31 Jul 2018, Jon Trulson wrote:
> So - is anyone on this list familiar with docbook XML want to take up the task
> of upgrading our documentation format and generation to something from this
> decade?
>
> Short term, using a new onsgmls is probably the way to go, but long term, it
> seems
I guess I'm just having trouble understanding what I must do differently, does
my patch simply need to be rebased and the commits deleting dtudcfonted can be
reversed on your end, or do I need to manually readd all the previous files by
hand from a previous version and repatch? Because one solut
On 07/31/2018 04:59 PM, Marcin Cieslak wrote:
On Tue, 31 Jul 2018, Jon Trulson wrote:
So - is anyone on this list familiar with docbook XML want to take up the task
of upgrading our documentation format and generation to something from this
decade?
Short term, using a new onsgmls is probably t
To answer a previous question you posed, It worked fairly well, with one minor
problem that dtinfogen keeps throwing a very nondescript error of "dtinfogen:
sgmls not found
make[4]: *** [usersGuide/TOC.sgm] Error 255"
Thank you for your time,
-Chase
‐‐‐ Original Message ‐‐‐
On July 31,
On 07/31/2018 06:55 PM, Chase wrote:
To answer a previous question you posed, It worked fairly well, with one minor
problem that dtinfogen keeps throwing a very nondescript error of "dtinfogen:
sgmls not found
make[4]: *** [usersGuide/TOC.sgm] Error 255"
Ok, so creating the guides was broken
Surprisingly no, the man pages and the other docs wrote without a hiccup.
Thank you for your time,
-Chase
‐‐‐ Original Message ‐‐‐
On July 31, 2018 8:01 PM, Jon Trulson wrote:
> On 07/31/2018 06:55 PM, Chase wrote:
>
> > To answer a previous question you posed, It worked fairly well, w
Chase writes:
> I guess I'm just having trouble understanding what I must do
> differently, does my patch simply need to be rebased and the commits
> deleting dtudcfonted can be reversed on your end, or do I need to
> manually readd all the previous files by hand from a previous version
> and rep
Did you try running dtinfo and looking at some of the guides? That's
definitely an error... Maybe you had a previous install already there?
Anyway, I'm just guessing, but it would fail the build (the make[4]: ***
[usersGuide/TOC.sgm] Error 255" line).
-jon
On 07/31/2018 07:03 PM, Chase wrote
I think Matthew explained it pretty well. You might do some reading up
on git, and typical git workflows - there's tons of docs out there.
But essentially:
You create a branch from current master, revert the 2(?) previous
commits that removed dtudcfont* programs (look at the "git revert"
com
Ahh now I see, thats what I did the first time, so I need to commit the reverts
as well? Because I did revert the commits on my side. Everything works without
errors, just compiler warnings.
Thank you for your time,
-Chase
‐‐‐ Original Message ‐‐‐
On July 31, 2018 8:28 PM, Jon Trulson
On 07/31/2018 07:31 PM, Chase wrote:
Ahh now I see, thats what I did the first time, so I need to commit the reverts
as well? Because I did revert the commits on my side. Everything works without
errors, just compiler warnings.
When you do a revert, it will add a new commit that undoes the c
Jon Trulson writes:
> Not a clue. I think ultimately we would want it to generate HTML and
> just use a web browser for both help and the guides.
I'd really hate to see that.
* DtInfo is part of CDE.
* DtInfo (like all of CDE) is very lightweight.
* DtInfo provides index and search capabilit
On 07/31/2018 07:53 PM, Matthew R. Trower wrote:
Jon Trulson writes:
Not a clue. I think ultimately we would want it to generate HTML and
just use a web browser for both help and the guides.
I'd really hate to see that.
* DtInfo is part of CDE.
* DtInfo (like all of CDE) is very lightweig
Jon Trulson writes:
> On 07/31/2018 07:53 PM, Matthew R. Trower wrote:
>> Jon Trulson writes:
>>
>>> Not a clue. I think ultimately we would want it to generate HTML and
>>> just use a web browser for both help and the guides.
>>
>> I'd really hate to see that.
>>
>> * DtInfo is part of CDE.
>>
17 matches
Mail list logo
