Re: specifying directory in htmlxref.conf file to include more files

2025-02-13 Thread Patrice Dumas
On Sat, Jan 18, 2025 at 11:22:07PM +0100, Patrice Dumas wrote: > In any case, I said above, my preference now would be to use both an > htmlxref.cnf and files in htmlxref.d/*.cnf in all the directories where > htmlxref.cnf are searched for currently and no include directive. This is done. I also

Re: `@anchor` improvement

2025-02-13 Thread Werner LEMBERG
> I do not like the automatic association of an inline command like > @anchor, that may happen anywhere, to another command. I think that > it would be cleaner to have an @-command with two arguments, > instead, like > > @anchorlabel Bows, Bögen > > A comma in the anchor part would need to be e

Re: `@anchor` improvement

2025-02-13 Thread Werner LEMBERG
> Your proposal from a few days ago of using a @*heading command > appears relevant. We could use a command like > "@xrefanchorlabelisheading" (hard to get a descriptive, short name). > > So with input like: > > @heading Bögen > @anchor{Bows} > > Then @ref{Bows} would produce "Bögen", etc. >

Re: `@anchor` improvement

2025-02-13 Thread Werner LEMBERG
>> * For translators, having the same anchor name as in the original >> document helps a lot in translation. And vice versa, it helps >> maintainers who don't speak the particular language to still do >> various maintenance tasks easier. > > I do not think that this is such a good reason t

Re: `@anchor` improvement

2025-02-13 Thread pertusus
On Wed, Feb 12, 2025 at 10:12:15PM +0100, pertu...@free.fr wrote: > I do not like the automatic association of an inline command like > @anchor, that may happen anywhere, to another command. I think that it > would be cleaner to have an @-command with two arguments, instead, like > > @anchorlabel