Radialix-软件本地化工具-使用教程Word版

合集下载

软件安装说明

软件安装说明1.安装软件前首先退出所有的杀毒软件2.安装RSLinx 2.57软件,系列号输入任意10位数3.安装RSLogix Emulate500(6.0版本)和RSLogix Emulate5000(19.0版本)这2个软件不需要系列号。

但是Emulate5000不支持64位的操作系统，所以对于像Win8系统安装时，鼠标右键选择setup——属性——兼容性（兼容WIN7）——选择以兼容模式安装。

4.安装RSLogix500软件(8.3英文版,8.1中文版),系列号输入1012后6位输入任意数字5.安装RSLogix5000软件(19版中文)在安装的过程中需要先安装.1.1，如果不能安装的话，就选择手动安装方式：选择DotNet文件夹——dotnetfxsp1.exe（1.1版本），手动安装完成后，再重新安装RSLogix5000软件。

6.安装AB-Key（1）选择AB授权——dekart private disk 2.03——鼠标右键点击prvdisk.exe 选择“以管理员身份运行”——点击连接（装载一个虚拟盘到操作系统）——选择ab key…….文件（在当前文件夹使用）——打开——输入密码（12345）——确定。

完成后在我的计算机会看到一个虚拟盘。

（2）计算机——程序文件——Rockwell software——Utilities——Move Activation -32 bit——将Key从虚拟盘移动到Ｃ盘或Ｄ盘（在Move Key时，如果Ｃ盘不允许写入，可以鼠标右键“以管理员身份运行”）。

*如果仍然不能安装,可以将其转移到移动硬盘(非U盘)，然后再转移到安装盘。

课程内容1.PLC综述——PLC的定义、组成、原理、特点、分类、产生与发展2.SLC选型——处理器、I/O模块、通信与通信模块、Micrologix系列控制器3.SLC编程——内存结构、寻址方式、基本逻辑控制指令、RSLogix500编程软件的使用4.RSLinx的使用——通信配置，程序下载、DDE功能5.SLC配置——I/O配置、高级编程指令6.Controllogix控制器选型——处理器、背板、I/O模块、通信Controllogix编程——任务、程序与例程的关系，数据标签的建立与定义，RSLogix5000软件Controllogix通信——Produce/consumer通信、MSG通信、Controllogix冗余设计——I/O故障诊断AB PLC与网络程序复用数据结构符号标签GSV读取CPU信息提高可靠性。

海地软件使用方法大全

海地软件地面线文件采集的地面点文件是*.TXT的（若是*.csv则不用导入excel），先打开excel，采用“数据--导入外部数据--导入数据”打开“选取数据源”对话框，按照楼主地面点文件保存路径找到地面点文件双击打开，在“文本导入向导”中选择“分隔符号”，点“下一步”，选择“空格”，将采集的xyz坐标导入excel。

在excel 中，若导入后A列为X值，B列为Y值，C列为Z值，则在D列第1行输入公式“=A1&","&B1&","&C1”回车，D1中显示第一个点“X坐标,Y坐标,高程”，选中D1右下角向下拖动公式，直到采集的数据全部在D列中显示。

选中D列中的所有数据，右键“复制”，在CAD中新建图层，设置为当前图层。

选中输入点命令，在cad下方对话框中“指定点：”后，右键“粘贴”，则所有采集的地面点输入CAD内。

用海地“DTM-电子地形图数字化”打开“地形图数字化”对话框，在“选择高程数据层”中选择所输入点所在的图层，点“确定”，生成*.xyz文件，“DTM—构造DTM”，“DTM—生成DTM”，生成*.tin文件，“纵断面—由DTM切纵横断面”，打开“由DTM切纵横断面”对话框，根据现场采集宽度采用“直接输入”方式，输入左右边距（若输入宽度超过DTM的范围则无法提取），设置切值方式、切值范围、地面线文件格式，设置输出文件的名称及保存路径（注意不要覆盖了实测的dmg文件），点确定则生成了*.dmg、*.dmx文件，若采集的数据中无路线中桩位置坐标、高程，为了提取的地面线的准确，应按上述方法将中桩点（XYZ）输入CAD中再生成DTM，提取*.dmx文件。

2.1.2总体流程1、您只需按照以下程序操作即可很快浏览到Hard的主要功能，轻松了解它的使用过程。

2、流程考虑到初学者还没有熟练掌握Hard系统，故在流程中不考虑“数模”，即不考虑系统在三维环境中的操作方法。

西ря什表itzerland style Expansion Desktop用户手册说明书

Seagate Expansion Desktop 用户手册单击这里以访问本文档的最新在线版本。

