Sponsored Content
Full Discussion: Japanese Language in Suse
Operating Systems Linux SuSE Japanese Language in Suse Post 302580187 by dude2cool on Wednesday 7th of December 2011 10:23:23 PM
Old 12-07-2011
Hmm, can you post the output from:

Quote:
file -i jptest-utf8.txt
and
file -i jptest.txt
 

2 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Typing in Japanese language

Hi. I am running Solaris 10,HPUX 11.31 and AIX 6.1. I am trying to get my system to write in Japanese. I can choose the Japanese language for the system to display, but I cannot figure out how to write in Japanese. I have set up my system, and Mozilla (including the menu and web pages) to display... (1 Reply)
Discussion started by: meeraramanathan
1 Replies

2. UNIX and Linux Applications

Japanese Language support (Montavista)

Hi, I am working on Montavista linux. Japanese language is not getting rendered. I executed fc-list command and found that japanese fonts were not installed. But adding sazanami-gothic.ttf from the web is also not working, fc-list does not display japanese fonts yet. How can i add... (0 Replies)
Discussion started by: teluser123
0 Replies
Perl::Critic::Policy::InputOutput::RequireEncodingWithUTUseryContributed Perl DoPerl::Critic::Policy::InputOutput::RequireEncodingWithUTF8Layer(3)

NAME
Perl::Critic::Policy::InputOutput::RequireEncodingWithUTF8Layer - Write "open $fh, q{<:encoding(UTF-8)}, $filename;" instead of "open $fh, q{{<:utf8}, $filename;". AFFILIATION
This Policy is part of the core Perl::Critic distribution. DESCRIPTION
Use of the ":utf8" I/O layer (as opposed to ":encoding(UTF8)" or ":encoding(UTF-8)") was suggested in the Perl documentation up to version 5.8.8. This may be OK for output, but on input ":utf8" does not validate the input, leading to unexpected results. An exploit based on this behavior of ":utf8" is exhibited on PerlMonks at <http://www.perlmonks.org/?node_id=644786>. The exploit involves a string read from an external file and sanitized with "m/^(w+)$/", where $1 nonetheless ends up containing shell meta-characters. To summarize: open $fh, '<:utf8', 'foo.txt'; # BAD open $fh, '<:encoding(UTF8)', 'foo.txt'; # GOOD open $fh, '<:encoding(UTF-8)', 'foo.txt'; # BETTER See the Encode documentation for the difference between "UTF8" and "UTF-8". The short version is that "UTF-8" implements the Unicode standard, and "UTF8" is liberalized. For consistency's sake, this policy checks files opened for output as well as input, For complete coverage it also checks "binmode()" calls, where the direction the operation can not be determined. CONFIGURATION
This Policy is not configurable except for the standard options. NOTES
Because "Perl::Critic" does a static analysis, this policy can not detect cases like my $encoding = ':utf8'; binmode $fh, $encoding; where the encoding is computed. SEE ALSO
PerlIO Encode "perldoc -f binmode" <http://www.socialtext.net/perl5/index.cgi?the_utf8_perlio_layer> <http://www.perlmonks.org/?node_id=644786> AUTHOR
Thomas R. Wyant, III wyant at cpan dot org COPYRIGHT
Copyright (c) 2010-2011 Thomas R. Wyant, III This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.16.3 2014-06-09 Perl::Critic::Policy::InputOutput::RequireEncodingWithUTF8Layer(3)
All times are GMT -4. The time now is 03:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy