Re: Iconv.html and iconv.html
Mike Frysinger <[email protected]>
| Newsgroups | gmane.comp.lib.newlib |
|---|---|
| Message-ID | <Y5RDVjTLLgfCb2bA@vapier> |
On 10 Dec 2022 01:29, Mike Frysinger wrote:
> On 02 Dec 2022 17:06, Torbjorn SVENSSON wrote:
> > I have been building a toolchain for the arm-none-eabi target using a
> > rather recent snapshot of newlib. While building the html documentation,
> > I noticed that there will be generated the two files named Iconv.html
> > and iconv.html.
> > While this works fine for case sensitive file systems, it's obvious that
> > this will not have the desired outcome on a case-insensitive file
> > system, such as on Windows system.
> >
> > The Iconv.html file contains the chapter description and the iconv.html
> > file contains the description of the iconv-function.
> >
> > Can someone, with the knowledge of how these filenames are generated,
> > change one of them so that the filenames differ on a case insensitive
> > file system?
>
> the naming is straightforward -- the @node attribute is turned directly into
> the filename. we use @node Iconv for the chapter and @node iconv for the C
> function APIs. so the fix is to change one of them.
>
> the sub-areas have a 1-to-1 mapping to the chapter (e.g. stdio/->Stdio,
> iconv/->Iconv, etc...).
i took another look at this ... my initial dataset coincidentally aligned,
but looking at all of them, it seems we already aren't standardized.
ctype/ctype.tex Ctype
iconv/iconv.tex Iconv
locale/locale.tex Locale
misc/misc.tex Misc
posix/posix.tex Posix
reent/reent.tex Reentrancy
signal/signal.tex Signals
ssp/ssp.tex Overflow Protection
stdio64/stdio64.tex Stdio64
stdio/stdio.tex Stdio
stdlib/stdlib.tex Stdlib
string/strings.tex Strings
string/wcstrings.tex Wchar strings
time/time.tex Timefns
it's common for @node & @chapter to be aligned, so looking at iconv.tex:
@node Iconv
@chapter Encoding conversions (@file{iconv.h})
so changing @node to "Encoding conversions" seems pretty easy.
-mike
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEuQK1JxMl+JKsJRrUQWM7n+g39YEFAmOUQ1YACgkQQWM7n+g3 9YFxig//bPuXOM9ZVFvf1d2z2SVSpHC4J3G3Kd7DjLdAO9g4Xi6p3MKCu8cP7Pvi qtRUab+YHdxo810J2/Vg0QZp+25W6TMj8PRLTyL59PwmzbBvyrxRjuTCSGoFsPG0 OJ2cws3mPfcmSFuWruV0n1/XkobtM9TcaLaqTxAwKkzM4LTrygw4nI3zrEdawljJ Xk2Jna+Wv5XJb67wubntk5JYj0g32mA62YKbPb0q95TuC6X9HlBMlFs4LTVVOuM5 Vb21c+OK3Qbb7JvTTLjD24SZavDOJsvLWVx/Hk7BQgyQzHc5TgTzc4Xux5NU27FI OibbLgL5flXvMWbc/Zf3uZTfCjScUluY9pdE6WTM/E+xOFmOgnG80Rus/CzqVofT tSuGtnMPU1+fmoRY2z2oAGYudM6m21a/D3AtTv8+ah7Lv8v5UmHjvKq/lgi3+FEP 5jvM7ZQMLKoOTFQ6JeAeLmGTyopTraupeTr4r22o5y3XSgKJ5+zkZZhDZZrdegqT Qr0s7nedttBUYCfiU3qmmyMpIpa/dccipRr23hvBql15dxYSbwNmfDuQMR/YfO/H J9Zny23Gj9S1qM011o8emEvONRnfaJUkgmoxX6IEBthhqQHEdMalrcf1qttKyYQY Vq7g+3SMl38c9u50Vh8ZEiL4k1ggR3prxEFEPLXhm1tSKELLESo= =61UI -----END PGP SIGNATURE-----