[NVDA-dev] Little problem creating the changes.html document

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[NVDA-dev] Little problem creating the changes.html document

Michel Such
Here is the little thing.
 
When I look at the changes.html files generated in the snapshots, I can see the main title (What's new in NVDA) is at h1 level, which is good.
When I generate it myself in the build process, this title gets at h2 level, and the versions titles also are at h2.
Could it be that the global.t2tconf used in the site build process could be different from the one we get when retrieving the main source code?
 
Reply | Threaded
Open this post in threaded view
|

Re: [NVDA-dev] Little problem creating the changes.html document

James Teh
Aside from dependencies documented in readme.txt, the official automated
build script only uses code checked out of bzr, so it's exactly the same
as what you get yourself. When building, the script just calls scons
with the appropriate arguments.

How are you trying to build the changes.html file? Also, does the same
problem occur when you build the English changes file?

What version of txt2tags are you using? It could be a change in the
output that we aren't accounting for. We're currently using version 2.5.

Jamie

On 10/07/2011 11:11 PM, Michel such wrote:

> Here is the little thing.
> When I look at the changes.html files generated in the snapshots, I can
> see the main title (What's new in NVDA) is at h1 level, which is good.
> When I generate it myself in the build process, this title gets at h2
> level, and the versions titles also are at h2.
> Could it be that the global.t2tconf used in the site build process could
> be different from the one we get when retrieving the main source code?
>
>
>
> _______________________________________________
> NVDA-dev mailing list
> [hidden email]
> http://lists.nvaccess.org/listinfo/nvda-dev

--
James Teh
Vice President, Developer
NV Access Inc, ABN 61773362390
Email: [hidden email]
Web site: http://www.nvaccess.org/