您还将找到最新的内容，以及可扩展的说明、更轻松的导航和搜索功能。

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents1欢迎使用包装内容最低系统要求2使用入门连接电源连接到计算机备份文件3格式化和分区（可选）选择文件系统格式格式化说明4从您的计算机安全移除设备Windows Mac 5常见问题解答所有用户Windows Mac 6Regulatory Compliance China RoHS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 端口. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 操作系统. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 同时兼容 Windows 和 Mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 针对 Windows 优化性能. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 针对 macOS 优化性能. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 了解更多. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 通过 Finder 窗口退出. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 通过桌面退出. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 问题：我的文件传输速度很慢. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 问题：我的计算机只有 USB-C 端口. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 问题：我必须对 USB 设备使用 USB 集线器. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 问题：提供的 USB 电缆太短. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 问题：我收到了文件传输错误消息. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 问题：计算机中未显示硬盘图标. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 问题：我的桌面上未显示硬盘图标4444455668888899101010101011111111111212121213131414Taiwan RoHS14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .欢迎使用包装内容Seagate Expansion Desktop18W 电源适配器USB 3.0 电缆（USB micro-B 转 USB-A）快速入门指南最低系统要求端口使用随附的电缆将希捷设备连接至带有 USB-A 端口的计算机。

Ipinstall软件工具操作说明word版本

Ipinstall软件工具操作说明Ipinstall软件工具是用于联网型对讲系统中网络设备的属性及参数修改，该设备在系统中是否能正常运行，其属性和参数的设置起着决定性的作用，然而设备的属性、参数设置是否能成功地设置好，则关系着Ipinstall软件工具的正确操作与否。

一、“Ipinstall”软件工具的运行双击该软件工具图标“”运行软件工具，单击“刷新”按钮，显示系统中设备的IP地址及相关属性，如图1。

安居宝网络设备属性设置二、设备属性设置单击要修改属性的设备IP，接着单击“设备属性”按钮，此时将会显示设备的相关属性，如图2。

操作步骤：单击设备IP→单击“设备属性”钮→修改属性→单击“设置”钮→待设备重启。

在设备属性设置项中，可修改的项有IP地址和固件版本。

注：1.设备“IP地址”在系统中是唯一的。

2.设备“固件版本”指的是PCB板间的版本。

三、设备参数设置单击要修改的设备IP，接着单击“设备参数设置”钮，此时将会显示该设备初始参数，如图3。

操作步骤：单击“设备IP”→单击“设备参数设置”钮→修改设备参数→单击“设置”钮→待设备重启。

四、设备软件程序升级在设备参数设置的界面下进行设备的软件程序升级，首先要选择程序的类别，在“程序类别”的下拉列表框中选择对应的设备程序类别，然后打开设备程序，点击“更新”按钮。

操作步骤：单击“设备IP”→单击“设备参数设置”钮→选择程序类别→选择对应的设备程序→单击“更新”钮→待设备重启。

程序软件升级的次序：引导程序→主程序→程序数据。

注：表格中“x”代表程序软件的版本号。

五、注意事项1.在对设备属性或参数修改完时，点击了“设置”按钮后；或者对设备进行程序软件升级时，点击“更新”按钮后，必须等待设备重启成功（可见该设备的IP地址），方可进行下一步对设备属性、参数的修改、程序软件的升级。

2.在对设备属性、参数修改或程序软件升级，需再次操作时，必须关闭当前属性、参数修改窗口，返回至图1窗口，单击“刷新”按钮，直至可见该设备IP地址，方可重新进行设备相关的属性、参数修改或程序软件的升级。

软件汉化教程(完整版)

软件汉化全教程初识资源『资源简介』软件界面上的各种文字、图像、图标等，在编程的时候根据特定的格式分门别类地存放在软件里面，这些特定的格式就叫“资源”(Resource)。

软件资源分为标准资源和非标准资源(简称非标)，标准资源通常可以通过PE类资源查看工具(如：PE Explorer、ResScope 等)可视化查看编辑(VB除外)，而非标目前还无法实现可视化预览。

特别注意的是VB 程序资源比较特殊，上述分类概念不适用，但汉化人一般把VB 窗体汉化器等提取的窗体资源称为标准资源，而通过点睛字符替换器提取的VB 字串、Unicode 字串和ASCII 字串均称为非标。

常见的标准资源通常有Bitmap(位图)、Menu(菜单)、Dialog(对话框)、String(字符串)、RCData(RC-数据)、Cursor(光标)、Accelerator(加速器)、Icon(图标)、Version(版本)、Toolbar(工具栏)、Form(窗体)，其中RC-data多见于Delphi程序中，Form多见于VB程序中。

非标资源主要包括ASCII字串、Unicode字串两大类。

标准资源汉化后，在软件界面或调用信息时显示、但又不出现在上述标准资源中的字串多数属于非标资源。

『汉化资源分布』由于编写软件所使用的编程工具不同，软件中的汉化资源发布位置也不尽相同，常见如下：1. VC 类标准资源由Microsoft Visual C++ 编写，汉化资源一般分布于Menu、Dialog、String 等；2.Delphi 类标准资源由Borland Delphi 编写，汉化资源一般分布在Rcdata 和String 中；3.VB 类标准资源由Microsoft Visual Basic 编写，汉化资源一般出现在Form 窗体中；3.非标资源Unicode 字串和ASCII 字串，后者又可细分为VB 字串、Delphi 字串和其他ASCII 字串。

简体中文自由软件本地化工作指南说明书

简体中文自由软件本地化工作指南Free Software Localization Guide for Chinese (simplified)By Aron Xu and Mingye WangVersion 1.2; Released under CC-BY-NC-SA 3.0 Unported.本文档提供自由软件本地化的一般性指引，主要包含 Gettext翻译的编辑、验证和提交，以及目前较通行的写作风格信息。

