On Fri, Apr 10, 2009 at 05:31, Philip Olson <philip@roshambo.org> wrote:
So, we _can_ make the individual extension references valid standalone
and render them standalone and make them work OK within XML editors..
but at the cost of quite massive overhead when doing full builds.
Anyone thinks it is worth it?
By increasing build time by minutes, are you talking about per book or per
full build?
full builds. It is over 500% increase :|
That's not _too_ bad, and perhaps over time we'd find a few optimizations. Okay, 500% is bad.
I don't think it's worth implementing yet but would love to see a wiki entry
detailing all of this so that the work is not lost. And if we do decide to
move translations towards gettext (po files) it would likely be a good time
to revisit this topic.
Its not the translations fault, they are dealt with by using catalogs.
Its the redefinition of all the entities ~200 times (each ext) that is
killing it I think.
But since it requires editing most every XML file (thus outdating every translation) it would make for a good time to do it. Along with our move to SVN or GIT. Ugh.
Regards,
Philip