| Osamu Aoki 2006-06-27, 1:25 pm |
| On Tue, Jun 27, 2006 at 12:28:15PM +0200, Frank K=FCster wrote:
> Osamu Aoki <osamu@debian.org> wrote:
>=20
S,[vbcol=seagreen]
ing[vbcol=seagreen]
"?[vbcol=seagreen]
>=20
> And which packages are affected?
Sorry, I can not be specific. That is my old memory. Let's move on. 
>=20
> If a LaTeX document is complex, this can be in fact needed (although
> I've never seen anything needing more than 4 repetitions). It could
> also be a problem of the build system. In any case it has nothing to do
> with the fact that the sourceis xml/sgml, except maybe that there might
> be suboptimal converters involved.
>=20
>=20
> cjk is still a problem, that's right. I hope I'll be able to sponsor an
> upload of latex-cjk soon.
Please. I did few minor NMU to get it to etch. I thought Anthony Fok
is back in action.
>=20
> Sorry, which build script are you talking about? doc-debian's? =20
That what I meant. we fixed it by updating debiandoc-sgml. Anyway,
that was non-trivial work for SGML DOC maintainer without LaTeX
knowledge.
> Then
> how is this a problem for generating PDF from xml/sgml sources?
That is history now. The point is if you think about building PDF from
source, you are pulling huge amount of packages. That is major
headache.
I think people scream when GCC upgrades and cough on some programs.
Similar situation is what might have happened with DOC package and TeX.
I think TeX is maintained well in par with GCC. But Debian release
cycle is mostly dictated by Kernel/GCC/glibc/X/gtk/gnome/Qt/... So
current policy not to be FTBFS even for DOC package is tough one. (I
think we need to have reasonable exceptions for DOC package. If it
build with previous "stable" release, it should be allowed to be
published.=20
I know current effort of moving developer-reference to XML is only for
HTML and plain text. There seem to be issues with building PDF from
UTF-8. Talk to W. Borgert" <debacle@debian.org> on this subject.
>=20
> Sorry, I don't understand what you want to say.
I saw sometime ago, some package had non-PDF source, and PDF file as a
part of source. Then build of the source package just moved PDF to
binary package.
>=20
> ? It does contain documentation in form of example text files. If
> that's not enough, that's a problem of content, not of the format, isn't
> it?=20
Look into the source package and run "make ifupdown.pdf" (yep you need few
more dependancy application installed like "dia". )
> Regards, Frank
Osamu
|