4-(2-碘代乙酰氨基)-2,2,6,6-四甲基哌啶-1-氧基自由基
最小起订1克
供货总量1000克
发货地址河南郑州市
建议售价￥1/克
更新日期日
电话咨询请告知是在盖德化工网上看到的，谢谢!
企业认证：
企业性质：18,21,14,26,
主营产品：化工产品,仪器仪表,化学试剂
公司地址：郑州市管城区港湾路2号
产品英文名称：
4-(2-IODOACETAMIDO)-TEMPO
C11H20IN2O2 *
产品规格：
5g 25g 50g 100g 500g 1kg
&厂家直销，现货供应联系电话：6&询&价QQ：&&&侯经理&&&&&&&（阿尔法）郑州汇聚化工有限公司是集开发、生产、销售为一体的高科技化学试剂公司，提供通用试剂的分销、非通用试剂的订制和开发等技术服务。公司拥有一批长期从事精细化学品开发和生产的高级技术人员，以及设备齐全的研发实验室和中试车间。产品被广泛应用于全国高等院校、科研院所、医药研发企业和化工企业等科研部门，且受到用户的一致好评。&&&&&&&&&我公司主要生产硼酸类，吡啶类，噻吩类，菲啰啉类，羧酸联吡啶类，金属催化剂，硅烷类等用于医药化工、精细化工、催化化工的有机中间体化学品。各种纯度的试剂：优级纯,分析纯,化学纯,试剂级,基准试剂,&实验纯&,教学试纯，高纯试剂纯，色谱纯,光谱纯,电子纯。&我公司所有产品全国包邮，提供各种包装规格，另部分产品能够定制，店铺内只有公司部分产品。我们价格优惠，质量有保障，我公司对高校和国家科研机构可以先发货和开票后再付款，如果您在工作中有用到的试剂，欢迎您及时联系。出现质量问题，全额退款，并承担所有运费，欢迎QQ或来电咨询相关产品，具体价格和优惠请QQ联系或电议为准。&电话：6&&&&询价QQ：&&侯经理
（阿尔法）郑州汇聚化工有限公司 是集开发、生产、销售为一体的高科技化学试剂公司，提供通用试剂的分销、非通用试剂的订制和开发等技术服务。公司拥有一批长期从事精细化学品开发和生产的高级技术人员，以及设备齐全的研发实验室和中试车间。产品被广泛应用于全国各大专院校、科研院所、医药研发企业和化工企业等科研部门，经过多年的发展，公司的诚信、实力和产品质量受到用户的一致好评。 公司崛起于中原腹地，坐落于交通便利的绿城&mdash；郑州。“质量第一，用户至上”是我们的服务宗旨。（阿尔法）汇聚化工始终坚持以市场为导向，集产、学、研技术服务为一体，根据客户的不同需求，及时为客户提供最优质的服务。我公司主要生产硼酸类，吡啶类，噻吩类，菲啰啉类，羧酸联吡啶类，金属催化剂，硅烷类等用于医药化工、精细化工、催化化工的有机中间体化学品。 我公司所有产品 全国包邮，提供各种包装规格，另部分产品能够定制，店铺内只有公司部分产品。我们价格优惠，质量有保障，我公司对高校和国家科研机构可以先发货和开票后再付款，如果您在工作中有用到的试剂，欢迎您及时联系。出现质量问题，全额退款，并承担所有运费，欢迎来电或QQ咨询相关产品，具体价格和优惠请QQ联系或电议为准。
成立时间：
企业经济性质：
私营独资企业
年营业额：
注册资金：
经营模式：
生产商,贸易商,
员工人数：
该公司其他产品
价格：￥10/g/kg
产品详情：厂家直销，现货供应联系电话：询价QQ：李经理（阿尔法）郑州汇聚化工有限公司是集开发、生产...
价格:10&元/g/kg
品牌:阿尔法
价格：￥1/克
产品详情：厂家直销，现货供应联系电话：询价QQ：侯经理（阿尔法）郑州汇聚化工有限公司是集开发、生产...
价格:1&元/克
品牌:阿尔法
4-(2-碘代乙酰氨基)-2,2,6,6-四甲基哌啶-1-氧基自由基...相关供应商报价
￥1/上海羽...
国产/进...
￥891/毫克
进口、国...
相关产品热搜词
“4-(2-碘代乙酰氨基)-2,2,6,6-四甲基哌啶-1-氧基自由基...”热门产品搜索
免责声明：以上所展示的信息由企业自行提供，内容的真实性 、准确性和合法性由发布企业负责，盖德化工网对此不承担任何保证责任。 同时我们郑重提醒各位买/卖家，交易前 请详细核实对方身份，切勿随意打款或发货，谨防上当受骗。如发现虚假信息，请向盖德化工网举报。
致：(阿尔法)郑州汇聚化工有限公司
关注微信公众号未找到信息!
未找到信息!
收录 / 索引信息
未找到信息!
一般不超过80字符
网站关键词
一般不超过100字符
一般不超过200字符
同主机安全
虚假或欺诈网站
挂马或恶意网站
未存在违规内容
相关子域名
alexa排名趋势
服务器信息
服务器类型
源文件大小
压缩后大小
最后修改时间
关闭关闭关闭perl: Uncaught exception: malformed UTF-8 character in JSON string - Stack Overflow
Join Stack Overflow to learn, share knowledge, and build your career.
or sign in with
Related to
(to another question) I am still unable to process UTF-8 with JSON.
I have tried to make sure all the required voodoo is invoked based on recommendations from the very best experts, and as far as I can see the string is as valid, marked and labelled as UTF-8 as possible. But still perl dies with either
Uncaught exception: malformed UTF-8 character in JSON string
Uncaught exception: Wide character in subroutine entry
What am I doing wrong here?
(hlovdal) localhost:/work/2011/perl_unicode&cat json_malformed_utf8.pl
#!/usr/bin/perl -w -CSAD
### BEGIN ###
# Apparently the very best perl unicode boiler template code that exist,
# https://stackoverflow.com/questions/6162484/why-does-modern-perl-avoid-utf-8-by-default/3129
# Slightly modified.
use v5.12; # minimal for unicode string feature
#use v5.14; # optimal for unicode string feature
# Declare that this source unit is encoded as UTF-8. Although
# once upon a time this pragma did other things, it now serves
# this one singular purpose alone and no other.
# Enable warnings, since the previous declaration only enables
use warnings
# strictures and features, not warnings. I also suggest
# promoting Unicode warnings into exceptions, so use both
# these lines, not just one of them.
qw( :encoding(UTF-8) :std );
# Declare that anything that opens a filehandles within this
# lexical scope but not elsewhere is to assume that that
# stream is encoded in UTF-8 unless you tell it otherwise.
# That way you do not affect other module’s or other program’s code.
use charnames
qw& :full &;
# Enable named characters via \N{CHARNAME}.
use feature
qw& unicode_strings &;
qw& carp croak confess cluck &;
use Encode
qw& encode decode &;
use Unicode::Normalize
qw& NFD NFC &;
END { close STDOUT }
if (grep /\P{ASCII}/ =& @ARGV) {
@ARGV = map { decode("UTF-8", $_) } @ARGV;
binmode(DATA, ":encoding(UTF-8)");
# If you have a DATA handle, you must explicitly set its encoding.
# give a full stack dump on any untrapped exceptions
local $SIG{__DIE__} = sub {
confess "Uncaught exception: @_" unless $^S;
# now promote run-time warnings into stackdumped exceptions
*unless* we're in an try block, in which
case just generate a clucking stackdump instead
local $SIG{__WARN__} = sub {
if ($^S) { cluck
"Trapped warning: @_" }
{ confess "Deadly warning: @_"
### END ###
use Getopt::L
my $use_nfd = 0;
my $use_water = 0;
GetOptions("nfd" =& \$use_nfd, "water" =& \$use_water );
print "JSON-&backend-&is_pp = ", JSON-&backend-&is_pp, ", JSON-&backend-&is_xs = ", JSON-&backend-&is_xs, "\n";
sub check {
my $text =
return "is_utf8(): " . (Encode::is_utf8($text) ? "1" : "0") . ", is_utf8(1): " . (Encode::is_utf8($text, 1) ? "1" : "0"). ". ";
my $json_text = "{ \"my_test\" : \"hei p? deg\" }\n";
if ($use_water) {
$json_text = "{ \"water\" : \"水\" }\n";
if ($use_nfd) {
$json_text = NFD($json_text);
print check($json_text), "\$json_text = $json_text";
# test from perluniintro(1)
if (eval { decode_utf8($json_text, Encode::FB_CROAK); 1 }) {
print "string is valid utf8\n";
print "string is not valid utf8\n";
my $hash_ref1 = JSON-&new-&utf8-&decode($json_text);
my $hash_ref2 = decode_json( $json_text );
Running this gives
(hlovdal) localhost:/work/2011/perl_unicode&./json_malformed_utf8.pl
JSON-&backend-&is_pp = 0, JSON-&backend-&is_xs = 1
is_utf8(): 1, is_utf8(1): 1. $json_text = { "my_test" : "hei p? deg" }
string is valid utf8
Uncaught exception: malformed UTF-8 character in JSON string, at character offset 20 (before "\x{5824}eg" }\n") at ./json_malformed_utf8.pl line 96.
at ./json_malformed_utf8.pl line 46
main::__ANON__('malformed UTF-8 character in JSON string, at character offset...') called at ./json_malformed_utf8.pl line 96
(hlovdal) localhost:/work/2011/perl_unicode&./json_malformed_utf8.pl | ./uniquote
Uncaught exception: malformed UTF-8 character in JSON string, at character offset 20 (before "\x{5824}eg" }\n") at ./json_malformed_utf8.pl line 96.
at ./json_malformed_utf8.pl line 46
main::__ANON__('malformed UTF-8 character in JSON string, at character offset...') called at ./json_malformed_utf8.pl line 96
JSON-&backend-&is_pp = 0, JSON-&backend-&is_xs = 1
is_utf8(): 1, is_utf8(1): 1. $json_text = { "my_test" : "hei p\N{U+E5} deg" }
string is valid utf8
(hlovdal) localhost:/work/2011/perl_unicode&./json_malformed_utf8.pl -nfd | ./uniquote
Uncaught exception: Wide character in subroutine entry at ./json_malformed_utf8.pl line 96.
at ./json_malformed_utf8.pl line 46
main::__ANON__('Wide character in subroutine entry at ./json_malformed_utf8.pl line 96.\x{a}') called at ./json_malformed_utf8.pl line 96
JSON-&backend-&is_pp = 0, JSON-&backend-&is_xs = 1
is_utf8(): 1, is_utf8(1): 1. $json_text = { "my_test" : "hei pa\N{U+30A} deg" }
string is valid utf8
(hlovdal) localhost:/work/2011/perl_unicode&./json_malformed_utf8.pl -water
JSON-&backend-&is_pp = 0, JSON-&backend-&is_xs = 1
is_utf8(): 1, is_utf8(1): 1. $json_text = { "water" : "水" }
string is valid utf8
Uncaught exception: Wide character in subroutine entry at ./json_malformed_utf8.pl line 96.
at ./json_malformed_utf8.pl line 46
main::__ANON__('Wide character in subroutine entry at ./json_malformed_utf8.pl line 96.\x{a}') called at ./json_malformed_utf8.pl line 96
(hlovdal) localhost:/work/2011/perl_unicode&./json_malformed_utf8.pl -water | ./uniquote
Uncaught exception: Wide character in subroutine entry at ./json_malformed_utf8.pl line 96.
at ./json_malformed_utf8.pl line 46
main::__ANON__('Wide character in subroutine entry at ./json_malformed_utf8.pl line 96.\x{a}') called at ./json_malformed_utf8.pl line 96
JSON-&backend-&is_pp = 0, JSON-&backend-&is_xs = 1
is_utf8(): 1, is_utf8(1): 1. $json_text = { "water" : "\N{U+6C34}" }
string is valid utf8
(hlovdal) localhost:/work/2011/perl_unicode&./json_malformed_utf8.pl -water --nfd | ./uniquote
Uncaught exception: Wide character in subroutine entry at ./json_malformed_utf8.pl line 96.
at ./json_malformed_utf8.pl line 46
main::__ANON__('Wide character in subroutine entry at ./json_malformed_utf8.pl line 96.\x{a}') called at ./json_malformed_utf8.pl line 96
JSON-&backend-&is_pp = 0, JSON-&backend-&is_xs = 1
is_utf8(): 1, is_utf8(1): 1. $json_text = { "water" : "\N{U+6C34}" }
string is valid utf8
(hlovdal) localhost:/work/2011/perl_unicode&rpm -q perl perl-JSON perl-JSON-XS
perl-5.12.4-159.fc15.x86_64
perl-JSON-2.51-1.fc15.noarch
perl-JSON-XS-2.30-2.fc15.x86_64
(hlovdal) localhost:/work/2011/perl_unicode&
uniquote is from
Thanks to brian for highlighting the solution. Updating the source to use json_text for all normal strings and json_bytes for what is going to be passed to JSON like the following now works like expected:
my $json_bytes = encode('UTF-8', $json_text);
my $hash_ref1 = JSON-&new-&utf8-&decode($json_bytes);
I must say that I think the documentation for the JSON module is extremely unclear and partially misleading.
The phrase "text" (at least to me) implies a string of characters.
So when reading $perl_scalar = decode_json $json_text I have an
expectation of json_text being a UTF-8 encoded string of characters.
Thoroughly re-reading the documentation, knowing what to look for,
I now see it says: "decode_json ... expects an UTF-8 (binary) string and tries to parse
that as an UTF-8 encoded JSON text", however that still is not clear in my opinion.
From my background using a language having some additional non-ASCII
characters, I remember back in the days where you had to guess the code
page being used, email used to just cripple text by stripping of the
8th bit, etc. And "binary" in the context of strings meant a string
containing characters outside the 7-bit ASCII domain.
But what is
"binary" really? Isn't all strings binary at the core level?
The documentation also says "simple and fast interfaces (expect/generate UTF-8)" and "correct unicode handling", first point under "Features", both without mentioning anywhere near that it does not want a string but instead a byte sequence. I will request the
author to at least make this clearer.
17.7k859114
I expand on my answer in .
From reading the JSON docs, I think those functions don't want a character string, but that's what you're trying to give it. Instead, they want a "UTF-8 binary string". That seems odd to me, but I'm guessing that it's mostly to take input directly from an HTTP message instead of something that you type directly in your program. This works because I make a byte string that's the UTF-8 encoded version of your string:
use v5.14;
use feature
qw& unicode_strings &;
use Data::D
use Devel::P
my $filename = 'hei.txt';
my $char_string = qq( { "my_test" : "hei p? deg" } );
open my $fh, '&:encoding(UTF-8)', $
print $fh $char_
say '=' x 70;
my $byte_string = qq( { "my_test" : "hei p\303\245 deg" } );
print "Byte string peek:------\n"; Dump( $byte_string );
decode( $byte_string );
say '=' x 70;
my $raw_string = do {
open my $fh, '&:raw', $
local $/; &$fh&;
print "raw string peek:------\n"; Dump( $raw_string );
decode( $raw_string );
say '=' x 70;
my $char_string = do {
open my $fh, '&:encoding(UTF-8)', $
local $/; &$fh&;
print "char string peek:------\n"; Dump( $char_string );
decode( $char_string );
sub decode {
my $string =
my $hash_ref2 = eval { decode_json( $string ) };
say "Error in sub form: $@" if $@;
print Dumper( $hash_ref2 );
my $hash_ref1 = eval { JSON-&new-&utf8-&decode( $string ) };
say "Error in method form: $@" if $@;
print Dumper( $hash_ref1 );
The output shows that the character string doesn't work, but the byte string versions do:
======================================================================
Byte string peek:------
SV = PV(0x) at 0x
REFCNT = 1
FLAGS = (PADMY,POK,pPOK)
PV = 0x " { \"my_test\" : \"hei p\303\245 deg\" } "\0
'my_test' =& "hei p\x{e5} deg"
'my_test' =& "hei p\x{e5} deg"
======================================================================
raw string peek:------
SV = PV(0x) at 0x
REFCNT = 1
FLAGS = (PADMY,POK,pPOK)
PV = 0x " { \"my_test\" : \"hei p\303\245 deg\" } "\0
'my_test' =& "hei p\x{e5} deg"
'my_test' =& "hei p\x{e5} deg"
======================================================================
char string peek:------
SV = PV(0x) at 0x
REFCNT = 1
FLAGS = (PADMY,POK,pPOK,UTF8)
PV = 0x " { \"my_test\" : \"hei p\303\245 deg\" } "\0 [UTF8 " { "my_test" : "hei p\x{e5} deg" } "]
Error in sub form: malformed UTF-8 character in JSON string, at character offset 21 (before "\x{5824}eg" } ") at utf-8.pl line 51.
Error in method form: malformed UTF-8 character in JSON string, at character offset 21 (before "\x{5824}eg" } ") at utf-8.pl line 55.
So, if you take your character string, which you typed directly into your program, and convert it to a UTF-8 encoded byte string, it works:
use v5.14;
use feature
qw& unicode_strings &;
use Data::D
use Encode qw(encode_utf8);
my $char_string = qq( { "my_test" : "hei p? deg" } );
my $string = encode_utf8( $char_string );
decode( $string );
sub decode {
my $string =
my $hash_ref2 = eval { decode_json( $string ) };
say "Error in sub form: $@" if $@;
print Dumper( $hash_ref2 );
my $hash_ref1 = eval { JSON-&new-&utf8-&decode( $string ) };
say "Error in method form: $@" if $@;
print Dumper( $hash_ref1 );
I think JSON should be smart enough to deal with this so you don't have to think at this level, but that's the way it is (so far).
95.1k27162430
The docs say
$perl_hash_or_arrayref
= decode_json $utf8_encoded_json_
yet you do everything in your power to decode the input before passing it to decode_json.
use Data::Dumper qw( Dumper );
use Encode
qw( encode );
for my $json_text (
qq{{ "my_test" : "hei p? deg" }\n},
qq{{ "water" : "水" }\n},
my $json_utf8 = encode('UTF-8', $json_text);
# Counteract "use utf8;"
my $data = JSON-&new-&utf8-&decode($json_utf8);
local $Data::Dumper::Useqq
local $Data::Dumper::Terse
local $Data::Dumper::Indent = 0;
print(Dumper($data), "\n");
{"my_test" =& "hei p\x{e5} deg"}
{"water" =& "\x{6c34}"}
PS & It would be easier to help you if you didn't have two pages of code to demonstrate a simple problem.
240k8159360
I believe that I have happened by chance across an answer!
pretty symbols come in the websocket and work fine
JSON::XS::decode_json dies "Wide character"
no way out
(write_file of that json darn goes bonkers too, I had to write my own spurt function)
There's a lot of DIY required. Here are my IO commands:
sub spurt {
my $self =
my $file =
my $stuff =
say "Hostinfo: spurting $file (".length($stuff).")";
open my $f, '&', $file || die "O no $!";
binmode $f, ':utf8';
print $f $stuff."\n";
slurp instead does:
my $m = join "", &$f&;
Then to JSON decode stuff that comes in the websocket:
start_timer();
$hostinfo-&spurt('/tmp/elvis', $msg);
my $convert = q{perl -e 'use YAML::S use JSON::XS; use File::S}
.q{print " - reading json from /tmp/elvis\n";}
.q{my $j = read_file("/tmp/elvis");}
.q{print "! json already yaml !~?\n$j\n" if $j =~ /^---/s;}
.q{print " - convert json -& yaml\n";}
.q{my $d = decode_json($j);}
.q{print " - write yaml to /tmp/elvis\n";}
.q{DumpFile("/tmp/elvis", $d);}
.q{print " - done\n";}
`$convert`;
$j = LoadFile('/tmp/elvis');
while (my ($k, $v) = each %$j) {
if (ref \$v eq "SCALAR") {
$j-&{$k} = Encode::decode_utf8($v);
say "Decode in ".show_delta();
Which has just thrown me for a loop - I might need smelling salts!
But the only way I got the path totally cleared for strange symbols travelling disk - perl - websocket/json - JS/HTML/codemirror/whatever and back. The symbols must be written to disk with spurt, with the :utf8 level or mode. I guess Mojo or something I'm using together is breaking that as it all works fine in a perl one liner, and I know I can fix it all, I'm just so goshdarn busy.
There's probably something simple somewhere but I doubt it. Life just overwhelms me sometimes, I declare!
One less madness than this one results in broken characters on disk but working characters in perl and on the other end of the websocket.
48.4k12120167
Your Answer
Sign up or
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Post as a guest
By posting your answer, you agree to the
Not the answer you're looking for?
Browse other questions tagged
Stack Overflow works best with JavaScript enabled404 Not Found
404 Not Found
The requested URL was not found on this server.
您要找的内容已被删除|鲜花 44449
喜欢，就分享给好友吧！
Love si love发布的其它内容
个性网站内热门搜索
共257个QQ网名