Closed egh closed 10 years ago
I think .texi files of FLIM and SEMI are generated from .sgml files. But the converter (sinfo.el, according to FLIM's .texi files) may obsolete. If we will maintain these files, we should first decide which (.texi or .sgml) files to maintain. If we will maintain only .texi files, .sgml file should be dropped. Or, if we will maintain .sgml files, we need to revive a converter.
Thanks for the comment. My preference would be switching to texinfo or some other format to be converted to texinfo rather than use a custom SGML format, but if we don't want to make a decision now I can easily make the change to the SGML file as well.
I'm not familiar with Texinfo, so please tell me if I'm not correct.
@setitle
command? stripping {
and }
is not enough?mime-en
because this is the same file. I changed mime-ja
to mime-ui-ja
because that is the correct name. I removed the multipart
reference because I could not find a valid multipart
section in the file.SEMI's document is mime-ui-en
and mime-en
is FLIM's document. For example, you remove (@ref{(mime-en)8bit}
, but FLIM's document has 8bit
node.
Oh, sorry! Thank you, I will correct all these and file a new pull request.
I was trying to use
makeinfo
to generate an.info
file, but it was failing on broken cross-references. This should correct the issue. I am unable to read Japanese, so cannot fix themime-ui-ja.texi
file.