目录1工作流程 (1)1.1准备 (1)1.2协调 (1)1.3翻译 (2)1.4提交 (3)1.5语言要求 (3)2PO文件格式和要求 (3)2.1基础信息 (3)2.2文件头 (4)2.3字符转义和格式 (5)2.4排版风格 (6)2.5注释和字符串属性 (8)3工具使用速查 (9)3.1Gettext工具集 (9)3.2Intltool工具集 (9)后记 (10)版本历史Rev. 1.22015-09-12重制ODT。

添加必要注解，删减陈旧内容，今年是2015年。

Rev. 1.12009-11-07更新格式信息。

Rev. 1.02009-08-26初始版本，网页发布于i18n-zh。

感谢GNU计划、LibreOffice和推动LibreOffice产生的乌龟壳公司。

本页的技术用途在于显式定义LibreOffice在首页后原会自动插入的空白页。

1工作流程自由软件翻译的工作流程基本分为准备、协调、翻译、提交四步，不同项目各有不同。

一些翻译平台，如Launchpad，Transifex和Crowdin，提供基于网页的提交方式。

Align 软件工具用户指南说明书

Align: Start, Stop, Continue Guide Regional EntitiesExecutive SummaryTo what level is my work impacted due to this change? ModerateUse this document to familiarize yourself with Regional Entity Align process changes! Align is a new software tool that support the ERO’s vision of a single business process shared across our industry, tracking compliance data through a central hub that integrates CORES registration data with compliance monitoring and enforcement activities. Release 1 will include self-reporting/self-logging, enforcement processing,and mitigation functionality in the Align system, as well as the deployment of the ERO Secure Evidence Locker (ERO SEL). The ERO SEL will be used to collect registered entity-provided evidence as part of the ERO Enterprise’s CMEP activities. Align andthe SEL are built in a way that requires changes to the processes and language youuse today, and this guide will help you understand those changes and what to expectupon our first production release.It is important to note that Align Release 1 will utilize a phased launch approach withthe initial two regions (Texas RE & MRO) going live first with a certain segment oftheir registered entities. The remaining four regions will transition to Alignapproximately 4 to 6 weeks after the initial Release 1 launch. During the transitionyou will complete all monitoring, enforcement, and reporting functions usingexisting tools and processes for regions and registered entities not transitioned toAlign .Overview Start/Stop/Continue What should you start doing? For noncompliance that begins in Align• Performing Self-Log (if applicable based on your regional self-log process) & Self-Report processes in Align • Performing enforcement activities (e.g., Violation Processing, Dismissals, CEs,FFTs, and Settlement/NOCV processes) in Align • Performing mitigating activities & Mitigation Plan tracking and reportingprocesses in Align • Initiating PNCs in Align if discovered through a Self-Certification, PDS, TFE,Compliance Audit, Spot Check, Compliance Investigation or Complaint • If necessary, review associated evidence in the ERO SELImpact ScaleSignificant • Significant impact resulting in fundamental changes in tools and/or processes. You will likely require significant training to perform in your role. In addition, new tasks may be added, orcurrent tasks may be eliminated from your roleModerate• Several ways in which you do your jobs will change. You may have new work, requiring new skills that will potentially require some training Low • Minimal changes to the way you do your jobs. Existing tools and processes will remain in place.Training not required.What should youcontinue doing? Additional DetailsWhat should youstop doing? • Performing processes related to Self-Certifications, Periodic Data Submittals, Technical Feasibility Exceptions, Compliance Audits, Spot Checks, Compliance Investigations and Complaints using existing tools• Performing all Compliance Planning activities (e.g., COP, IRA, ICE) usingexisting processes and tools• Reporting on non-Release 1 activities using existing tools and processes (e.g.,Self-certifications, PDS, Audits, etc.)For noncompliance that began in CITS/CDMS• Performing your enforcement activities (e.g., Violation Processing, Dismissals,CEs, FFTs, and Settlement/NOCV) using existing tools (e.g., WebCDMS, CITS)• Performing your mitigation activities & Mitigation Plan tracking and reportingprocesses using existing tools (e.g., WebCDMS, CITS)• The Align Release 1 Start, Stop, Continue Executive Summary provides only high-level information onprocess, terminology, and tool changes• Please see the section below for detailed information on what processes will be completed in Alignvs. existing toolsFor noncompliance that began in CITS/CDMS • Performing your Self-Log (if applicable based on your regional self-log process) &Self-Report processes using existing tools (e.g., WebCDMS, CITS)• Collecting evidence through legacy toolsDetailed Guides:1. Self-Reporting & Self-LoggingTo what level is my work impacted due to this change? ModerateWhen a Registered Entity has identified a potential non-compliance (PNC), they willcreate the Self-Report in Align. An entity that is approved for self-logging will eitheradd Self-Log items directly into Align or continue submitting Self-Logs via spreadsheetdependent on regional processes.OverviewStart/Stop/Continue What should youstart doing? What should youstop doing? • Provisioning access for Self-Logging in Align if applicable based on yourregional self-log process• Receiving notification that Self-Log & Self Report has been initiated in Align• Initiating preliminary screen process in Align tool• Receiving evidence through the ERO SEL• Receiving notifications that Self-Log (if applicable based on your regional self-logprocess) & Self-Report has been initiated in existing tools (e.g., CITS, WebCDMS,etc.)• Initiating preliminary screen process in existing tools (e.g., CITS, WebCDMS, etc.)• Receiving evidence through legacy toolsFor non-U.S. jurisdictional noncompliance • Receiving notifications that Self-Log & Self-Report has been initiated inexisting tools (e.g., CITS, WebCDMS, etc.)• Initiating preliminary screen process in existing tools (e.g., CITS, WebCDMS,etc.)• Receiving evidence through legacy toolsWhat should youcontinue doing?Additional Details•Self-Reports and Self-Logs allow flexibility to add mitigating activities before or after Registered Entity submits initial report•Whether or not the entity chooses to add mitigating activities to the report, your action in this process is the same; you’ll be notified of the new report and initiate the preliminary screening process •Any Registered Entity can report a PNC through a Self-Report by default•The ability to Self-Log is exclusive to those entities that have been vetted through an evaluation process, and must be provisioning by the CEA in Align•If the entity has not been vetted into the Self-Logging program, they will not have the ability to submit Self-Logs in Align; the vetting process is done outside of Align2.Preliminary Screen & Potential Non-Compliance Review (PNCR)OverviewOnce a Self-Report or Self-Log is submitted by a Registered Entity, it triggers thepreliminary screen and the Potential Non-Compliance Review (PNCR). These aretightly linked and will be reviewed below.To what level is my work impacted due to this change?ModerateStart/Stop/ContinueWhat should you start doing? What should youstop doing? For noncompliance submitted into AlignPreliminary Screen:•Reviewing PNC, within 5 business days of submittal, to:o ensure the reliability standard requirement that was potentiallyviolated was applicable, approved, and in effect at the time of thePNCo check if the PNC violates the same standard and requirements as another possible violation or alleged violation already beingprocessed▪if yes, you may choose to link PNC to existing openenforcement action (OEA)▪if no, evaluate if PNC is a true duplicate, and mark as failedscreen•If PNC passes, marking PNC passed in Align•If PNC fails, marking as failed screen in AlignPotential non-Compliance Review (PNCR):•Completing PNC Review (e.g., Risk Analysis, Root Cause Analysis, Extent of Condition Review) in Align•Making determination on PNC and marking accordingly in Aligno If out of compliance, make all comments and proceed to enforcement activities in Align•If needed, issuing a formal RFI through Align•If necessary, reviewing associated evidence in the ERO SEL•Following existing preliminary screen for U.S. jurisdictional noncompliance using existing tools (e.g., CITS, WebCDMS, etc.)•Follow-up regularly with Registered Entities to ensure you have all required information to arrive at a recommendation for enforcement action •Evaluating the scope, risk impact, root cause, and mitigation of the issue to arrive at a recommendation for enforcement actionFor noncompliance submitted into CITS/CDMS•Following existing PNCR process using existing tools (e.g., CITS, WebCDMS, etc.)•Reviewing evidence through legacy toolsWhat should you continue doing?Additional Details•When you pass screening in Align it will notify NERC and the Registered Entity that a noncompliance exists, and that entity should retain all data and documents for noncompliance •We will no longer use NERC violation IDs. In Align, each record will have a unique ID for the entire process•In Align, the notice of noncompliance will also serve as the NPV3.Enforcement ActivitiesOverviewSubmitting a PNCR will automatically create an Enforcement Action (EA) record inAlign. The EA can then follow several different enforcement pathways. This sectionfocuses on Violation Processing, Dismissals, Compliance Exceptions, Find, Fix & Trackprocesses, and Settlement and Confirmed Violations processes.To what level is my work impacted due to this change? SignificantStart/Stop/ContinueWhat should you start doing? For noncompliance submitted into AlignViolation Processing:•Reviewing risk assessment and analyzing circumstances of PNC in Align •Deciding disposition of PNC (e.g., CE, FFT, dismissal, etc.) in Align•Issuing NAVAPS in Align•Checking to see if Registered Entity has Contested the NAVAPS/NOCV in Align •If applicable, sending RFI to Registered Entity in AlignDismissals:•Confirming if record is Compliance Investigation in Align•If Compliance Investigation, asking NERC to complete review outside of Align •Determining type of dismissal and designating the record accordingly in Align •Sending dismissal letter to Registered Entity in Align•Closing record in AlignCompliance Exception (CE) & Find, Fix, Tack Processes:•Creating disposition record of CE type or FFT and providing rationale in Align •Sending CE or FFT letter to Registered Entity in Align•Sending CE or FFT to NERC for review in Align (if Entity does not opt-out) •Closing record upon completion of 60-day review period and mitigating activities or Mitigation PlanSettlement/Confirmed Violation Process•Issuing NAVAPS to Registered Entity in Align•Uploading executed settlement agreement in Align•Uploading NOP/SNOP, before submitting it to NERC for review, in Align •Marking the Settlement/confirmed violation complete in Align•Sending NOCV to Registered Entity in Align•Closing out Settlement/confirmed violation in Align, and sending a notice of completion to NERC and the Entity•If necessary, reviewing associated evidence in the ERO SELWhat should youstop doing?•N/A4. Mitigation Plans & Mitigating ActivitiesTo what level is my work impacted due to this change? SignificantThe key process change in Mitigation is that the Registered Entity will submit mitigating activities instead of Mitigation Plans by default. If the mitigating activitiesneeds to be converted to a plan, the CEA will make that conversion in Align.The other change to the Mitigation workflow is that Align will replace existing methodsof submission, review, and tracking. Registered Entities will need to stop using existingtools like webCDMS or CITS and stop any manual tracking of mitigation activities.Everything should be submitted, reviewed and tracked in Align.Overview What should youcontinue doing?• Using preexisting rationale and definitions to decide disposition • Calculating the potential penalty and creating a draft settlement agreement in collaboration with the Registered Entity using existing processes and tools • Coordinating regularly with Registered Entity contacts to work through Enforcement workflow • Deciding if the disposition should be changed to a confirmed violation if Registered Entity does not agree to terms of settlement using existing processes and tools For noncompliance submitted into CITS/CDMS • Completing all Enforcement Activities (e.g., Violation Processing, Dismissals, CEs, FFTs, and Settlement/Confirmed violation) using existing tools (e.g., WebCDMS, CITS, etc.) and processes • Reviewing evidence through legacy toolsAdditional Details• A CEA cannot issue any dismissal to a Compliance Investigation before NERC is able to review• NERC does not need a notification of a dismissal; however, it should be visible to them upon login tothe system (i.e., dashboard view)Start/Stop/ContinueWhat should you start doing? For noncompliance submitted into AlignMitigating Activities:•Reviewing mitigating activities in Align•If applicable, requesting revision of mitigating activities in Align•Accepting mitigating activities in Align•Accepting or verifying completion of mitigating activities in Align•If necessary, sending RFI to Registered Entity in AlignMitigation Plans:•If necessary, converting mitigating activities to Mitigation Plan from in Align•Reviewing Mitigation Plan to determine if it will be accepted in Align•If applicable, extending Mitigation Plan review period in Align•Accepting or rejecting Mitigation Plan in Align•Monitoring new facts and circumstances to determine if a Mitigation Plan may need to be revised in Align•If applicable, receiving Mitigation Plan revisions, after acceptance, from Registered Entities in Align•If necessary, reviewing associated evidence in the ERO SELWhat should you stop doing? Mitigating Activities:•Creating, reviewing, and rejecting or approving mitigating activities in existing tools (e.g., CITS, WebCDMS, etc.)Mitigation Plans:•Creating, reviewing, and rejecting or approving Mitigation Plans in existing tools (e.g., CITS, WebCDMS, etc.)•Collecting evidence through legacy toolsWhat should you continue doing? •Coordinating regularly with your Registered Entity to help ensure mitigation activities and Mitigation Plan deadlines are met, and all necessary evidence is providedFor noncompliance submitted into CITS/CDMS and non-U.S. Jurisdictional noncompliance•Creating, reviewing, and rejecting or approving mitigating activities in existing tools (e.g., CITS, WebCDMS, etc.)Mitigation Plans:•Creating, reviewing, and rejecting or approving Mitigation Plans in existing tools (e.g., CITS, WebCDMS, etc.)•Collecting evidence through legacy tools5. Tracking Mitigation PlansTo what level is my work impacted due to this change? ModerateAdditional Details• Mitigating activities will be submitted by default with each PNC• If mitigating activities need to be transitioned to a formal Mitigation Plan, the CEA will need to initiatethe process in Align• Non-US Jurisdiction Mitigation Plans do not go to FERC• A Registered Entity may request the ability to revise their Mitigation Plan at any time by contactingthe regional point of contact(s) outside of Align. The regional point of contact(s) will take action in Align to send back to the Entity for revisiono The reason for requesting a revision may include expanding the scope of the PNC orMitigation Plan due to new information being discovered. The CEA should determine if arevision is appropriate or if a new Self-Report should be createdOnce a Mitigation Plan is submitted, the Registered Entity will begin tracking againstthe plan. They have the ability to update the actual completion date and uploadevidence for verification from submission of plan through verification. At this point,you will begin monitoring progress of the Mitigation Plan in Align. After the RegisteredEntity certifies that their Mitigation Plan is complete, you can choose to accept, verifyor reject the completion.OverviewStart/Stop/Continue What should youstart doing? For noncompliance submitted into Align • Reviewing the submitted Mitigation Plan and confirming the milestones and activities in Align • If Milestone extension is requested, choosing to extend milestone completiondate in Align• If applicable, escalating the disposition path if the Registered Entity is notadhering to their Mitigation Plan in Align • Reviewing evidence submitted with Mitigation Plan to verify completion in Align • Verify that the completion date certified by the Registered Entity is accurate in Align • If applicable, sending RFI to Registered Entity in Align • If necessary, reviewing associated evidence in the ERO SEL6. Self-Certifications, PDS, TFEs, Compliance Audits, Spot Checks, Compliance Investigations, and ComplaintsTo what level is my work impacted due to this change? LowWhat should youstop doing? • N/AWhat should youcontinue doing? •Coordinate regularly with your Registered Entity to help ensure Mitigation Plan deadlines are met, and all necessary evidence is provided For noncompliance submitted into CITS/CDMS and non-U.S. Jurisdictional noncompliance • Tracking Mitigation Plan milestone completion in existing tools (e.g., CITS, WebCDMS, etc.) • Sending requested information via email or secure file transfers • Sending verification letter or notice of plan acceptance in existing tools (e.g., CITS, WebCDMS, etc.) • Continue collecting evidence through legacy tools• Additional Details• The CEA has the option to escalate the disposition path if the Registered Entity is not adhering to theirMitigation Plan• An officer, employee, attorney or other authorized representative at the Registered Entity mustcertify the completion of all activities laid out in the Mitigation PlanThe processes for Self-Certifications, Periodic Data Submittals (PDS), Technical Feasibility Exceptions (TFE), Compliance Audits, Spot Checks, Compliance Investigations, and Complaints will not change due to Align Release 1. Continue to use the current established process & systems for receiving and responding to Self-Certifications, PDS, TFEs, Compliance Audits, Spot Checks, Compliance Investigations and triggering Technical Feasibility Exceptions and Complaints. Overview Start/Stop/Continue What should youstart doing? • Creating a PNC in Align if discovered through a Self-Certification, PDS,Compliance Audit, Spot Check, Compliance Investigation or Complaint7. Support ProcessTo what level is my work impacted due to this change? LowWhat should youstop doing? • Processing PNCs in existing tools if discovered through Self-Certification, PDS,Compliance Audit, Spot Check, Compliance Investigation or Complaint in AlignWhat should youcontinue doing? • Sending, receiving and responding to Self-Certifications, Periodic Data Submittals Self-Certification, PDS, Compliance Audit, Spot Check orCompliance Investigation using existing tools (e.g., CITS, WebCDMS, etc.)• Documenting and tracking TFEs and Complaints using existing tools (e.g.,CITS, WebCDMS, etc.)Additional Details• It is important to note that if a potential Non-Compliance (PNC) is the outcome of one of the aboveactivities during Release 1, that PNC must be initiated in Align. Once new PNC is initiated, follow the new Align process for completionSupport for Align will follow the new ERO Enterprise Application Support Process. Support of enterprise applications, including Align, will follow a disciplined process to ensure requests are handled in a timely manner, and are prioritized according to business importance and criticality. Overview Start/Stop/Continue What should youstart doing? • Requesting and receiving support for the Align application and existing CMEPapplications via a support request ticket (enabled by FootPrints) fornoncompliance started in Align.What should youstop doing? •N/A What should youcontinue doing?• Requesting and receiving support for all existing CMEP applications using current processes and tools for noncompliance started in CITS/CDMS.。

