> AFAICS, the only method to get a 'space' index entry is having a
> series of backslashes if 'txiindexbackslashignore' is set.
I have to correct myself. An index entry
```
@findex {}
```
also generates a line
```
\entry{ }{1}{\code {}}
```
However, it gets swallowed by `texindex`, so it do
[texinfo.tex 2022-10-18.18]
Consider the following input file
```
\input texinfo.tex
@set txiindexbackslashignore
@findex \\
@findex A
@printindex fn
@bye
```
The created `.fn` file contains
```
\entry{ }{1}{\code {\backslashchar {}\backslashchar {}}}
```
which doesn't make sense, and wh
> On Nov 6, 2022, at 8:05, Patrice Dumas wrote:
>
> On Sat, Nov 05, 2022 at 07:43:17PM +, Gavin Smith wrote:
>> On Sat, Nov 05, 2022 at 05:25:07PM +0100, Patrice Dumas wrote:
>>> Hello,
>>>
>>> It will become possible to add translation context to in-document
>>> translated strings in dev
On Sat, Nov 05, 2022 at 07:43:17PM +, Gavin Smith wrote:
> On Sat, Nov 05, 2022 at 05:25:07PM +0100, Patrice Dumas wrote:
> > Hello,
> >
> > It will become possible to add translation context to in-document
> > translated strings in developments to come. I am not sure in which
> > situations
On Sat, Nov 05, 2022 at 05:25:07PM +0100, Patrice Dumas wrote:
> Hello,
>
> It will become possible to add translation context to in-document
> translated strings in developments to come. I am not sure in which
> situations it will be better to use contexts to be clearer on the
> intended use of
Hello,
It will become possible to add translation context to in-document
translated strings in developments to come. I am not sure in which
situations it will be better to use contexts to be clearer on the
intended use of a translated string. In particular there are, for HTML,
many direction str
