Hi Tim,
many, many kudo's. You were right, after installing
system/library/iconv/unicode
<https://pkg.openindiana.org/hipster/info/0/system%2Flibrary%2Ficonv%2Funicode%400.5.11%2C5.11-2022.0.0.20866%3A20220109T015823Z>
all tests passed
+Test project $(@D)
+ Start 1: libclamav
+1/5 Test #1: libclamav ........................ Passed 19.76 sec
+ Start 2: clamscan
+2/5 Test #2: clamscan ......................... Passed 4.83 sec
+ Start 3: clamd
+3/5 Test #3: clamd ............................ Passed 21.79 sec
+ Start 4: freshclam
+4/5 Test #4: freshclam ........................ Passed 2.07 sec
+ Start 5: sigtool
+5/5 Test #5: sigtool .......................... Passed 0.63 sec
+
+100% tests passed, 0 tests failed out of 5
and even
builduser@userland:~$ iconv -f PCK -t UTF-8 "/tmp/ja"
縺薙ｓ縺ｫ縺｡縺ｯ縺薙ｓ縺ｫ縺｡縺ｯ
now delivers a reasonable result.
Another question. Jim Klimov initially created this package. He also
prepared a README stating:
/It is expected that ultimate deployments might not want to run all of//
//the components in the same operating environment. In particular, the//
//maintenance of a local copy of the virus definitions database adds a//
//considerable storage and internet-traffic overhead which would be not//
//needed on systems that do not run `clamd` or other implementations of//
//the scanning engine directly.//
/
So, he created several packages to allow distinct installations.
Currently I've created only one package, but for update reasons should I
stick to the original packages (I think storage shouldn't be a problem
nowadays, despite I'm an educated engineer trying to be as efficient to
environment as possible, basically it is a consideration of minimum
space requirements and kind of convenience, also without updating
databases a virus scanner on a regular basis is kind of useless, right)?
kind regards,
Fritz
Am 11.01.2022 um 21:15 schrieb Tim Mooney via oi-dev:
In regard to: Re: [oi-dev] clamav update, Friedrich Kink via oi-dev
said...:
But maybe this code page is simply not supported by openindiana
because I tried to play around with iconv, too (it seems there is
nothing similar to JAPANESE_SHIFT_JIS) :
I just ran into this a couple weeks ago with a different test suite.
Based on how I read iconv_unicode(5) (and iconv(5), for non unicode),
OI's iconv has a limited set of supported conversions.
The tables in iconv_unicode(5) list "SJIS", though, which is the alias
OI uses, so in theory it should be possible to go from UTF-8 to SJIS.
That it's not showing up in the output from iconv -l has me wondering if
it's the case of a missing package. My guess is there should be a module
somewhere in /usr/lib/iconv/ that has "SJIS" (or perhaps some variant of
Kanji, since that's listed as the name, and SJIS is apparently the
alias?)
somewhere in its name.
Note the 'eucJP' does show up in the iconv output, and that is an
alternate (incompatible) pre-Unicode encoding.
This page has a lot of good info on the various encodings for Japan:
https://www.sljfaq.org/afaq/encodings.html
Tim
_______________________________________________
oi-dev mailing list
[email protected]
https://openindiana.org/mailman/listinfo/oi-dev
