[jira] [Created] (INCUBATOR-119) site-publish/ip-clearance/lucene-kuromoji.html does not seem to build correctly
site-publish/ip-clearance/lucene-kuromoji.html does not seem to build correctly --- Key: INCUBATOR-119 URL: https://issues.apache.org/jira/browse/INCUBATOR-119 Project: Incubator Issue Type: Bug Components: site Environment: WinXP/SP3 Apache Ant(TM) version 1.8.2 compiled on December 20 2010 Reporter: Sebb Priority: Minor If I delete the file site-publish/ip-clearance/lucene-kuromoji.html and rebuild the site, the generated file has differences from the original. Looks like there might be an encoding issue to sort out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-120) Are the following files still needed in site-publish?
Are the following files still needed in site-publish? - Key: INCUBATOR-120 URL: https://issues.apache.org/jira/browse/INCUBATOR-120 Project: Incubator Issue Type: Bug Components: site Reporter: Sebb Priority: Blocker [This is listed as a blocker because it's not possible to move to svnpubsub/CMS until resolved.] The following files in site-publish have no sources in site-author: The entire tree under: site-publish/projects/altrmi/ Looks like it should be deleted, as the project has gone away. Also the following individual files have no means to recreate them: ! 1243649 site-publish\projects\geronimo\status.html ! 1243649 site-publish\projects\geronimo\status.pdf ! 1243649 site-publish\projects\lcf.html ! 1243649 site-publish\projects\geronimo-proposal.html ! 1243649 site-publish\projects\ruper.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-117) Bootstrap CSS messes up display of a name internal link definitions
Bootstrap CSS messes up display of a name internal link definitions
-
Key: INCUBATOR-117
URL: https://issues.apache.org/jira/browse/INCUBATOR-117
Project: Incubator
Issue Type: Bug
Components: site
Environment:
http://mail-archives.apache.org/mod_mbox/incubator-general/201110.mbox/%3CCAOGo0VbK1Cdqd=bx-cs1rdxxxj6andzalrlu7zwx1e6zbpg...@mail.gmail.com%3E
Reporter: Sebb
Attachments: INCUBATOR-117.patch
[This is to document the fix applied, and a further possible solution]
The new Bootstrap CSS changes the default setting for links, by removing
underlines unless the mouse hovers over the link.
However, this has broken all the internal name definitions. These now look like
links - they are blue, and get underlined when hovered over.
One possible solution to this (thanks Francis!) is to use a Selector, i.e.
a[href] to limit the underline changes.
However this may not be supported by all browsers.
Another is to use
h2 a, h3 a, h4 a, h5 a {
text-decoration: none;
color: black;
}
This would affect real links in headers, but Incubator does not use them.
It would also be possible to change the Anakia stylesheet to use
h3 id='incubator'1. Incubation/h3
rather than:
h3a name=incubator1. Incubation/a/h3
This is arguably how the links should have been generated originally.
However this would generate a lot of changes.
Also, it would not stop problems with a name tags appearing in the XML source.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-118) Are the altrmi files still needed? If so, should they be moved elsewhere?
Are the altrmi files still needed? If so, should they be moved elsewhere? - Key: INCUBATOR-118 URL: https://issues.apache.org/jira/browse/INCUBATOR-118 Project: Incubator Issue Type: Bug Components: site Reporter: Sebb There is a large directory tree in the Incubator-public SVN containing the site for the podling AltRMI which is no longer with the ASF. See http://svn.apache.org/repos/asf/incubator/public/trunk/site-publish/projects/altrmi and http://incubator.apache.org/projects/altrmi/ Seems to me the only AltRMI file we should keep is the podling status, i.e. http://incubator.apache.org/projects/altrmi.html However, if the files are still to be kept, do they really belong on the Incubator public website? Would it not be more appropriate to store them elsewhere and make them read-only? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
