On Sat, Apr 21, 2012 at 9:42 AM, Clay Leeds the.webmaes...@gmail.comwrote:
On Apr 20, 2012, at 1:36 AM, Pascal Sancho pascal.san...@takoma.fr
wrote:
But there has to be a better way. Can we, as a start, change the CSS file
xmlgraphics.css so it doesn't have body {color: white;}?
Note
On Apr 20, 2012, at 1:36 AM, Pascal Sancho pascal.san...@takoma.fr wrote:
Hi,
great job, Clay!
I've looked at the compliance page closer, and it seems that rendering
doesn't support markdown extras (like table or headerid), when it is said
here [1] that such features are enabled for the
Hi,
great job, Clay!
I've looked at the compliance page closer, and it seems that rendering
doesn't support markdown extras (like table or headerid), when it is
said here [1] that such features are enabled for the CMS.
As a workaround, we can insert html markup inside the markdown, I tried
On 19/04/2012 02:02, Clay Leeds wrote:
I replaced the logo for all sites a month or so ago.
Thanks Clay - I can see the new logo fine. I was referring to the TM
characters in the text. I can see it everywhere except the top level XML
Graphics home page, which is a page I definitely changed.
On Thu, Apr 19, 2012 at 12:40 AM, Chris Bowditch bowditch_ch...@hotmail.com
wrote:
On 19/04/2012 02:02, Clay Leeds wrote:
I replaced the logo for all sites a month or so ago.
Thanks Clay - I can see the new logo fine. I was referring to the TM
characters in the text. I can see it
On Tue, Apr 17, 2012 at 7:52 AM, Chris Bowditch
bowditch_ch...@hotmail.comwrote:
BACKGROUND:
We are discussing moving XML Graphics web site to ASF-CMS. You can see
progress here:
http://xmlgraphics.staging.**apache.org/http://xmlgraphics.staging.apache.org/
I realize its work in progress
On 18/04/2012 07:24, The Web Maestro wrote:
Hi Clay,
On Tue, Apr 17, 2012 at 7:52 AM, Chris Bowditch
bowditch_ch...@hotmail.com mailto:bowditch_ch...@hotmail.com wrote:
BACKGROUND:
We are discussing moving XML Graphics web site to ASF-CMS. You
can see progress here:
On Apr 18, 2012, at 5:12 AM, Chris Bowditch bowditch_ch...@hotmail.com wrote:
On 18/04/2012 07:24, The Web Maestro wrote:
Hi Clay,
I added the logo (in GIF, JPG, PNG SVG formats... ;-)
Thanks, but I don't yet see it on the staging website. Is there a delay
before that appears?
On 18/04/2012 13:52, Clay Leeds wrote:
On Apr 18, 2012, at 5:12 AM, Chris Bowditchbowditch_ch...@hotmail.com wrote:
On 18/04/2012 07:24, The Web Maestro wrote:
Hi Clay,
I added the logo (in GIF, JPG, PNG SVG formats... ;-)
Thanks, but I don't yet see it on the staging website. Is there a
I replaced the logo for all sites a month or so ago.
I'm not at a place I can publish, but if someone can publish the PRODUCTION
sites, the logo will show up (be sure to clear cache!).
Clay
My religion is simple. My religion is kindness.
- HH The Dalai Lama of Tibet
On Apr 18, 2012, at 7:09
On 15/04/2012 19:52, The Web Maestro wrote:
I just added most of the nav for FOP Development (0.95, 1.0, trunk/
and 'dev'):
Hi Clay,
http://xmlgraphics.staging.apache.org/
As mentioned, there are likely missing things (like java-docs,
download.cgi, Batik's DEMO, etc.)... It'd be great if
NOTE: Moving discussion to general@. Please make all further responses to
general@.
BACKGROUND:
We are discussing moving XML Graphics web site to ASF-CMS. You can see progress
here:
http://xmlgraphics.staging.apache.org/
ToDo:
- Lots.
- Style templating work
- Non-HTML content (figure out
On 17/04/2012 14:59, Clay Leeds wrote:
NOTE: Moving discussion to general@. Please make all further responses to
general@.
Hi Clay,
Thanks for moving to general@
BACKGROUND:
We are discussing moving XML Graphics web site to ASF-CMS. You can see progress
here:
I've updated the docs a bit, and gotten much (but not all!) of the FOP,
Batik Commons content into the CMS...
We're still missing an adequate navigation system, so I did a preliminary
job of getting a few links in the sidenav, but it's incomplete and ugly as
sin. We'll need to build a mechanism
I just added most of the nav for FOP Development (0.95, 1.0, trunk/ and
'dev'):
http://xmlgraphics.staging.apache.org/
As mentioned, there are likely missing things (like java-docs,
download.cgi, Batik's DEMO, etc.)... It'd be great if folks could take a
look... I haven't figured out how to add
On Sun, Apr 15, 2012 at 12:52 PM, The Web Maestro
the.webmaes...@gmail.comwrote:
I just added most of the nav for FOP Development (0.95, 1.0, trunk/ and
'dev'):
http://xmlgraphics.staging.apache.org/
initial comments:
- the navigation panel on the left needs to start in a collapsed
Thx for the comments Glenn,
On Apr 15, 2012, at 12:50 PM, Glenn Adams gl...@skynav.com wrote:
initial comments:
the navigation panel on the left needs to start in a collapsed mode, and
remember its settings as you move to sub-projects and their descendants;
possibly better would be to limit
On 09/04/12 15:47, Glenn Adams wrote:
On Mon, Apr 9, 2012 at 6:50 AM, Clay Leeds the.webmaes...@gmail.com wrote:
On Apr 8, 2012, at 7:21 PM, Glenn Adams gl...@skynav.com wrote:
Yes, we'd lose the XML-based nature of the documentation. That's a fairly
large loss, but I don't know if that's a
On 12/04/2012 10:09, Vincent Hennebert wrote:
Hi Vincent,
My preference is to keep things as simple as possible. If keeping the
docs in xdoc format complicates the publishing process, then I’m not in
favour of it.
In particular, I’d like to remove the dependency on Forrest. Publishing
with
On Apr 12, 2012, at 6:41 AM, Glenn Adams gl...@skynav.com wrote:
Agreed that removing forrest dependency is desirable. However, presumably the
current xdocs would need to be converted to MD, in which case someone will
need to construct an XSLT to do so. That begs the question of whether it
On 09/04/2012 15:47, Glenn Adams wrote:
Hi Glenn, Clay,
On Mon, Apr 9, 2012 at 6:50 AM, Clay Leeds the.webmaes...@gmail.com
mailto:the.webmaes...@gmail.com wrote:
On Apr 8, 2012, at 7:21 PM, Glenn Adams gl...@skynav.com
mailto:gl...@skynav.com wrote:
Yes, we'd lose the
On Apr 8, 2012, at 7:21 PM, Glenn Adams gl...@skynav.com wrote:
Yes, we'd lose the XML-based nature of the documentation. That's a fairly
large loss, but I don't know if that's a showstopper, considering the
benefits of having CMS-based documentation.
What prevents you from using the
On Mon, Apr 9, 2012 at 6:50 AM, Clay Leeds the.webmaes...@gmail.com wrote:
On Apr 8, 2012, at 7:21 PM, Glenn Adams gl...@skynav.com wrote:
Yes, we'd lose the XML-based nature of the documentation. That's a fairly
large loss, but I don't know if that's a showstopper, considering the
benefits
On Fri, Mar 30, 2012 at 8:55 AM, Glenn Adams gl...@skynav.com wrote:
On Fri, Mar 30, 2012 at 7:00 AM, Clay Leeds the.webmaes...@gmail.comwrote:
Makes sense to me. However, I don't think it's necessary to have all
documentation as such. Perhaps just the Day to day stuff can be translated
On Sun, Apr 8, 2012 at 7:45 PM, The Web Maestro the.webmaes...@gmail.comwrote:
So if you can find a way to transition to CMS as the doc management
system while still reusing the existing source formats and output formats
(modulo the above), then I have no objection to that.
Yes, we'd lose
Makes sense to me. However, I don't think it's necessary to have all
documentation as such. Perhaps just the Day to day stuff can be translated
(things that are more likely to change).
That's my current plan, anyway (although I don't yet know how to make that
happen). Ye olde documentation
On Fri, Mar 30, 2012 at 7:00 AM, Clay Leeds the.webmaes...@gmail.comwrote:
Makes sense to me. However, I don't think it's necessary to have all
documentation as such. Perhaps just the Day to day stuff can be translated
(things that are more likely to change).
There aren't too many docs
On Thu, Mar 29, 2012 at 10:22 PM, Glenn Adams gl...@skynav.com wrote:
I also feel it is very important to continue using FOP documentation to
create *some* output format. I am not prepared to give up our dog food,
as that provides one more set of tests on FOP, that would otherwise be
missing.
28 matches
Mail list logo
