Java gbk轉utf-8
1、文件轉碼:使用腳本
gbk轉utf-8的腳本文件:
#!/bin/bash
FILE_SUFFIX="java xml html vm js"
# FILE_SUFFIX="vm"
file_names=""
for x in $FILE_SUFFIX
do
file_names=`find . -name "*.$x" | xargs file -I | grep -v utf-8 | awk -F " |:" '{print $1}'`
for file_name in $file_names
do
# echo $file_name
iconv -f cp936 -t UTF-8 $file_name >$file_name".new" &&
mv -f "$file_name.new" "$file_name"
done
echo "$x ok"
done
find . -name "*.xml" | xargs sed -i "" "/<?xml/s/GBK/UTF-8/g"
find . -name "*.xml" | xargs sed -i "" "/<?xml/s/GB2312/UTF-8/g"
echo "xml head is ok!"
find . -name "pom.xml" | xargs sed -i "" "/<encoding>/s/GBK/UTF-8/g"
find . -name "pom.xml" | xargs sed -i "" "/<encoding>/s/GB2312/UTF-8/g"
find . -name "pom.xml" | xargs sed -i "" "/project.build.sourceEncoding/s/GBK/UTF-8/g"
find . -name "pom.xml" | xargs sed -i "" "/project.reporting.outputEncoding/s/GBK/UTF-8/g"
find . -name "pom.xml" | xargs sed -i "" "s/pop-vender-common-pageframe/pop-vender-common-pageframe-utf8/g"
echo "pom.xml is ok!"
find . -name "*.properties" | xargs sed -i "" "/input.encoding/s/GBK/UTF-8/g"
find . -name "*.properties" | xargs sed -i "" "/output.encoding/s/GBK/UTF-8/g"
echo "velocity properties is OK!"
find . -name "strut*.xml" | xargs sed -i "" '/struts.i18n.encoding/s/GBK/UTF-8/g'
echo "struts xml is ok!"
find . -name "*.vm" | xargs sed -i "" "s/\/common\/js\/jdmsg\/jd-msg.js/\/common\/js\/jdmsg\/jd-msg-utf8.js/g"
find . -name "*.vm" | xargs sed -i "" "/\/ui.datepicker.js/s/<script t/<script charset=\"GBK\" t/g"
find . -name "*.vm" | xargs sed -i "" "/\/jquery-calendar.js/s/<script t/<script charset=\"GBK\" t/g"
echo "vm is ok"
echo "finished"
# echo $file_names
2、文件轉碼后,本地環(huán)境改成utf-8環(huán)境,可能會有部分亂碼文件,手動修復
3、含有中文js引用增加charset="gbk"
如依賴:static.360buying.com、shop.jd.com
4、打包編譯編碼:替換成UTF-8
5、xml設置格式:以前可能為gbk或gb2312,改成utf-8
6、web.xml轉成UTF-8,請求攔截器字符編碼
如使用spring配置
<!--Character Encoding filter(字符集攔截轉換) --> <filter> <filter-name>charsetFilter</filter-name> <filter-class>org.springframework.web.filter.CharacterEncodingFilter</filter-class> <init-param> <param-name>encoding</param-name> <param-value>UTF-8</param-value> </init-param> <init-param> <param-name>forceEncoding</param-name> <param-value>true</param-value> </init-param> </filter>
7、代碼GBK使用
主要是代碼里面寫死GBK方式
如string.getBytes("GBK")替換
8、jdurl配置編碼
增加<property name="charsetName" value="utf-8"/>
避稅分頁中含有中文亂碼
如:jdurl的編碼設置:
<bean class="com.jd.pop.component.url.PopJdUrl">
<property name="url" value="${pop-vender.login.address}"/>
<property name="charsetName" value="utf-8"/>
</bean>
大概是這8條
重點在后面:
這時你會發(fā)現,頁面的get請求請求服務器時還是會出現亂碼,別慌,那是因為tomcat的編碼你還沒有設置.
利用request.setCharacterEncoding("UTF-8");來設置Tomcat接收請求的編碼格式,只對POST方式提交的數據有效,對GET方式提交的數據無效!
要設置GET的編碼,可以修改server.xml文件中,相應的端口的Connector的屬性:URIEncoding="UTF-8",這樣,GET方式提交的數據才會被正確解碼。
<Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" URIEncoding="UTF-8" />
這樣就ok了!!!
以上就是本文的全部內容,希望本文的內容對大家的學習或者工作能帶來一定的幫助,同時也希望多多支持腳本之家!
相關文章
RabbitMQ中的死信隊列(Dead Letter Exchanges)詳解
這篇文章主要介紹了RabbitMQ中的死信隊列(Dead Letter Exchanges)詳解,當RabbitMQ出現死信,可能會導致業(yè)務邏輯錯誤,比如下訂單后修改庫存操作,在下單后因為某種原因,發(fā)送的消息未被簽收,這時庫存數據會出現不一致,需要的朋友可以參考下2023-12-12
Springboot?整合?RocketMQ?收發(fā)消息的配置過程
這篇文章主要介紹了Springboot?整合?RocketMQ?收發(fā)消息,本文給大家介紹的非常詳細,對大家的學習或工作具有一定的參考借鑒價值,需要的朋友可以參考下2021-12-12

