• conversion to cp866

    From Maurice Kinal@1:153/7001.2989 to Zoot on Sat Mar 16 07:04:44 2024
    Hey Zoot!

    This time I only used 'trans' to translate unbounded English text and then 'fold' and 'sed' to format the Russian text shown below. 'iconv' was then deployed to convert utf8 Russian text to cp866. Looks like it works much better than 'trans' -width modifier.

    , 祭 筮 宩 ࠢ
    襩. ᥣ ᥬ줥 , ᥬ
    ⭠ ⭠ , १ ᢮ , . . ... 㯠... ... ࠧ... ⮢ 墠뢠饣
    ...

    Life is good,
    Maurice

    -o o- o- -o o- -o o- o- -o o- o- o- o- o- -o -o
    (\ /) /) (\ /) (\ /) /) (\ /) /) /) /) /) (\ (\
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Fidonet 4K - Sweet Sixteen Penguins of the Apocalypse.
    --- GNU bash, version 5.2.26(1)-release (x86_64-pc-linux-gnu)
    * Origin: One of us @ (1:153/7001.2989)
  • From Maurice Kinal@2:280/464.113 to Maurice Kinal on Sat Mar 16 07:27:00 2024
    Hej Maurice!

    Looks like it works much better than 'trans' -width modifier.

    Excellent. From this angle all characters were preserved ... no hanky-panky anywhere along the way. :-)

    Het leven is goed,
    Maurice

    o- o- o- o-
    /) /) /) /)
    ^^ ^^ ^^ ^^
    ... Fidonet 1080p - De vier pinguïns van de Apocalyps
    --- GNU bash, version 5.2.26(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's EuroPoint @ (2:280/464.113)
  • From Nicholas Boel@1:154/10 to Maurice Kinal on Sat Mar 16 08:37:20 2024
    On Sat, 16 Mar 2024 07:04:44 GMT, Maurice Kinal -> Zoot wrote:

    This time I only used 'trans' to translate unbounded English text and
    then 'fold' and 'sed' to format the Russian text shown below.  'iconv' was then deployed to convert utf8 Russian text to cp866.  Looks like it works much better than 'trans' -width modifier.

    Боюсь, наша жизнь должна показаться очень скучной и тихой по сравнению
    с вашей. Мы всего лишь восемьдесят молодых блондинок, всем от
    шестнадцати до девятнадцати с половиной лет, отрезанные от мира в своем
    замке, и никто не может нас защитить. Оооо. Это одинокая жизнь...
    купание... одевание... раздевание... изготовление захватывающего
    нижнего белья...

    That's neat-o. Keep up the good fight! :)

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Maurice Kinal@2:280/464.113 to Nicholas Boel on Sat Mar 16 15:38:18 2024
    Hej Nicholas!

    That's neat-o.

    I note that you convert them back to utf-8 before replying. I do the same here except that after replying I convert them back to the supported 8-bit character set, cp866 in this case. To be honest utf-8 for all would be best especially when given bogus information in so-called ftn standards. Simply shocking methinks.

    Keep up the good fight! :)

    For sure. Someone has to be on the side of what is right and proper. :-)

    Het leven is goed,
    Maurice

    o- -o o- -o
    /) (\ /) (\
    ^^ ^^ ^^ ^^
    ... Fidonet 1080p - De vier pinguïns van de Apocalyps
    --- GNU bash, version 5.2.26(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's EuroPoint @ (2:280/464.113)
  • From Nicholas Boel@1:154/10 to Maurice Kinal on Sat Mar 16 10:55:42 2024
    On Sat, 16 Mar 2024 15:38:18 GMT, Maurice Kinal -> Nicholas Boel wrote:

    I note that you convert them back to utf-8 before replying.  I do the same here except that after replying I convert them back to the
    supported 8-bit character set, cp866 in this case.  To be honest utf-8 for all would be best especially when given bogus information in
    so-called ftn standards.  Simply shocking methinks.

    I believe this client forces utf-8 when posting, which is fine. The conversion works automatically. I do have other clients for testing purposes that can send it back in CP866, but why?

    For sure.  Someone has to be on the side of what is right and proper.  :-)

    Be prepared to be in the fight for the long haul. :)

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Maurice Kinal@1:153/7001 to Nicholas Boel on Sat Mar 16 16:09:19 2024
    Hey Nicholas!

    I believe this client forces utf-8 when posting, which is fine.

    From the PID I am gathering the client is nttp based. I've run across similar strategies here and there. The output looks fine from this angle.

    I do have other clients for testing purposes that can send it back
    in CP866, but why?

    Because we can? Besides CP866 is one of the few encodings that they - whoever 'they' are - get right.

    Be prepared to be in the fight for the long haul. :)

    I've been doing so off and on and probably will continue as long as I have a haul nevermind a long one.

    Besides it isn't the size of the haul but the quality. ;-)

    Life is good,
    Maurice

    -o -o o- o- -o -o o- -o o- -o -o -o o- -o -o -o
    (\ (\ /) /) (\ (\ /) (\ /) (\ (\ (\ /) (\ (\ (\
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Monig biþ uncuþ treowgeþofta, teorað hwilum.
    Many a trusted friend will prove to be unknown, will fail at times.
    --- GNU bash, version 5.2.26(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From August Abolins@2:221/1.59 to Nicholas Boel on Sat Mar 16 12:45:10 2024

    Did not go over well with Aftershock.
    HTTPS://ibb.co/rx9V6kx

    On 16 Mar. 2024 08:37, you wrote to Maurice:
    @MSGID: 1:154/10 65f5a090
    @REPLY: 1:153/7001.2989 65f5448c
    @PID: smapinntpd/linux 2.1.9
    @CHRS: UTF-8 4
    @TZUTC: -0500
    @TID: hpt/lnx 1.9 2024-02-05

    On Sat, 16 Mar 2024 07:04:44 GMT, Maurice Kinal -> Zoot wrote:

    This time I only used 'trans' to translate unbounded English text and
    then 'fold' and 'sed' to format the Russian text shown below.?? 'iconv'
    was then deployed to convert utf8 Russian text to cp866.?? Looks like it
    works much better than 'trans' -width modifier.

    ???????, ???? ??????? ????????? ???????????
    ?????? ????????? ?? ???????? ??? ?????????? ?
    ??????. ??? ??????? ????? ????????????? ??????????
    ?????????????, ???? ??? ????????????? ????
    ??????????????? ? ?????????????? ???,
    ??????????? ??? ????? ? ?????? ?????, ?? ???????
    ?? ??????? ??? ??????????. ????????. ????? ????????????
    ???????... ????????... ???????????...
    ????????????... ?????????????????
    ???????????????? ??????????? ?????...

    That's neat-o. Keep up the good fight! :)

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10) SEEN-BY: 103/705 120/616 123/10 124/5016 153/757 7001 154/10 30 40 50 700 SEEN-BY: 203/0 220/90 221/0 1 6 360 226/18 70 240/1120 5832 280/464 5003 SEEN-BY: 292/8125 301/1 310/31 320/219 341/66 234 396/45 423/81 460/58 467/888 SEEN-BY: 633/280 712/848 770/1 2320/105 3634/12 5020/400 @PATH: 154/10 280/464 221/1


    --- AfterShock/Android 1.7.5
    * Origin: Mobile Pixel 3aXL (2:221/1.59)
  • From August Abolins@2:221/1.59 to Maurice Kinal on Sat Mar 16 12:47:22 2024
    This one was perfectly readable in Aftershock, but the reply does not cooperate.

    On 16 Mar. 2024 07:04, you wrote to Zoot:
    @MSGID: 1:153/7001.2989 65f5448c
    @CHRS: CP866 2

    Hey Zoot!

    This time I only used 'trans' to translate unbounded English text and then 'fold' and 'sed' to format the Russian text shown below. 'iconv' was then deployed to convert utf8 Russian text to cp866. Looks like it works much better than 'trans' -width modifier.

    ?????, ???? ????? ?????? ?????????? ????? ??????? ? ????? ?? ?????????
    ? ?????. ?? ????? ???? ??????????? ??????? ?????????, ???? ??
    ??????????? ?? ???????????? ? ????????? ???, ?????????? ?? ???? ? ?????
    ?????, ? ????? ?? ????? ??? ????????. ????. ??? ???????? ?????...
    ???????... ????????... ??????????... ???????????? ??????????????
    ??????? ?????...

    Life is good,
    Maurice

    -o o- o- -o o- -o o- o- -o o- o- o- o- o- -o -o (\ /) /) (\ /) (\ /) /) (\ /) /) /) /) /)
    (\ (\ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ^^ ^^ ^^ ... Fidonet 4K - Sweet Sixteen Penguins of the Apocalypse. --- GNU bash, version 5.2.26(1)-release (x86_64-pc-linux-gnu)
    * Origin: One of us @ (1:153/7001.2989)
    SEEN-BY: 103/705 124/5016 134/100 153/135 143 148 757 802 7001 154/10 30 203/0 SEEN-BY: 221/0 1 6 360 240/1120 5832 280/464 5003 292/8125 301/1 310/31 SEEN-BY: 320/219 341/66 234 396/45 423/81 460/58 467/888 633/280 712/848 770/1 SEEN-BY: 3634/12 5020/400
    @PATH: 153/7001 757 280/464 221/1


    --- AfterShock/Android 1.7.5
    * Origin: Mobile Pixel 3aXL (2:221/1.59)
  • From Nicholas Boel@1:154/10 to August Abolins on Sat Mar 16 12:19:30 2024
    On Sat, 16 Mar 2024 17:45:10 -0400, August Abolins -> Nicholas Boel wrote:

    Did not go over well with Aftershock.
    HTTPS://ibb.co/rx9V6kx

    From the looks of that screenshot, it doesn't look like it quotes very well, either, going from 80 or more characters wide to 50 characters. But I would imagine if there were no initials before the quoted text, it would probably work better.

    Either way, that's because you seem to have Aftershock setup for CP437 charset. Those kind of UTF-8 characters do not translate to CP437, at all.

    Did Maurice's original message show up ok for you? Because I don't think CP866 (at least those characters) translates to CP437, either.

    Can Aftershock use different charsets?

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to August Abolins on Sat Mar 16 12:21:28 2024
    On Sat, 16 Mar 2024 17:47:22 -0400, August Abolins -> Maurice Kinal wrote:

    This one was perfectly readable in Aftershock, but the reply does not cooperate.

    You would have to setup Aftershock to post/reply with CP866 as well (before you send off your message). As of right now you're trying to translate those characters to CP437, which won't work.

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Maurice Kinal on Sat Mar 16 12:25:04 2024
    Hello Maurice,

    On Sat, 16 Mar 2024 07:04:44 GMT, you wrote:

    This time I only used 'trans' to translate unbounded English text and
    then 'fold' and 'sed' to format the Russian text shown below. 'iconv'
    was then deployed to convert utf8 Russian text to cp866. Looks like it works much better than 'trans' -width modifier.

    , 祭 筮 宩 ࠢ
    襩. ᥣ ᥬ줥 , ᥬ
    ⭠ ⭠ , १ ᢮
    , . . ...
    㯠... ... ࠧ... ⮢ 墠뢠饣
    ...

    Let's see how this one gets back to you. ;)

    Regards,
    Nick

    ... Take my advice, I don't use it anyway.
    --- slrn/pre1.0.4-9 (Linux)
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Wilfred van Velzen@2:280/464 to August Abolins on Sat Mar 16 18:23:23 2024
    Hi August,

    On 2024-03-16 12:45:10, you wrote to Nicholas Boel:

    Did not go over well with Aftershock.
    HTTPS://ibb.co/rx9V6kx
    ^^^^^

    Please use lowercase, so my terminal recognises it as an url and shows it as a clickable link! ;-)


    Bye, Wilfred.

    --- FMail-lnx64 2.3.0.0-B20240315
    * Origin: FMail development HQ (2:280/464)
  • From Maurice Kinal@2:280/464.113 to August Abolins on Sat Mar 16 17:37:42 2024
    Hej August!

    This one was perfectly readable in Aftershock, but the reply does
    not cooperate.

    Not surprising given that CP437 doesn't support CP866 encoding. The only encoding that properly supports differing languages is utf8. CP437 falls short of supporting anything other than the so-call higher ascii, which of course is bogus. All ascii are 7-bit characters and is well supported by most encodings in the range of 0x00 to 0x7f. Anything above that isn't ascii, higher or otherwise.

    Het leven is goed,
    Maurice

    o- o- o- o-
    /) /) /) /)
    ^^ ^^ ^^ ^^
    ... Fidonet 1080p - De vier pinguïns van de Apocalyps
    --- GNU bash, version 5.2.26(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's EuroPoint @ (2:280/464.113)
  • From Maurice Kinal@2:280/464.113 to Nicholas Boel on Sat Mar 16 17:54:35 2024
    Hej Nicholas!

    Let's see how this one gets back to you. ;)

    It looks perfect from this angle. I am still left wondering how accurate the original translation was.

    Het leven is goed,
    Maurice

    o- o- -o o-
    /) /) (\ /)
    ^^ ^^ ^^ ^^
    ... Fidonet 1080p - De vier pinguïns van de Apocalyps
    --- GNU bash, version 5.2.26(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's EuroPoint @ (2:280/464.113)
  • From August Abolins@2:221/1.58 to Wilfred van Velzen on Sat Mar 16 18:27:00 2024
    Hello Wilfred!

    Did not go over well with Aftershock.
    HTTPS://ibb.co/rx9V6kx
    ^^^^^

    Please use lowercase, so my terminal recognises it as an url and shows
    it as a clickable link! ;-)

    Maybe program your reader to accept https! :D No issues with
    that here! ;)




    --- OpenXP 5.0.58
    * Origin: (2:221/1.58)
  • From August Abolins@2:221/1.58 to Nicholas Boel on Sat Mar 16 18:56:00 2024
    Hello Nicholas!

    Did not go over well with Aftershock.
    HTTPS://ibb.co/rx9V6kx

    From the looks of that screenshot, it doesn't look like it
    quotes very well, either, going from 80 or more characters
    wide to 50 characters. But I would imagine if there were
    no initials before the quoted text, it would probably work
    better.

    It's not so bad. The message can also be viewed in landscape.


    Either way, that's because you seem to have Aftershock
    setup for CP437 charset. Those kind of UTF-8 characters do
    not translate to CP437, at all.

    Aftershock only has selectable CP437 and CP866. There is a
    mode "same as device", but I don't know how that works.


    Did Maurice's original message show up ok for you? Because
    I don't think CP866 (at least those characters) translates
    to CP437, either.

    The original one was fine in Aftershock.


    Can Aftershock use different charsets?

    Dunno. Maybe "same as device" does that?

    --
    ../|ug

    --- OpenXP 5.0.58
    * Origin: (2:221/1.58)
  • From August Abolins@2:221/1.58 to Nicholas Boel on Sat Mar 16 19:02:00 2024
    HTTPS://ibb.co/rx9V6kx

    From the looks of that screenshot, it doesn't look like it
    quotes very well, either, going from 80 or more characters
    wide to 50 characters. But I would imagine if there were
    no initials before the quoted text, it would probably work
    better.

    It's not so bad. The message can also be viewed in landscape.

    Oops.. I forgot to add the screenshot:

    https://ibb.co/GsGdnBr


    --
    ../|ug

    --- OpenXP 5.0.58
    * Origin: (2:221/1.58)
  • From August Abolins@2:221/1.58 to Maurice Kinal on Sun Mar 17 09:28:00 2024
    Hello Maurice Kinal!

    Not surprising given that CP437 doesn't support CP866
    encoding. The only encoding that properly supports
    differing languages is utf8. CP437 falls short of
    supporting anything other than the so-call higher ascii,
    which of course is bogus. All ascii are 7-bit characters
    and is well supported by most encodings in the range of
    0x00 to 0x7f. Anything above that isn't ascii, higher or
    otherwise.

    So.. you're implying that utf8 should be baked into fidonet?

    A vast majority of retro systems and software would still be
    limited to the 7-bit chars and high-ascii, so.. what's the
    urgency for utf8?

    --
    ../|ug

    --- OpenXP 5.0.58
    * Origin: (2:221/1.58)
  • From Maurice Kinal@2:280/464.113 to August Abolins on Sun Mar 17 13:53:20 2024
    Hej August!

    So.. you're implying that utf8 should be baked into fidonet?

    It already is. Has been for over a decade now.

    A vast majority of retro systems and software would still be
    limited to the 7-bit chars and high-ascii,

    Not a problem. utf8, like most of the 8-bit codepages, has ascii built into it. Without that you'd have a very good case for rejecting it in any ftsc document. As is your argument has no teeth.

    so.. what's the urgency for utf8?

    No urgency other than being first and best, which undoubtably I am ... or at least I used to be. I had it working before it became part of fts-5003.001.

    Het leven is goed,
    Maurice

    o- -o o- o-
    /) (\ /) /)
    ^^ ^^ ^^ ^^
    ... Fidonet 1080p - De vier pinguïns van de Apocalyps
    --- GNU bash, version 5.2.26(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's EuroPoint @ (2:280/464.113)
  • From August Abolins@2:221/1.58 to Maurice Kinal on Sun Mar 17 12:17:00 2024
    Hello Maurice!

    So.. you're implying that utf8 should be baked into fidonet?

    It already is. Has been for over a decade now.

    What I meant was should it be "the" standard in character
    support in fidonet products?

    There is nothing stopping anyone setting up an exclusive/pure
    utf8-based ftn-based network.


    so.. what's the urgency for utf8?

    No urgency other than being first and best, which
    undoubtably I am ... or at least I used to be. I had it
    working before it became part of fts-5003.001.

    I do believe that the ftsc-gods need to see sufficient evidence
    of any new tech in use *before* it is given recognition with an
    fts document ;) ..so, you *had* to have it working before it
    became part of fts-5003.001. :D


    --
    ../|ug

    --- OpenXP 5.0.58
    * Origin: (2:221/1.58)
  • From Maurice Kinal@1:153/7001 to August Abolins on Sun Mar 17 16:36:24 2024
    Hey August!

    What I meant was should it be "the" standard in character support
    in fidonet products?

    No but it definetly should be if one wishes to claim a completely capable product. I would wish no less for you and yours.

    There is nothing stopping anyone setting up an exclusive/pure
    utf8-based ftn-based network.

    I suppose but it would probably be very lonely. Mind you I see that happening anyhow so there doesn't appear to be much to lose at this point in time.

    you *had* to have it working before it became part of
    fts-5003.001. :D

    I was really bored at the time and it offered an interesting challenge. I was caught offguard when it became part of standards. I wasn't expecting that at the time but I was ready for it as it turned out.

    Life is good,
    Maurice

    o- o- -o o- -o o- -o -o -o o- -o -o o- -o o- o- /) /) (\ /) (\ /) (\ (\ (\ /) (\ (\ /) (\ /) /) ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Ne læt þu no unlofod þæt þu swytele ongite þæt licwyrðe sie.
    Do not leave unpraised anything you know well to be worthy.
    --- GNU bash, version 5.2.26(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Alexander Grotewohl@1:120/616 to Maurice Kinal on Sun Mar 17 18:07:21 2024
    On 17 Mar 2024, Maurice Kinal said the following...

    What I meant was should it be "the" standard in character support
    in fidonet products?

    No but it definetly should be if one wishes to claim a completely capable product. I would wish no less for you and yours.

    it feels kind of lame that BBS systems still use codepages.

    my term (ZOC) obviously is just translating CP437 to my UTF-8 font and it displays all the line drawing and pseudo graphic characters (imo) better than almost all the retro fonts ever did..

    so i've been a long time IRC user and one day someone, or noone, basically decided IRC was going to be UTF-8 and if you couldn't read what was written
    too bad.

    ... 私の墓石は DejaVu Sans Mono で刻まれます

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
    * Origin: cold fusion - cfbbs.net - grand rapids, mi (1:120/616)
  • From Alexander Grotewohl@1:120/616 to Alexander Grotewohl on Sun Mar 17 18:17:54 2024
    On 17 Mar 2024, Alexander Grotewohl said the following...

    ... 私の墓石は DejaVu Sans Mono で刻まれます

    and it didn't work.. because of course it didn't.. heh

    watashi no boseki wa DejaVu Sans Mono de kizama remasu
    "My tombstone will be engraved with DejaVu Sans Mono"

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
    * Origin: cold fusion - cfbbs.net - grand rapids, mi (1:120/616)
  • From Maurice Kinal@1:153/7001 to Alexander Grotewohl on Sun Mar 17 22:11:49 2024
    Hey Alexander!

    it feels kind of lame that BBS systems still use codepages.

    They need cp437 for ansi art. They shouldn't for ascii art but then again they don't know any better that cp437 characters from 0x80-0xff aren't really ascii and never were. This is what really made cp437 the codepage to avoid.

    it displays all the line drawing and pseudo graphic characters
    (imo) better than almost all the retro fonts ever did..

    Agreed. For ansi art I take it a step further and restrict the output to a 80x24 terminal so that lines without terminators get properly wrapped. I used to use 'setterm' but now that I have tmux with the proper screen dimensions which allows me to use the rest of the real estate for other things. On a 4K monitor it makes a HUGE difference. I highly recommend tmux for a client based BBS surfing solution with a bad-ass attitude.

    IRC was going to be UTF-8 and if you couldn't read what was
    written too bad.

    We can do better.

    Life is good,
    Maurice

    o- -o o- o- o- -o o- -o -o o- o- o- -o o- -o o- /) (\ /) /) /) (\ /) (\ (\ /) /) /) (\ /) (\ /) ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Sorg bið swarost byrðen, slæp bið deaðe gelicost.
    Sorrow is the heaviest burden, sleep is most like death.
    --- GNU bash, version 5.2.26(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)