Radial Engineering DAN-RX 用户指南说明书

True to the Music™User GuideDAN-RX™2-Ch Dante ® ReceiverRadial Engineering Ltd.1588 Kebet Way, Port CoquitlamBritish Columbia, Canada, V3C 5M5 Tel: 604-942-1001 • Fax: 604-942-1010Email:******************Table of Contents PageFeatures ...................................................................................1-2Overview.......................................................................................3Getting Started .............................................................................4Making Connections .....................................................................5Using the Headphone Amplifier ....................................................6Block Diagram ..............................................................................7Specifications ...............................................................................8Warranty .......................................................................Back coverCongratulations on purchasing the Radial DiNET DAN-RX™! The DAN-RX is a high-resolution digital-to-analog converter that is designed to connect to a Dante-enabled Ethernet network — seamlessly transferring the audio stream to a pair of balanced audio outputs to feed a PA, recording device or broadcast mixing console.This manual covers the setup and operation of the DAN-RX in various applications. Please take a few minutes to read through and familiarize yourself with the DAN-RX features and functions. If you have any questions that are not covered in this manual, please consult the FAQ section on our website. This is where we post the latest updates. If you still do not find what you are lookingfor,*******************************************and we will do our best to reply in short order.Radial ® DAN-RX™ User GuidefeaTUreS4912378101.HeaDPHone: Sets output level of the headphone amplifi er. Mini 3.5mm (1/8”) TRS headphone output. Works with earbuds and standard headphones.2.SYnC leDs: Red LED is illuminated when unit is powered. Green LED will illuminate once connected to an Ethernet network. Flashing green LED indicates that the DAN-RX is in master clock mode, solid green LED indicates that it is in slave mode.3.eTHerneT PorT: Connects to the Dante network via standard CAT5e or CAT6 Ethernet cable. This port delivers the digital audio signal from the network and powers the DAN-RX when Power over Ethernet (PoE) is available.4.SYS leDs: Red LED illuminates when power is fi rst applied. Switches to green LED once Dante processor becomes active.5.+15V leD: Will illuminate when the DAN-RX is receiving power via the included DC power adapter.6.Poe leD: Will illuminate when the DAN-RX is receiving Power over Ethernet (PoE).567. lefT anD rigHT Xlr oUT: Balanced analog audio outputs. Output level is controlled by audio playback source.8. PoWer: 15VDC connection for use with included Radial power adapter.9.CaBle ClamP: Used to secure the power supply cable (when used) to prevent accidental disconnection.10. no SliP PaD: Provides electrical and mechanical isolation andkeeps the DAN-RX from sliding around.11. groUnD lifT: Lifts pin-1 onboth XLR outputs to eliminate buzz and hum from ground loops. Move the switch to the right (towards the Ethernet input) to lift the ground.11oVerVieWThe Radial DiNET DAN-RX is a professional grade digital-to-analog audio converter designed specifi cally for use with Dante-enabled networks. It allows you to create a stereo audio endpoint at any location within a Dante network, featuring an Ethernet connector to receive the digital signal, and balanced analog outputs to feed mixing consoles, power amplifi ers, or self-powered speakers. High quality 24bit/96kHz converters provide pristine audio and ensure that the digital source content is reproduced as faithfully as possible, and a rugged 14-gauge steel chassis with a bookend design protects the connectors from damage. The DAN-RX also features a built-in headphone amplifi er with an adjustable level control, allowing you to easily check the audio signals, or feed a monitor mix to any destination.The DAN-RX is easy to use, with no setup required on the device itself. It is completely confi gured by Dante Controller, which manages digital audio routing across the Dante network. Dante Controller is a software application by Audinate™ that allows the user to manage all Dante-enabled devices across a network. Use Dante Controller to route audio to the DAN-RX and all other components on the network. Simply plug the DAN-RX into the network and it will automatically appear as an available output device within Dante Controller. The DAN-RX will initially have the name “DiNET-RX-xxxxxx”, where the last 6 digits will be the unique media access control address (MAC address) of your DAN-RX. As this can be changed to a user-generated name using Dante Controller, we recommend writing down the MAC address of your unit in the space provided below for future reference.record your Dan-rX maC address here:DineT-rX-__________________Dante Controller can be downloaded for free at . For latest firmware for the DAN-RX please visit .Dante networkDante networkCat 5e / Cat6geTTing STarTeDBefore making any connections, always ensure your amplifi ers or speakers are either turned down or turned off in order to protect sensitive components from damage due to loud transients that can occur when plugging in or turning on various components.PoWering THe Dan-rXPoePower for the DAN-RX can be provided via power over ethernet (PoE) from a PoE-capable network switch or a separate PoE injector. Once power is available, the side panel PoE LED indicator will illuminate and the DAN-RX will be ready to use.Power SupplyThe included 15VDC power supply is provided for use when PoE is not available. Once you have connected the DAN-RX to the Ethernet switch, plug in the power supply. The side panel +15VDC LED will illuminate and the DAN-RX will be ready to use.eTHerneT ConneCTionThe DAN-RX connects to the Ethernet switch using a standard CAT5e or CAT6 cable. Once the Ethernet switch is connected to a computer running the Dante Controller software, the DAN-RX will appear as anavailable receive device.As a backup option, the DAN-RX is designed to be able to have both PoE and the 15VDC adaptor connected at the same time. If one fails, the otherwill maintain power without switch-over noise.making ConneCTionSConnect two standard low-impedance XLR cables from the LEFT and RIGHT outputs to the inputs of your PA or recording system. These XLR outputs conform to the AES standard and are balanced to drive long cable runs up to 100 meters (300’) without noise, and are suitable for connecting the DAN-RX to professional mixing consoles, preamps and power amplifi ers. The signal level at these outputs is controlled by the audio playback source.imPorTanT noTe: The DAN-RX does not require phantom power tooperate. The DAN-RX is equipped with blocking capacitors to prevent damage from DC voltage, but for best results please ensure that thephantom power is switched off when connecting to the microphoneinput of a mixer.Audio connections for PA system and recording systems usebalanced XLR cables up to 100 meters (300’).USing THe HeaDPHone amPlifierThe DAN-RX is equipped with a dedicated stereo headphone output. The 3.5mm (1/8”) output is designed for both ear buds and standard TRS stereo headphones wired tip-left, ring-right and the sleeve is ground. The volume control on the DAN-RX affects the headphone output only, as it is designed for testing purposes rather than setting the level of the XLR outputs.Be careful! The DAN-RX is designed for professional use. The headphone amplifi er is very powerful and is capable of high sound levels that could damage your hearing. Always ensure the volume control is set to its lowest point (fully counter-clockwise) when plugging in headphones, and slowly increase the level to a satisfactory level. If no signal is present, ensure that audio is routed to the unit via the Dante Controller software.Not all headphones are created equally! Always start at the lowest volume when switching headphones. While the DAN-RX is designed to work with headphones of all different impedances, volume level can change drastically from pair to pair.Headphone Safety Warning Caution: Very Loud Ampliﬁ erAs with all products capable of producing high sound pressure levels (SPL), usersmust be very careful to avoid the hearing damage that may occur from prolonged exposure. This is particularly important when applied to headphones, as prolonged listening at high SPL’s will eventually cause tinnitus and can lead to partial or complete loss of hearing. Please be aware of the recommended exposure limits within your jurisdiction and follow them closely. The user agrees that Radial Engineering Ltd is not liable for any health effects resulting from the use of this product and the user clearly understands that he or she is entirely responsible for the safe and proper use of this product. Please consult the Radial Limited Warranty for further details.BloCk Diagram** Subject to change without notice.SPeCifiCaTionS** Subject to change without notice.Audio Circuit Type: ............................................High current balanced active output device Number of Channels: .. (2)Sample Rate: .....................................................44.1kHz, 48kHz, 88.2kHz, and 96kHz Bit Depth: ...........................................................24 bitFrequency Response: ......................................20Hz-20kHz Idle Channel Noise: ...........................................-108dB Dynamic Range: ...............................................>100dB Channel Separation: ..........................................>75dBGain: ..................................................................8dBu max @ 0dBfs Total Harmonic Distortion + Noise: ....................0.007% @ -6dBfs Output Impedance: ............................................150ΩPower Consumption: .........................................1.25WFeaturesInput Connections: .............................................RJ45 EthernetOutput Connectors: ...........................................2x XLR male, 1x 3.5mm headphone out LED Indicators: ..................................................SYNC, SYS, +15V, and PoEExtras: ...............................................................Headphone amplifier with level controlGeneralPower: ...............................................................15VDC 400mA (included) or PoE Power over Ethernet (PoE) ................................Class 1 IEEE 802.3afFCC Approval: ...................................................Meets FCC Part 15B Class A Construction: .....................................................14-gauge steelFinish:................................................................Durable powder coatWarranty: ..........................................................Radial 3-year, transferableC H A S S I S _G N DU N D F T®THREE YEAR TRANSFERABLE LIMITED WARRANTYRADIAL ENGINEERING LTD. (“Radial”) warrants this product to be free from defects in material and workmanship and will remedy any such defects free of charge according to the terms of this warranty. Radial will repair or replace (at its option) any defective component(s) of this product (excluding fi nish and wear and tear on components under normal use) for a period of three (3) years from the original date of purchase. In the event that a particular product is no longer available, Radial reserves the right to replace the product with a similar product of equal or greater value. In the unlikely event that a defect isuncovered,************************************************************RA number (Return Authorization number) before the 3 year warranty period expires. The product must be returned prepaid in the original shipping container (or equivalent) to Radial or to an authorized Radial repair centre and you must assume the risk of loss or damage. A copy of the original invoice showing date of purchase and the dealer name must accompany any request for work to be performed under this limited and transferable warranty. This warranty shall not apply if the product has been damaged due to abuse, misuse, misapplication, accident or as a result of service or modifi cation by any other than an authorized Radial repair center.THERE ARE NO EXPRESSED WARRANTIES OTHER THAN THOSE ON THE FACE HEREOF AND DESCRIBED ABOVE. NO WARRANTIES WHETHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE SHALL EXTEND BEYOND THE RESPECTIVE WARRANTY PERIOD DESCRIBED ABOVE OF THREE YEARS. RADIAL SHALL NOT BE RESPONSIBLE OR LIABLE FOR ANY SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES OR LOSS ARISING FROM THE USE OF THIS PRODUCT. THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS, AND YOU MAY ALSO HAVE OTHER RIGHTS, WHICH MAY VARY DEPENDING ON WHERE YOU LIVE AND WHERE THE PRODUCT WAS PURCHASED.Radial ® DAN-RX™ User Guide - Part #: R870 1033 00 / 06-2017 Copyright 2017 Radial Engineering Ltd. All rights reserved. Specifi cations and appearance subject to change without notice.Radial Engineering Ltd.1588 Kebet Way, Port Coquitlam, British Columbia, V3C 5M5 Tel:604-942-1001•Fax:604-942-1010•Email:******************T o meet the requirements of California Proposition 65, it is our responsibility to inform you of the following:Warning: This product contains chemicals known to the State of California to cause cancer, birth defects or other reproductive harm.Please take proper care when handling and consult local government regulations before discarding.。

