----------------------------------------------------------------------------------
@MSGID: 1@dont-email.me> 73e568b8
@REPLY: <20230418075305.0e777c74@lm-Satellite-Pro-C70-B>
e3baf4e1
@REPLYADDR Colin Randall
<colin.randall2@gmail.com>
@REPLYTO 2:5075/128 Colin Randall
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID: 1@dont-email.me>
@RFC-References: 1@dont-email.me>
<20230414163259.7f528ebf@lm-Satellite-Pro-C70-B> 1@dont-email.me>
<a7b84722-ba92-42c9-bfbe-01445a125575n@googlegroups.com> 1@dont-email.me>
<20230418075305.0e777c74@lm-Satellite-Pro-C70-B>
@TZUTC: 0100
@PID: Mozilla/5.0 (Windows NT 10.0; Win64; x64;
rv:102.0) Gecko/20100101 Thunderbird/102.10.0
@TID: FIDOGATE-5.12-ge4e8b94
On 18/04/2023 15:53, Viatrix wrote:
> On 2023-04-18T11:02:16+0100
> Colin Randall <
colin.randall2@gmail.com> wrote:
>
>> a possible workaround? shall test
> That workaround looks correctly aligned on my client.
> I will note that line wasn`t the only one which looked misaligned; so
> do lines 64-65 (top 2 lines of serif "Welcome to ASCII art"), and
> 104-116 (entries 10 and up on the table of contents)
indeed ... same issue
... infact any(all) line(s) which start with a space
is(are) getting another(additional) space char inserted
during google-groups text to html translation library
[another (whitespace) test]
o <- zero leading spaces
o <- one leading space
o <- two leading spaces
--
.
._!__ __ __
/ _/_ |_ \\!_
/ / 7 / /|
\\ \\_ _/ / \\ .
\\_//__/|_\\_\\!_.
|
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
Thunderbird/102.10.0
* Origin: none whatsoever (2:5075/128)
SEEN-BY: 50/109 301/1 463/68 467/888 4500/1
5000/111 5001/100 5005/49
SEEN-BY: 5020/715 806 830 848 1042 4441 12000
5030/49 1081 5053/51 5054/8
SEEN-BY: 5064/56 5075/35 128 5083/1 444 6090/1
@PATH: 5075/128 5020/1042 4441