Hi Walter,
At 2023-10-26T17:21:21+0200, Walter Alejandro Iglesias wrote:
> Ah, now I understand where's the problem, as it happens to me, groff
> 1.22.4 also ingores what you're explaining.
For me, the output doesn't change, but groff 1.22.4 doesn't emit a
diagnostic.
But that's not a surprise.
On Thu, Oct 26, 2023 at 09:35:07AM -0500, G. Branden Robinson wrote:
> At 2023-10-25T16:20:27+0200, Walter Alejandro Iglesias wrote:
> > What you did above is not the step by step way I posted to reproduce
> > the bug. Of course it won't be helpful if you overlook it.
>
> You've already gotten wh
At 2023-10-25T16:20:27+0200, Walter Alejandro Iglesias wrote:
> What you did above is not the step by step way I posted to reproduce
> the bug. Of course it won't be helpful if you overlook it.
You've already gotten what I would have thought to be a sufficient
explanation of the diagnostic messag
On Wed, Oct 25, 2023 at 07:58:37AM -0500, G. Branden Robinson wrote:
> Hi Walter,
>
> At 2023-10-25T14:25:42+0200, Walter Alejandro Iglesias wrote:
> > > This transcript isn't as useful as it could be, because it didn't
> > > disclose to me what character encoding was used for list.tr on the
> > >
Hi Walter,
At 2023-10-25T14:25:42+0200, Walter Alejandro Iglesias wrote:
> > This transcript isn't as useful as it could be, because it didn't
> > disclose to me what character encoding was used for list.tr on the
> > file system. Running the file(1) command on it and sharing that
> > would help.
On Wed, Oct 25, 2023 at 05:03:36AM -0500, G. Branden Robinson wrote:
> Hi Walter & Dave,
>
> At 2023-09-11T19:45:30+0200, Walter Alejandro Iglesias wrote:
> > If instead of sourcing hyphen.tr from my macros with .mso I source it
> > directly from the roff document with .so those error messages
> >
Hi Walter & Dave,
At 2023-09-11T19:45:30+0200, Walter Alejandro Iglesias wrote:
> If instead of sourcing hyphen.tr from my macros with .mso I source it
> directly from the roff document with .so those error messages
> desapear.
As Dave mentioned, this is explained by soelim(1) not being run on th
On 10/5/23, Walter Alejandro Iglesias wrote:
> If I feed preconv with a file already in latin1 (using UTF-8 locales
> here) ...
>
> $ preconv -e utf8 list_in_latin1.tr
>
> ... *all* non ASCII characters in the output are replaced by \[uFFFD].
Yes, this would be expected to not work. preconv's
On Thu, Oct 05, 2023 at 10:08:50AM +0200, Walter Alejandro Iglesias wrote:
> On Wed, Oct 04, 2023 at 10:20:57PM +, Bjarni Ingi Gislason wrote:
> > Latin1 iacute has the utf8 code 'Ã'
> > and the hexadecimal code is C3AD which is "LATIN CAPITAL LETTER A WITH
> > TILDE" and "SOFT HYPHEN"
> >
On Wed, Oct 04, 2023 at 10:20:57PM +, Bjarni Ingi Gislason wrote:
> Latin1 iacute has the utf8 code 'Ã'
> and the hexadecimal code is C3AD which is "LATIN CAPITAL LETTER A WITH
> TILDE" and "SOFT HYPHEN"
>
> "groff" turns "soft hyphen" into "HYPHEN-MINUS" (0x2D)
>
> More is in the attachme
On Wed, Oct 04, 2023 at 10:20:57PM +, Bjarni Ingi Gislason wrote:
> Latin1 iacute has the utf8 code 'Ã'
> and the hexadecimal code is C3AD which is "LATIN CAPITAL LETTER A WITH
> TILDE" and "SOFT HYPHEN"
>
> "groff" turns "soft hyphen" into "HYPHEN-MINUS" (0x2D)
>
Correction, it is turned
Latin1 iacute has the utf8 code 'Ã'
and the hexadecimal code is C3AD which is "LATIN CAPITAL LETTER A WITH
TILDE" and "SOFT HYPHEN"
"groff" turns "soft hyphen" into "HYPHEN-MINUS" (0x2D)
More is in the attachment.
file list.tr
.hw a-hÃ-
.hw a-ño
.hw ár-bol
.hw cu-brÃ--a
.hw e-té-re-o
.hw c
On Wed, Oct 04, 2023 at 01:49:49AM -0500, Dave Kemper wrote:
> On 9/12/23, Walter Alejandro Iglesias wrote:
> > This last command throws no error, that's because soelim(1) allows
> > preconv(1) to process the list.tr file.
>
> Walter,
>
> There's a proposal (http://savannah.gnu.org/bugs/?59442)
On 9/12/23, Walter Alejandro Iglesias wrote:
> This last command throws no error, that's because soelim(1) allows
> preconv(1) to process the list.tr file.
Walter,
There's a proposal (http://savannah.gnu.org/bugs/?59442) to change the
order of preprocessors to run soelim before preconv when grof
Hi Branden,
On Mon, Sep 11, 2023 at 03:33:03PM -0500, G. Branden Robinson wrote:
> This suggests to me that preconv(1) _must_ be run before you try to
> process your documents with this technique.
> [...]
> Please share input file(s) that reproduce the problem, and a command
> line that produces
Hi Walter,
At 2023-09-11T19:45:30+0200, Walter Alejandro Iglesias wrote:
> On Mon, Sep 11, 2023 at 07:18:59PM +0200, Walter Alejandro Iglesias wrote:
> > I normally use OpenBSD in my desktop, which still comes with groff
> > 1.22.4. Today I booted an old laptop with Debian testing (Devuan to
> >
On Mon, Sep 11, 2023 at 07:18:59PM +0200, Walter Alejandro Iglesias wrote:
> Dear groff users and developers,
>
> I normally use OpenBSD in my desktop, which still comes with groff
> 1.22.4. Today I booted an old laptop with Debian testing (Devuan to be
> more precise) and, after updating it, I c
17 matches
Mail list logo