1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。

Radialix 是一款功能比较强大的软件本地化工具，支持以 VC++、Delphi、.Net 等语言编写的软件、以及 INI 格式文本文件的本地化。

尤其是它具有非标资源的本地化功能、以及可以设置更多的资源属性。

以下是开发商的描述。

- PE32、PE32+ 文件、.NET 程序集，资源和各类文本文件的本地化
- 加载子程序集的 .NET 程序集的本地化
- 非标（硬编码）字符串的本地化
- IDA 插件
- Unicode 支持
- 自动翻译、包括模糊翻译
- 机器翻译
- 翻译验证检查
- 对话框、窗体和菜单的所见即所得可视化编辑
- 导出和导入 CSV、TMX 和 TXT 文件
- 翻译记忆编辑器
- XML 格式的方案文件
下面是软件界面
要汉化编辑一个程序的资源首先要导入这个程序，点击【文件】【新建】【新建本地化方案】
在打开的窗口中点击【添加文件】浏览选择要打开的程序
弹出【文件属性】窗口中【目标构建操作】选项选择【创建本地话文件】
注：如果要编辑非编资源切换到【非标字串】选项勾选【提取非标字串】
其他可以保持默认点击【确定】后如果不继续添加需要编辑的程序就在弹出窗口继续点击【下一步】，然后来到语言添加界面双击简体中文添加到下方列表中。

【下一步】继续弹出信息窗口根据提示自行填写一下，也可不填直接点击【完成】.
等待程序载入完毕可以发现程序中所有能识别的资源的在左侧窗口列出来了，点击找到相关项目列表后直接在右侧窗口进行编辑即可。

编辑完毕后点选相关项目后右键点选【“切换”只读】
等待全部编辑完毕后点击【翻译】菜单栏点击【构建全部】即可在程序原目录生成名字后缀为【_CHS.exe】的程序，这个就是编辑后生成的文件。

（注：可编辑下载，若有不当之处，请指正，谢谢!）。