外文翻译规范要求及模版格式
毕业论文外文翻译格式【范本模板】
因为学校对毕业论文中的外文翻译并无规定，为统一起见,特做以下要求：1、每篇字数为1500字左右，共两篇；2、每篇由两部分组成:译文+原文.3 附件中是一篇范本，具体字号、字体已标注。
外文翻译（包含原文)(宋体四号加粗）外文翻译一（宋体四号加粗）作者：(宋体小四号加粗）Kim Mee Hyun Director, Policy Research & Development Team，Korean Film Council（小四号）出处：(宋体小四号加粗)Korean Cinema from Origins to Renaissance(P358～P340) 韩国电影的发展及前景（标题：宋体四号加粗）1996～现在数量上的增长(正文:宋体小四）在过去的十年间，韩国电影经历了难以置信的增长。
上个世纪60年代，韩国电影迅速崛起，然而很快便陷入停滞状态,直到90年代以后，韩国电影又重新进入繁盛时期。
在这个时期，韩国电影在数量上并没有大幅的增长，但多部电影的观影人数达到了上千万人次。
1996年，韩国本土电影的市场占有量只有23.1%。
但是到了1998年，市场占有量增长到35。
8%，到2001年更是达到了50%。
虽然从1996年开始，韩国电影一直处在不断上升的过程中，但是直到1999年姜帝圭导演的《生死谍变》的成功才诞生了韩国电影的又一个高峰。
虽然《生死谍变》创造了韩国电影史上的最高电影票房纪录，但是1999年以后最高票房纪录几乎每年都会被刷新。
当人们都在津津乐道所谓的“韩国大片”时，2000年朴赞郁导演的《共同警备区JSA》和2001年郭暻泽导演的《朋友》均成功刷新了韩国电影最高票房纪录.2003年康佑硕导演的《实尾岛》和2004年姜帝圭导演的又一部力作《太极旗飘扬》开创了观影人数上千万人次的时代。
姜帝圭和康佑硕导演在韩国电影票房史上扮演了十分重要的角色。
从1993年的《特警冤家》到2003年的《实尾岛》，康佑硕导演了多部成功的电影。
毕业论文 外文翻译格式
毕业论文外文翻译格式毕业论文外文翻译格式在撰写毕业论文时，外文翻译是一个重要的环节。
无论是引用外文文献还是翻译相关内容，都需要遵循一定的格式和规范。
本文将介绍一些常见的外文翻译格式，并探讨其重要性和应用。
首先，对于引用外文文献的格式，最常见的是使用APA（American Psychological Association）格式。
这种格式要求在引用外文文献时，先列出作者的姓氏和名字的首字母，然后是出版年份、文章标题、期刊名称、卷号和页码。
例如：Smith, J. D. (2010). The impact of climate change on biodiversity. Environmental Science, 15(2), 145-156.在翻译外文文献时，需要注意保持原文的准确性和完整性。
尽量避免意译或添加自己的解释，以免歪曲原文的意思。
同时，还需要在翻译后的文献后面加上“译者”和“翻译日期”的信息，以便读者可以追溯翻译的来源和时间。
其次，对于翻译相关内容的格式，可以参考国际标准组织ISO（International Organization for Standardization）的格式。
这种格式要求在翻译相关内容时，先列出原文，然后是翻译后的文本。
例如：原文：The importance of effective communication in the workplace cannot be overstated.翻译：工作场所有效沟通的重要性不容忽视。
在翻译相关内容时，需要注意保持原文的意思和语气。
尽量使用准确的词汇和语法结构，以便读者能够理解和接受翻译后的内容。
同时，还需要在翻译后的文本后面加上“翻译者”和“翻译日期”的信息，以便读者可以追溯翻译的来源和时间。
此外，对于长篇外文文献的翻译，可以考虑将其分成若干章节，并在每个章节前面加上章节标题。
这样可以使读者更容易理解和阅读翻译后的内容。
外文翻译规范要求及模版格式
外文翻译规范要求及模版格式
外文中文翻译规范要求及模板格式可以根据具体需求和要求有所不同，以下是一般常见的外文中文翻译规范要求及模板格式：
1.规范要求：
-符合语法、语言规范和语义准确性；
-译文流畅自然，符合中文表达习惯；
-忠实准确地传达原文信息；
-注意统一使用特定的术语翻译；
-文章结构、段落、标题等要与原文一致；
-保持适当的篇幅，不过度增加或删减内容；
-遵守保密原则。
2.模板格式：
-文章标题（与原文保持一致，可放在正文上方）；
-标题（与原文保持一致）；
-段落（与原文保持一致，首行缩进）；
-字体（常用宋体或黑体，一般字号12或14）；
-行间距（一般1.5倍，可根据需要调整）；
-页边距（上下左右均为2.5厘米）；
-段落间距（一般1.5倍，可根据需要调整）；
以上是一般常见的外文中文翻译规范要求及模板格式，具体要求和格式可以根据具体的翻译项目和要求进行调整。
在翻译过程中，保持准确、流畅、专业是非常重要的。
外文翻译与文献综述模板格式以及要求说明
外文翻译与文献综述模板格式以及要求说明
外文中文翻译格式：
标题：将外文标题翻译成中文，可以在括号内标明外文标题
摘要：将外文摘要翻译成中文，包括问题陈述、研究目的、方法、结果和结论等内容。
关键词：将外文关键词翻译成中文。
引言：对外文论文引言进行翻译，概述问题的背景、重要性和研究现状。
方法：对外文论文方法部分进行翻译，包括研究设计、数据采集和分析方法等。
结果：对外文论文结果部分进行翻译，介绍研究结果和统计分析等内容。
讨论：对外文论文讨论部分进行翻译，对研究结果进行解释和评价。
结论：对外文论文结论部分进行翻译，总结研究的主要发现和意义。
附录：如果外文论文有附录部分，需要进行翻译并按照指定的格式进行排列。
文献综述模板格式：
标题：文献综述标题
引言：对文献综述的背景、目的和方法进行说明。
综述内容：按照时间、主题或方法等进行分类，对相关文献进行综述，可以分段进行描述。
讨论：对综述内容进行解释和评价，概括主要研究成果和趋势。
结论：总结文献综述，概括主要发现和意义。
要求说明：
1.外文中文翻译要准确无误，语句通顺流畅，做到质量高、符合学术
规范。
2.文献综述要选择与所研究领域相关的文献进行综述，覆盖面要广，
内容要全面、准确并有独立思考。
4.文献综述要注重整体结构和逻辑连贯性，内容要有层次感，段落间
要过渡自然。
5.外文中文翻译和文献综述要进行查重，确保原文与译文的一致性，
并避免抄袭和剽窃行为。
专业中英文翻译规范
翻译规范——Format（2011年修订版）请仔细阅读以下规定。
本篇大部分规定为格式方面的规定，而部分翻译项目则可能对其格式另有特殊规定。
1. SPACE（空格）除非有特别指示，请在每个翻译项目的中文文字（双字节字符）和英文字或数字（均为单字节）之间留一个单字节空格。
Example 1:今天是2002 年5 月26 日正确。
今天是2002 年5 月26 日错误，数字前没有留出一个单字节空格。
今天是2002 年5 月26 日错误，2 个中文字间无需留出一个空格。
欲知以上各行间有何区别，可到Word > 工具> 选项> 视图> “格式标记”下选择“全部”或者“隐藏文字”。
Example 2:熟练操作WINDOWS 98 中文环境。
在“作”和“W”，“S”和“9”，及“8”和“中”之间都需要留出一个空格。
英文字或数字位于句首或句末的，则无需留空。
Example 1:2002 年5 月26 日是个重要的日子。
正确。
2002 年5 月26 日是个重要的日子错误，句首无须留出一个空格。
Example 2:他的英文名叫做John。
正确。
他的英文名叫做John 。
地址: 福州左海帝景3座1105室网址: 错误，句末无须留出一个空格。
2. PUNCTUATION（标点符号）usage1) 中文须使用双字节标点符号，如，。
、“”！；：; 英文则须使用单字节标点符号, . , “” ! ; :。
双字节标点符号和单字节标点符号的区示：输入状态不同，即双字节标点符号须在中文输入状态下输入，而单字节标点符号须在英文状态下输入；For example:“计算机世界”杂志要用双字节引号，“Computer World” 应使用单字节英文引号。
2) 英文中并列的单字节逗号“,”，中文翻译要改成双字节顿号“、” 等。
3) 书名、协议名称、法律合同规章名称译成英文时应该采用斜体形式，中文时则应在其名称前后加上书名号《》。
毕业设计(论文)外文资料和译文格式要求(模板)
成都东软学院外文资料和译文格式要求一、译文必须采用计算机输入、打印，幅面A4。
外文资料原文（复印或打印）在前，译文在后，于左侧装订。
二、具体要求1、至少翻译一篇内容与所选课题相关的外文文献。
2、译文汉字字数不少于4000字。
3、正文格式要求：宋体五号字。
译文格式参见《译文格式要求》，宋体五号字，单倍行距。
纸张纸张为A4纸，页边距上2.54cm、下2.54cm、左3.17cm、右3.17cm。
装订外文资料原文（复印或打印）在前，译文在后封面封面的专业、班级、姓名、学号等信息要全部填写正确。
封面指导教师必须为讲师以上职称，若助教则需要配备一名讲师协助指导。
讲师在前，助教在后。
指导教师姓名后面空一个中文空格，加职称。
页眉页眉说明宋体小五，左端“XX学院毕业设计（论文）”，右端“译文”。
页眉中的学院名称要与封面学院名称一致。
字数本科4000字。
附：外文资料和译文封面、空白页成都东软学院外文资料和译文专业：软件工程移动互联网应用开发班级：2班姓名：罗荣昆学号：12310420216指导教师：2015年 12月 8日Android page layoutUsing XML-Based LayoutsW hile it is technically possible to create and attach widgets to our activity purely through Java code, the way we did in Chapter 4, the more common approach is to use an XML-based layout file. Dynamic instantiation of widgets is reserved for more complicated scenarios, where the widgets are not known at compile-time (e g., populating a column of radio buttons based on data retrieved off the Internet).With that in mind, it’s time to break out the XML and learn how to lay out Android activities that way.What Is an XML-Based Layout?As the name suggests, an XML-based layout is a specification of widgets’ relationships to each other—and to their containers (more on this in Chapter 7)—encoded in XML format. Specifi cally, Android considers XML-based layouts to be resources, and as such layout files are stored in the res/layout directory inside your Android project.Each XML file contains a tree of elements specifying a layout of widgets and their containers that make up one view hierarchy. The attributes of the XML elements are properties, describing how a widget should look or how a container should behave. For example, if a Button element has an attribute value of android:textStyle = "bold", that means that the text appearing on the face of the button should be rendered in a boldface font style.Android’s SDK ships with a tool (aapt) which uses the layouts. This tool should be automatically invoked by your Android tool chain (e.g., Eclipse, Ant’s build.xml). Of particular importance to you as a developer is that aapt generates the R.java source file within your project, allowing you to access layouts and widgets within those layouts directly from your Java code. Why Use XML-Based Layouts?Most everything you do using XML layout files can be achieved through Java code. For example, you could use setTypeface() to have a button render its textin bold, instead of using a property in an XML layout. Since XML layouts are yet another file for you to keep track of, we need good reasons for using such files.Perhaps the biggest reason is to assist in the creation of tools for view definition, such as a GUI builder in an IDE like Eclipse or a dedicated Android GUI designer like DroidDraw1. Such GUI builders could, in principle, generate Java code instead of XML. The challenge is re-reading the UI definition to support edits—that is far simpler if the data is in a structured format like XML than in a programming language. Moreover, keeping generated XML definitions separated from hand-written Java code makes it less likely that somebody’s custom-crafted source will get clobbered by accident when the generated bits get re-generated. XML forms a nice middle ground between something that is easy for tool-writers to use and easy for programmers to work with by hand as needed.Also, XML as a GUI definition format is becoming more commonplace. Microsoft’s XAML2, Adobe’s Flex3, and Mozilla’s XUL4 all take a similar approach to that of Android: put layout details in an XML file and put programming smarts in source files (e.g., JavaScript for XUL). Many less-well-known GUI frameworks, such as ZK5, also use XML for view definition. While “following the herd” is not necessarily the best policy, it does have the advantage of helping to ease the transition into Android from any other XML-centered view description language. OK, So What Does It Look Like?Here is the Button from the previous chapter’s sample application, converted into an XMLlayout file, found in the Layouts/NowRedux sample project. This code sample along with all others in this chapter can be found in the Source Code area of .<?xml version="1.0" encoding="utf-8"?><Button xmlns:android="/apk/res/android"android:id="@+id/button"android:text=""android:layout_width="fill_parent"android:layout_height="fill_parent"/>The class name of the widget—Button—forms the name of the XML element. Since Button is an Android-supplied widget, we can just use the bare class name. If you create your own widgets as subclasses of android.view.View, you would need to provide a full package declara tion as well.The root element needs to declare the Android XML namespace:xmlns:android="/apk/res/android"All other elements will be children of the root and will inherit that namespace declaration.Because we want to reference this button from our Java code, we need to give it an identifier via the android:id attribute. We will cover this concept in greater detail later in this chapter.The remaining attributes are properties of this Button instance:• android:text indicates the initial text to be displayed on the button face (in this case, an empty string)• android:layout_width and android:layout_height tell Android to have the button’swidth and height fill the “parent”, in this case the entire screen—these attributes will be covered in greater detail in Chapter 7.Since this single widget is the only content in our activity, we only need this single element. Complex UIs will require a whole tree of elements, representing the widgets and containers that control their positioning. All the remaining chapters of this book will use the XML layout form whenever practical, so there are dozens of other examples of more complex layouts for you to peruse from Chapter 7 onward.What’s with the @ Signs?Many widgets and containers only need to appear in the XML layout file and do not need to be referenced in your Java code. For example, a static label (TextView) frequently only needs to be in the layout file to indicate where it should appear. These sorts of elements in the XML file do not need to have the android:id attribute to give them a name.Anything you do want to use in your Java source, though, needs an android:id.The convention is to use @+id/... as the id value, where the ... represents your locally unique name for the widget in question. In the XML layout example in the preceding section, @+id/button is the identifier for the Button widget.Android provides a few special android:id values, of the form @android:id/.... We will see some of these in various chapters of this book, such as Chapters 8 and 10.We Attach These to the Java How?Given that you have painstakingly set up the widgets and containers in an XML layout filenamed main.xml stored in res/layout, all you need is one statement in your activity’s onCreate() callback to use that layout:setContentView(yout.main);This is the same setContentView() we used earlier, passing it an instance of a View subclass (in that case, a Button). The Android-built view, constructed from our layout, is accessed from that code-generated R class. All of the layouts are accessible under yout, keyed by the base name of the layout file—main.xml results in yout.main.To access our identified widgets, use findViewById(), passing in the numeric identifier of the widget in question. That numeric identifier was generated by Android in the R class asR.id.something (where something is the specific widget you are seeking). Those widgets are simply subclasses of View, just like the Button instance we created in Chapter 4.The Rest of the StoryIn the original Now demo, the button’s face would show the current time, which would reflect when the button was last pushed (or when the activity was first shown, if the button had not yet been pushed).Most of that logic still works, even in this revised demo (NowRedux). However,rather than instantiating the Button in our activity’s onCreate() callback, we can reference the one from the XML layout:package youts;import android.app.Activity;import android.os.Bundle;import android.view.View;import android.widget.Button; import java.util.Date;public class NowRedux extends Activity implements View.OnClickListener { Button btn;@Overridepublic void onCreate(Bundle icicle) { super.onCreate(icicle);setContentView(yout.main);btn=(Button)findViewById(R.id.button);btn.setOnClickListener(this);upd ateTime();}public void onClick(View view) { updateTime();}private void updateTime() {btn.setText(new Date().toString()); }}The first difference is that rather than setting the content view to be a view we created in Java code, we set it to reference the XML layout (setContentView(yout.main)). The R.java source file will be updated when we rebuild this project to include a reference to our layout file (stored as main.xml in our project’s res/l ayout directory).The other difference is that we need to get our hands on our Button instance, for which we use the findViewById() call. Since we identified our button as @+id/button, we can reference the button’s identifier as R.id.button. Now, with the Button instance in hand, we can set the callback and set the label as needed.As you can see in Figure 5-1, the results look the same as with the originalNow demo.Figure 5-1. The NowRedux sample activity Employing Basic WidgetsE very GUI toolkit has some basic widgets: fields, labels, buttons, etc. Android’s toolkit is no different in scope, and the basic widgets will provide a good introduction as to how widgets work in Android activities.Assigning LabelsThe simplest widget is the label, referred to in Android as a TextView. Like in most GUI toolkits, labels are bits of text not editable directly by users. Typically, they are used to identify adjacent widgets (e.g., a “Name:” label before a field where one fills in a name).In Java, you can create a label by creating a TextView instance. More commonly, though, you will create labels in XML layout files by adding a TextView element to the layout, with an android:text property to set the value of the label itself. If you need to swap labels based on certain criteria, such as internationalization, you may wish to use a resource reference in the XML instead, as will be described in Chapter 9. TextView has numerous other properties of relevance for labels, such as:• android:typeface to set the typeface to use for the label (e.g., monospace) • android:textStyle to indicate that the typeface should be made bold (bold), italic (italic),or bold and italic (bold_italic)• android:textColor to set the color of the label’s text, in RGB hex format (e.g., #FF0000 for red)For example, in the Basic/Label project, you will find the following layout file:<?xml version="1.0" encoding="utf-8"?><TextView xmlns:android=/apk/res/androidandroid:layout_width="fill_parent"android:layout_height="wrap_content"android:text="You were expecting something profound?" />As you can see in Figure 6-1, just that layout alone, with the stub Java source provided by Android’s p roject builder (e.g., activityCreator), gives you the application.Figure 6-1. The LabelDemo sample applicationButton, Button, Who’s Got the Button?We’ve already seen the use of the Button widget in Chapters 4 and 5. As it turns out, Button is a subclass of TextView, so everything discussed in the preceding section in terms of formatting the face of the button still holds. Fleeting ImagesAndroid has two widgets to help you embed images in your activities: ImageView and ImageButton. As the names suggest, they are image-based analogues to TextView and Button, respectively.Each widget takes an android:src attribute (in an XML layout) to specify what picture to use. These usually reference a drawable resource, described in greater detail in the chapter on resources. You can also set the image content based on a Uri from a content provider via setImageURI().ImageButton, a subclass of ImageView, mixes in the standard Button behaviors, for responding to clicks and whatnot.For example, take a peek at the main.xml layout from the Basic/ImageView sample project which is found along with all other code samples at : <?xml version="1.0" encoding="utf-8"?><ImageView xmlns:android=/apk/res/androidandroid:id="@+id/icon"android:layout_width="fill_parent"android:layout_height="fill_parent"android:adjustViewBounds="true"android:src="@drawable/molecule" />The result, just using the code-generated activity, is shown in Figure 6-2.Figure 6-2. The ImageViewDemo sample applicationFields of Green. Or Other Colors.Along with buttons and labels, fields are the third “anchor” of most GUI toolkits. In Android, they are implemented via the EditText widget, which is a subclass of the TextView used for labels.Along with the standard TextView properties (e.g., android:textStyle), EditText has many others that will be useful for you in constructing fields, including:• android:autoText, to control if the fie ld should provide automatic spelling assistance• android:capitalize, to control if the field should automatically capitalize the first letter of entered text (e.g., first name, city) • android:digits, to configure the field to accept only certain digi ts • android:singleLine, to control if the field is for single-line input or multiple-line input (e.g., does <Enter> move you to the next widget or add a newline?)Beyond those, you can configure fields to use specialized input methods, such asandroid:numeric for numeric-only input, android:password for shrouded password input,and android:phoneNumber for entering in phone numbers. If you want to create your own input method scheme (e.g., postal codes, Social Security numbers), you need to create your own implementation of the InputMethod interface, then configure the field to use it via android: inputMethod.For example, from the Basic/Field project, here is an XML layout file showing an EditText:<?xml version="1.0" encoding="utf-8"?><EditTextxmlns:android=/apk/res/androidandroid:id="@+id/field"android:layout_width="fill_parent"android:layout_height="fill_parent"android:singleLine="false" />Note that android:singleLine is false, so users will be able to enter in several lines of text. For this project, the FieldDemo.java file populates the input field with some prose:package monsware.android.basic;import android.app.Activity;import android.os.Bundle;import android.widget.EditText;public class FieldDemo extends Activity { @Overridepublic void onCreate(Bundle icicle) { super.onCreate(icicle);setContentView(yout.main);EditText fld=(EditText)findViewById(R.id.field);fld.setText("Licensed under the Apache License, Version 2.0 " + "(the \"License\"); you may not use this file " + "except in compliance with the License. You may " + "obtain a copy of the License at " +"/licenses/LICENSE-2.0");}}The result, once built and installed into the emulator, is shown in Figure 6-3.Figure 6-3. The FieldDemo sample applicationNote Android’s emulator only allows one application in the launcher per unique Java package. Since all the demos in this chapter share the monsware.android.basic package, you will only see one of these demos in your emulator’s launcher at any one time.Another flavor of field is one that offers auto-completion, to help users supply a value without typing in the whole text. That is provided in Android as the AutoCompleteTextView widget and is discussed in Chapter 8.Just Another Box to CheckThe classic checkbox has two states: checked and unchecked. Clicking the checkbox toggles between those states to indicate a choice (e.g., “Ad d rush delivery to my order”). In Android, there is a CheckBox widget to meet this need. It has TextView as an ancestor, so you can use TextView properties likeandroid:textColor to format the widget. Within Java, you can invoke: • isChecked() to determi ne if the checkbox has been checked• setChecked() to force the checkbox into a checked or unchecked state • toggle() to toggle the checkbox as if the user checked itAlso, you can register a listener object (in this case, an instance of OnCheckedChangeListener) to be notified when the state of the checkbox changes.For example, from the Basic/CheckBox project, here is a simple checkbox layout:<?xml version="1.0" encoding="utf-8"?><CheckBox xmlns:android="/apk/res/android"android:id="@+id/check"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="This checkbox is: unchecked" />The corresponding CheckBoxDemo.java retrieves and configures the behavior of the checkbox:public class CheckBoxDemo extends Activityimplements CompoundButton.OnCheckedChangeListener { CheckBox cb;@Overridepublic void onCreate(Bundle icicle) { super.onCreate(icicle);setContentView(yout.main);cb=(CheckBox)findViewById(R.id.check);cb.setOnCheckedChangeListener(this);}public void onCheckedChanged(CompoundButton buttonView,boolean isChecked) {if (isChecked) {cb.setText("This checkbox is: checked");}else {cb.setText("This checkbox is: unchecked");}}}Note that the activity serves as its own listener for checkbox state changes since it imple ments the OnCheckedChangeListener interface (via cb.setOnCheckedChangeListener(this)). The callback for the listener is onCheckedChanged(), which receives the checkbox whose state has changed and what the new state is. In this case, we update the text of the checkbox to reflect what the actual box contains.The result? Clicking the checkbox immediately updates its text, as you can see in Figures 6-4 and 6-5.Figure 6-4. The CheckBoxDemo sample application, with the checkbox uncheckedFigure 6-5. The same application, now with the checkbox checkedTurn the Radio UpAs with other implementations of radio buttons in other toolkits, Android’s radio buttons are two-state, like checkboxes, but can be grouped such that only one radio button in the group can be checked at any time.Like CheckBox, RadioButton inherits from CompoundButton, which in turn inherits fromTextView. Hence, all the standard TextView properties for font face, style, color, etc., are available for controlling the look of radio buttons. Similarly, you can call isChecked() on a RadioButton to see if it is selected, toggle() to select it, and so on, like you can with a CheckBox.Most times, you will want to put your RadioButton widgets inside of aRadioGroup. The RadioGroup indicates a set of radio buttons whose state is tied, meaning only one button out of the group can be selected at any time. If you assign an android:id to your RadioGroup in your XML layout, you can access the group from your Java code and invoke:• check() to check a specific radio button via its ID (e.g., group.check(R.id.radio1))• clearCheck() to clear all radio buttons, so none in the group are checked• getCheckedRadioButtonId() to get the ID of the currently-checked radio button (or -1 if none are checked)For example, from the Basic/RadioButton sample application, here is an XML layout showing a RadioGroup wrapping a set of RadioButton widgets: <?xml version="1.0" encoding="utf-8"?> <RadioGroupxmlns:android=/apk/res/androidandroid:orientation="vertical"android:layout_width="fill_parent"android:layout_height="fill_parent" ><RadioButton android:id="@+id/radio1"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="Rock" /><RadioButton android:id="@+id/radio2"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="Scissors" /><RadioButton android:id="@+id/radio3"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="Paper" /></RadioGroup>Figure 6-6 shows the result using the stock Android-generated Java forthe project and this layout.Figure 6-6. The RadioButtonDemo sample application Note that the radio button group is initially set to be completely unchecked at the outset. To pre-set one of the radio buttons to be checked, use either setChecked() on the RadioButton or check() on the RadioGroup from within your onCreate() callback in your activity.It’s Quite a ViewAll widgets, including the ones previously shown, extend View, and as such give all widgets an array of useful properties and methods beyond those already described.Useful PropertiesSome of the properties on View most likely to be used include:• Controls the focus sequence:• android:nextFocusDown• android:nextFocusLeft• android:nextFocusRight• android:nextFocusUp• android:visibility, which controls wheth er the widget is initially visible• android:background, which typically provides an RGB color value (e.g., #00FF00 for green) to serve as the background for the widgetUseful MethodsYou can toggle whether or not a widget is enabled via setEnabled() and see if it is enabled via isEnabled(). One common use pattern for this is to disable some widgets based on a CheckBox or RadioButton selection.You can give a widget focus via requestFocus() and see if it is focused via isFocused(). You might use this in concert with disabling widgets as previously mentioned, to ensure the proper widget has the focus once your disabling operation is complete.To help navigate the tree of widgets and containers that make up an activity’s overall view, you can use:• get Parent() to find the parent widget or container• findViewById() to find a child widget with a certain ID• getRootView() to get the root of the tree (e.g., what you provided to the activity via setContentView())Android 页面布局使用XML进行布局虽然纯粹通过Java代码在activity上创建和添加部件，在技术上是可行的，我们在第4章中做的一样，更常见的方法是使用一种基于XML的布局文件。
毕业论文外文资料翻译【范本模板】
毕业论文外文资料翻译题目(宋体三号，居中）学院（全称，宋体三号，居中)专业(全称，宋体三号，居中）班级（宋体三号,居中）学生（宋体三号，居中）学号（宋体三号,居中)指导教师(宋体三号，居中)二〇一〇年月日(宋体三号，居中，时间与开题时间一致）（英文原文装订在前)Journal of American Chemical Society, 2006, 128(7）: 2421-2425. (文献翻译必须在中文译文第一页标明文献出处:即文章是何期刊上发表的,X年X卷X 期,格式如上例所示,四号，右对齐，杂志名加粗。
)［点击输入译文题目—标题1,黑体小二][点击输入作者，宋体小四］[点击输入作者单位，宋体五号］摘要［点击输入，宋体五号]关键词［点击输入,宋体五号]1［点击输入一级标题-标题2，黑体四号］［点击输入正文，宋体小四号，1。
25倍行距］1。
1［点击输入二级标题-标题3，黑体小四］［点击输入正文,宋体小四，1。
25倍行距]1.1。
1[点击输入三级标题-标题4，黑体小四］［点击输入正文,宋体小四，1。
25倍行距］说明：1.外文文章必须是正规期刊发表的。
2.翻译后的中文文章必须达到2000字以上，并且是一篇完整文章。
3.必须要有外文翻译的封面,使用学校统一的封面；封面上的翻译题目要写翻译过来的中文题目；封面上时间与开题时间一致。
4.外文原文在前，中文翻译在后；5.中文翻译中要包含题目、摘要、关键词、前言、全文以及参考文献,翻译要条理清晰，中文翻译要与英文一一对应.6.翻译中的中文文章字体为小四，所有字母、数字均为英文格式下的，中文为宋体,标准字符间距。
7.原文中的图片和表格可以直接剪切、粘贴，但是表头与图示必须翻译成中文。
8.图表必须居中，文章段落应两端对齐、首行缩进2个汉字字符、1.25倍行距。
例如:图1. 蛋白质样品的PCA图谱与8-卟啉识别排列分析(a)或16—卟啉识别排列分析（b).为了得到 b的数据矩阵，样品用16—卟啉识别排列分析来检测，而a 是通过捕获首八卟啉接收器数据矩阵从b 中萃取的.。
外文翻译与文献综述模板格式以及要求说明
杭州电子科技大学信息工程学院毕业论文外文文献翻译要求根据《普通高等学校本科毕业设计（论文）指导》的内容，特对外文文献翻译提出以下要求：一、翻译的外文文献可以是一篇，也可以是两篇，但总字符要求不少于1.5万（或翻译成中文后至少在3000字以上）。
二、翻译的外文文献应主要选自学术期刊、学术会议的文章、有关著作及其他相关材料，应与毕业论文（设计）主题相关，并作为外文参考文献列入毕业论文（设计）的参考文献。
并在每篇中文译文首页用“脚注”形式注明原文作者及出处，中文译文后应附外文原文。
三、中文译文的基本撰写格式为：1.题目:采用小三号、黑体字、居中打印；2.正文:采用小四号、宋体字，行间距一般为固定值20磅，标准字符间距。
页边距为左3cm，右2.5cm，上下各2.5cm，页面统一采用A4纸。
四、封面格式由学校统一制作（注：封面上的“翻译题目”指中文译文的题目），并按“封面、译文一、外文原文一、译文二、外文原文二、考核表”的顺序统一装订。
五、忌自行更改表格样式。
毕业论文外文文献翻译毕业设计（论文）题目Xxx翻译（1）题目指翻译后的中文译文的题目翻译（2）题目指翻译后的中文译文的题目系会计系以本模板为准）专业XXXXXX（以本模板为准）姓名XXXXXX（以本模板为准）班级XXXXXX（以本模板为准）学号XXXXXX（以本模板为准）指导教师XXXXXX（以本模板为准）正文指导教师对外文翻译的评语：指导教师（签名）年月日建议成绩（百分制）评阅小组或评阅人对外文翻译的评语：评阅小组负责人或评阅人（签名）年月日建议成绩（百分制）杭州电子科技大学信息工程学院本科毕业论文文献综述的写作要求为了促使学生熟悉更多的专业文献资料，进一步强化学生搜集文献资料的能力，提高对文献资料的归纳、分析、综合运用能力及独立开展科研活动的能力，现对本科学生的毕业设计（论文）提出文献综述的写作要求，具体要求如下：一、文献综述的概念文献综述是针对某一研究领域或专题搜集大量文献资料的基础上，就国内外在该领域或专题的主要研究成果、最新进展、研究动态、前沿问题等进行综合分析而写成的、能比较全面地反映相关领域或专题历史背景、前人工作、争论焦点、研究现状和发展前景等内容的综述性文章。
外文文献原稿和译文格式
四、外文文献原稿和译文打印格式
外文文献原稿和译文包括题目、原稿、译文三个部分。
●题目为“外文文献原稿和译文”：之上之下各留一空行，宋体，三号字，居中，加粗
原稿整体格式要尽量保持与原文格式相同，如原稿格式不明确可采用如下格式：
“原稿”：之下留一空行，宋体，小三号字，居中，加粗，“原稿”二字中间空两格；原稿内容：章节题目——新罗马“Times New Roman”字体，四号字，加粗，左对齐；正文——新罗马“Times New Roman”字体，小四号字，段落设置为：固定值，22磅，段前、段后均为0磅。
“译文”：本部分另起一页。
之上之下各留一空行。
宋体，小三号字，居中，加粗。
“译文”二字中间空两格。
译文内容：章节题目——章节题目：宋体，四号字，加粗，左对齐；正文——宋体，小四号字。
段落设置为：固定值，22磅，段前、段后均为0磅。
●页面设置为：上3.5cm，下2.6cm，左2.7cm，右2.7cm，页眉2.4cm，页脚2cm。
●页眉：“北京化工大学北方学院毕业设计（论文）——外文文献原稿和译文”，宋体，小五号字，居中。
●页脚：插入页码，居中。
页码格式为“1，2，3…”。
外文参考文献及翻译稿的要求与格式
百度文库- 让每个人平等地提升自我！外文参考文献及翻译稿的要求及格式一、外文参考文献的要求1、外文原稿应与本研究项目接近或相关联；2、外文原稿可选择相关文章或节选章节，正文字数不少于1500字。
3、格式：外文文献左上角标注“外文参考资料”字样，小四宋体。
1.5倍行距。
标题：三号，Times New Roman字体加粗，居中，行距1.5倍。
段前段后空一行。
作者（居中）及正文：小四号，Times New Roman字体，首行空2字符。
4、A4纸统一打印。
二、中文翻译稿1、中文翻译稿要与外文文献匹配，翻译要正确；2、中文翻译稿另起一页；3、格式：左上角标“中文译文”，小四宋体。
标题：宋体三号加粗居中，行距1.5倍。
段前、段后空一行。
作者（居中）及正文：小四号宋体，数字等Times New Roman字体，1.5倍行距，首行空2字符。
正文字数1500左右。
4、A4纸统一打印。
格式范例如后所示。
百度文库 - 让每个人平等地提升自我！外文参考文献Implementation of internal controls of small andmedium-sized pow erStephen Ryan The enterprise internal control carries out the strength to refer to the enterprise internal control system execution ability and dynamics, it is the one whole set behavior and the technical system, is unique competitive advantage which the enterprise has; Is a series of …………………………标题：三号，Times New Roman字体加粗，居中，行距1.5倍。
外文翻译格式
外文翻译格式
外语翻译通常需要遵循一定的格式，以确保翻译内容的准确性和易读性。
以下是一个700字外文翻译的通用格式示例：
1. 标题：翻译的内容的标题，通常与原文标题保持一致，居中显示。
2. 原文：原文内容，可将原文段落编号，并保留原文格式，如段落缩进或列表。
3. 译文：相关段落的翻译内容，与原文一一对应，并保持相同的段落编号和格式。
4. 术语翻译：将翻译中使用的特定术语或固定表达进行解释和翻译，避免出现歧义。
5. 校对与审校：对翻译内容进行校对和审校，确保翻译准确无误。
6. 结论：对整个翻译内容进行总结和评价，提出自己的观点和见解。
7. 参考文献：如有需要，列出翻译过程中所参考的文献或资料。
8. 附录：如有需要，可在翻译后添加附录，补充相关资料或说明。
注意事项：
- 翻译应遵循专业的术语和语法规范，尽量保持翻译内容的准确性。
- 可根据需要调整段落的分配和序号，以符合原文和翻译内容的逻辑结构。
- 保持翻译格式的统一和美观，使用合适的字体和字号，并注意标点符号的使用。
- 翻译结束后，应进行校对和审校，以确保翻译质量的准确性和流畅性。
总之，一个700字外文翻译的格式应该清晰明了，结构合理，准确无误，并能为读者提供一个清晰且易于理解的翻译内容。
外文翻译撰写规范
第一部分：格式篇
1.外文翻译封面中从“院系”——“指导老师”旁边的下划线请保持长度一致。
2.封面中“原文出处”信息应该完整，同参考文献中的外文文献格式。
3.先中文后英文，中文页码为阿拉伯数字，英文页码为罗马数字。
4.中英文上方第一行都是文章或者书的名称，第二行是出处。
5.字间距为标准，行距为固定值，设置值为23。
如标题与标题、标题与段落之
间间距明显较大时，请选定标题并选择“段落”检查间距中“段前”、“段后”
是否是0行。
6.中文文章段落中出现除序号外的阿拉伯数字或英文应用Times New Roman字
体。
第二部分：内容篇
1．必须是英文文献翻译成中文，不能中文翻译成英文。
2. 英文文献必须是外国人写的，不能只是中国人发表的外文论文。
3．外文文献只要和所写课题相关即可，不用完全一致。
如课题为审计风险，如果找不到审计风险的外文，也可以找审计相关的外文即可。
4．关键词前后翻译必须一致，英文缩写在中文翻译中第一次出现时必须翻译出全称。
5．不能仅仅依靠翻译软件，翻译的中文应检查是否语句通顺，是否有词不达意的情况。
毕业论文的外文翻译要求
毕业论文的外文翻译要求毕业论文是学生完成学业的重要标志，而其中的外文翻译部分更是为了提供更全面的学术支持和国际交流。
为了确保翻译的准确性和专业性，我们有一些明确的要求和规定。
一、译稿准确性要求1.1 语义准确：译稿应准确地传达原文的含义，翻译词语和句子应与原文相对应，确保不出现歧义或误解。
1.2 文法准确：译稿应符合外语语法规范，句子结构要清晰连贯，语法错误应予避免。
1.3 词汇准确：译稿应使用准确的词汇，能够准确表达原文中的专业术语和概念。
1.4 表达准确：译稿应能充分表达原文作者的意图和观点，不改变原意，不添加任何无关信息。
二、格式要求2.1 页面设置：译稿与正文部分应保持一致，包括页边距、字体、字号和行间距等方面。
2.2 段落格式：译稿应采用适当的段落划分，确保内容结构清晰，段落之间应有明显的过渡关系。
2.3 标点符号：译稿中的标点符号应准确无误，与原文保持一致。
2.4 图表翻译：如原文中包含图表、图片等内容，应准确翻译并清晰插入，保持与原文的对应关系。
三、语言风格要求3.1 学术性语言：译稿应以学术性的语言进行表达，避免使用口语或俚语词汇。
3.2 表达简明：译稿应尽量使用简明扼要的语言，避免冗长和啰嗦的表达。
3.3 文体恰当：译稿应根据原文的文体特点，保持与之一致的语言风格，如正式、客观等。
3.4 遵循学科要求：根据不同学科的要求，译稿应遵循相应的学科规范和术语。
四、参考文献要求4.1 引用准确：如译稿中涉及引用原文中的内容，应准确标注出处，遵循学术引用规范。
4.2 参考文献著录：如译稿中有参考文献部分，应按照规范的著录格式进行排版，确保引用的准确性。
4.3 翻译标注：如译稿中对参考文献进行翻译或添加注释，应将其清晰标注，以区分原文与译文。
总结：毕业论文的外文翻译要求是多方面的，从译稿准确性、格式要求、语言风格要求到参考文献要求，都需要学生严格遵循。
合理的格式和清晰的语言表达是展示学术水平和专业素养的重要方面，而译稿的准确性更是毕业论文的基石。
外文翻译格式及规范
嘉兴学院毕业论文（设计）外文翻译撰写格式规范一、外文翻译形式要求1、要求本科生毕业论文（设计）外文翻译部分的外文字符不少于1.5万字, 每篇外文文献翻译的中文字数要求达到2000字以上，一般以2000~3000字左右为宜。
2、翻译的外文文献应主要选自学术期刊、学术会议的文章、有关著作及其他相关材料，应与毕业论文（设计）主题相关，并作为外文参考文献列入毕业论文（设计）的参考文献。
3、外文翻译应包括外文文献原文和译文，译文要符合外文格式规范和翻译习惯。
二、打印格式嘉兴学院毕业论文（设计）外文翻译打印纸张统一用A4复印纸，页面设置：上：2.8；下：2.6；左：3.0；右：2.6；页眉：1.5；页脚：1.75。
段落格式为：1.5倍行距，段前、段后均为0磅。
页脚设置为：插入页码，居中。
具体格式见下页温馨提示：正式提交“嘉兴学院毕业论文（设计）外文翻译”时请删除本文本中说明性的文字部分（红字部分）。
嘉兴学院本科毕业论文（设计）外文翻译题目：（指毕业论文题目）学院名称：服装与艺术设计学院专业班级：楷体小四学生姓名：楷体小四一、外文原文见附件（文件名：12位学号+学生姓名+3外文原文．文件扩展名）。
二、翻译文章翻译文章题目（黑体小三号，1.5倍行距，居中）作者（用原文，不需翻译，Times New Roman五号，加粗，1.5倍行距，居中）工作单位（用原文，不需翻译，Times New Roman五号，1.5倍行距，居中）摘要：由于消费者的需求和汽车市场竞争力的提高，汽车检测标准越来越高。
现在车辆生产必须长于之前的时间并允许更高的价格进行连续转售……。
(内容采用宋体五号，1.5倍行距)关键词：汽车产业纺织品，测试，控制，标准，材料的耐用性1 导言（一级标题，黑体五号，1.5倍行距，顶格）缩进两个字符，文本主体内容采用宋体（五号），1.5倍行距参考文献（一级标题，黑体五号， 1.5倍行距，顶格）略（参考文献不需翻译，可省略）资料来源：AUTEX Research Journal, V ol. 5, No3, September 2008*****译****校（另起一页）三、指导教师评语***同学是否能按时完成外文翻译工作。
外文翻译的格式要求
外文翻译的格式要求
一、封面
1、已填写的内容不要改动
2、外文出处只能填写著作名、教材名、英文论文题目、英语国家官
方网页网址、期刊名、报纸名。
中文网址禁止填写。
二、外文翻译文件排列顺序
首先是封面，然后是译文即中文，其次另起一页英文即原文，最后一页是外文资料翻译评价表（由指导教师填写）。
三、译文部分格式要求
1、题目为宋体四号居中加粗
2、正文内容为宋体小四，行间距为固定值18磅，其他数值为0
四、原文格式要求
字体为Times New Roman ,其他与原文相同。
外文文献翻译--内容格式
外文文献翻译的撰写说明一、外文文献翻译的内容通过外文文献查阅与翻译，进一步提高掌握使用外文的能力，熟悉本专业的主要的外文书刊，了解毕业设计（论文）课题的国内外信息与发展动向。
翻译的外文文献应主要选自学术期刊、学术会议的文章、有关著作及其他相关材料，应与毕业设计（论文）主题相关，并作为外文参考文献列入毕业设计（论文）的参考文献，中文译文后应附外文原文。
（一）标题应真实反映翻译外文的主体内容或原外文标题内容，一般控制在20个汉字以内。
可以用副标题对标题予以补充说明；（二）标题下方正中为外文作者署名；（三）外文翻译成中文的内容；（四）外文著录。
二、字数要求一般要求为2000-3000汉字或不少于15000外文字符。
三、打印格式1、打印用纸：A42、页面设置：上：3.5cm；下:2.5 cm；左：3.0 cm；右2.4 cm；装订线：0.5cm；页眉：2.5 cm；页脚：1.8cm；行间距：固定值22磅3、字体、字号：1 一级标题：黑体、三号；1.1…二级标题：黑体、四号；1.1.1…三级标题：宋体、加粗、小四；标题顶格写，后空一个字位置正文部分：宋体、小四；每段空2字位置页眉“黄石理工学院外文文献翻译”，宋体、5号，居右排列；页码居页面底端靠右排列。
四、参考文献著录参考文献著录按照GB7714-87文参考文献著录规则执行。
书写顺序为：序号·作者·论文名或著作名·杂志或会议名·卷号、期号或会议地点·出版社·页号·年。
摘要、关键词：摘要、关键词顶格写，后用冒号摘要：废水回用可以大大减少……关键词：废水回收利用；反冲洗；上清液中间用“；”分隔，最后没有“。
”外文参考文献转换成中文参考文献：外文参考文献著录格式与中文不同。
1、外文中（康韦尔和麦克2001; Dotremont等，1999;。
LeGouellec等，2004;。
纳赛尔等人2002;。
外文文献翻译格式要求
外文文献翻译格式要求
外文文献中文翻译的格式要求通常包括以下几个方面：
2.翻译稿的标题应与原文保持一致，通常在文献翻译稿的第一页的中间位置，使用加粗、居中排版。
3.每一段落开始时空两行，段落间距可以根据需要适当调整。
4. 翻译稿中的引用部分，应在文中用中括号标注原文引用部分的位置，如 "[Original text]"
5.翻译稿中的图表、表格等内容，需要在相应位置插入，并在上方标明图表或表格编号，并在下方进行说明。
7.在翻译稿的最后，需要标注翻译人员的签名，并附上日期。
总之，翻译稿与原文应尽量保持一致，在排版和格式上遵循一定的要求和规范。
具体格式要求也可以根据翻译机构或期刊的要求进行调整。
外文翻译原文模板
1、外文资料翻译内容要求：外文资料的内容应为本学科研究领域，并与毕业设计（论文）选题相关的技术资料或专业文献，译文字数应不少于3000汉字以上，同时应在译文末注明原文的出处。
不可采用网络中直接有外文和原文的。
2、外文资料翻译格式要求：译文题目采用小二号黑体，居中；译文正文采用宋体小四号，段前、段后距为0行；行距：固定值20磅。
英文原文如果为打印的话用新罗马（Times New Roman）小四号字。
装订时原文在前，译文在后。
文章中有引用的地方在原文中也要体现。
参考文献也要翻译成中文！An Energy-Efficient Cooperative Algorithm for Data Estimation inWireless Sensor NetworksAbstract – In Wireless Sensor Networks (WSN), nodes operate on batteries and network’s lifetime depends on energy consumption of the nodes. Consider the class of sensor networks where all nodes sense a single phenomenon at different locations and send messages to a Fusion Center (FC) in order to estimate the actual information. In classical systems all data processing tasks are done in the FC and there is no processing or compression before transmission. In the proposed algorithm, network is divided into clusters and data processing is done in two parts. The first part is performed in each cluster at the sensor nodes after local data sharing and the second part will be done at the Fusion Center after receiving all messages from clusters. Local data sharing results in more efficient data transmission in terms of number of bits. We also take advantage of having the same copy of data at all nodes of each cluster and suggest a virtual Multiple-Input Multiple-Output (V-MIMO) architecture for data transmission from clusters to the FC. A Virtual-MIMO network is a set of distributed nodes each having one antenna. By sharing their data among themselves, these nodes turn into a classical MIMO system. In the previously proposed cooperative/virtual MIMO architectures there has not been any data processing or compression in the conference phase. We modify the existing VMIMO algorithms to suit the specific class of sensor networks that is of our concern. We use orthogonal Space-Time Block Codes (STBC) for MIMO part and by simulation show that this algorithm saves considerable energy compared to classical systems.I. INTRODUCTIONA typical Wireless Sensor Network consists of a set of small, low-cost and energy-limited sensor nodes which are deployed in a field in order to observe a phenomenon and transmit it to a Fusion Center (FC). These sensors are deployed close to one another and their readings of the environment are highly correlated. Their objective is to report a descriptive behavior of the environment based on all measurements to the Fusion Center. This diversity in measurement lets the system become more reliable and robust against failure. In general, each node is equipped with a sensing device, a processor and a communication module (which can be either a transmitter or transmitter/receiver).Sensor nodes are equipped with batteries and are supposed to work for a long period of time without battery replacement. Thus, they are limited in energy and one of the most important issues in designing sensor networks will be the energy consumption of the sensor nodes. To deal with this problem, we might either reduce the number of bits to be transmitted by source compression or reduce the required power for transmission by applying advanced transmission techniques while satisfying certain performance requirement.A lot of research has been done in order to take advantage of the correlation among sensors’ data for reducing the number of bits to be transmitted. Some are based on distributed source coding[1]while others use decentralized estimation[2-5]. In [1], authors present an efficient algorithm that applies distributed compression based on Slepian – Wolf[14] encoding technique and use an adaptive signal processing algorithm to track correlation among sensors data. In [2-5] the problem of decentralized estimation in sensor networks has been studied under different constraints. In these algorithms, sensors perform a local quantization on their data considering that their observations are correlated with that of other sensors. They produce a binary message and send it to the FC. FC combines these messages based on the quantization rules used at the sensor nodes and estimates the unknown parameter. Optimal local quantization and final fusion rules are investigated in these works. The distribution of data assumed for sensor observation in these papers has Uniform probability distribution function. In our model we consider Gaussian distribution introduced in [17] for sensor measurements which ismore likely to reality.As an alternative approach, some works have been done using energy-efficient communication techniques such as cooperative/virtual Multiple-Input Multiple-Output (MIMO) transmission in sensor networks [6-11]. In these works, as each sensor is equipped with one antenna, nodes are able to form a virtual MIMO system by performing cooperation with others. In [6] the application of MIMO techniques in sensor networks based on Alamouti[15] space-time block codes was introduced. In [8,9] energy-efficiency of MIMO techniques has been explored analytically and in [7] a combination of distributed signal processing algorithm presented and in [1] cooperative MIMO was studied.In this paper, we consider both techniques of compression and cooperative transmission at the same time. We reduce energy consumption in two ways; 1) processing data in part at the transmitting side, which results in removing redundant information thus having fewer bits to be transmitted and 2) reducing required transmission energy by applying diversity and Space-Time coding. Both of these goals will be achieved by our proposed two-phase algorithm. In our model, the objective is to estimate the unknown parameter which is basically the average of all nodes’ measurements. That is, exact measurements of individual nodes are not important and it is not necessary to spend a lot of energy and bandwidth to transmit all measured data with high precision to the FC. We can move some part of data processing to the sensors side. This can be done by local data sharing among sensors. We divide the network into clusters of ‘m’ members. The number of members in the cluster (m) is both the compression factor in data processing and also the diversity order in virtual-MIMO architecture. The remaining of this paper is organized as following: in section II we introduce our system model and basic assumptions. In section III we propose our collaborative algorithm. In section IV we present the mathematical analysis of the proposed algorithm and in section V we give some numerical simulations. Finally section VI concludes the paper.II. SYSTEM MODELA. Network ModelThe network model that we use is similar to the one presented in [2-5].Our network consists of N distributed Sensor Nodes (SN) and a Fusion Center (FC). Sensors are deployed uniformly in the field, close to one another and each taking observations on an unknown parameter (θ). Fusion Center is located far from the nodes. All nodes observe same phenomenon but with different measurements. These nodes together with the Fusion Center are supposed to find the value of the unknown parameter. Nodes send binary messages to Fusion Center. FC will process the received messages and estimate the unknown value.B. Data ModelIn our formulation we use the data model introduced in[17]. We assume that all sensors observe the same phenomenon (θ) which has Gaussian distribution with variance σx 2. They observe different versions of θ and we model this difference as an additive zero mean Gaussian noisewith variance σn 2. Therefore, sensor observations will be described byn i i θx += （1） Where θ ~ N (0, σx 2) and n i ~ N (0, σn 2) for i = 1, 2, … , N .Based on thisassumption the value of θ can be estimated by taking the numerical average of the nodes observations, i.e.∑==N i i x N 11θ（2）C. Reference System ModelOur reference system consists of N conventional Single Input Single Output (SISO) wireless links, each connecting one of the sensor nodes to the FC. For the reference system we do not consider any communication or cooperation among the sensors. Therefore each sensor quantizes its observation by an L-bit scalar quantizer designed for distribution of θ, generates a message of length L and transmits it directly to the FC. Fusion Center receives all messages and performs the processing, which is calculation of the numerical average of these messages.III. COOPERATIVE DATA PROCESSING ALGORITHMSensor readings are analog quantities. Therefore, each sensor has to compress its data into several bits. For data compression we use L -bit scalar quantizer [12,13].In our algorithm, network is divided into clusters, each cluster having a fixed and pre-defined number of members (m). Members of each cluster are supposed to cooperate with one another in two ways:1. Share, Process and Compress their data2. Cooperatively transmit their processed data using virtual MIMO.IV. ANALYSISThe performance metric considered in our analysis is the total distortion due to compression and errors occurred during transmission. The first distortion is due to finite length quantizer, used in each sensor to represent the analog number by L bits. This distortion depends on the design of quantizer.We consider a Gaussian scalar quantizer which is designed over 105 randomly generated samples. The second distortion is due to errors occurred during transmission through the channel. In our system, this distortion is proportional to the probability of bit error. Since the probability of bit error (Pe) is a function of transmission energy per bit (Eb), total distortion will be a function of Eb. In this section we characterize the transmission and total consumed energy of sensors and find the relationship between distortion and probability of bit error.V. SIMULATION AND NUMERICAL RESULTS To give a numerical example, we assume m = 4 members in each cluster. Therefore our Virtual-MIMO scheme will consist of 4 transmit antennas. We assume that network has N = 32 sensors. Sensor observations are Gaussian with σx2= 1 and are added to a Gaussian noise of σn2= 0.1 .Nodes are deployed uniformly in the field and are 2 meters apart from each other and the Fusion Center is located 100 meters away from the center of the field. The values for circuit parameters are quoted from [6] and are listed in Table I. These parameters depend on the hardware design and technological advances. Fig. 1 illustrates the performance (Distortion) of reference system and proposed two-phase V-MIMO scheme versus transmission energy consumption in logarithmic scale. As shown in the figures, depending on how much precision is needed in the system, we can save energy by applying the proposed algorithm.TABLE IFig. 2 illustrates the Distortion versus total energy consumption of sensor nodes. That is, in this figure we consider both the transmission and circuit energy consumption. The parameters that lead us to these results may be designed to give better performance than presented here. However, from these figures we can conclude that the proposed algorithm outperforms the reference system when we want to have distortion less than 10−3 and it can save energy as high as 10 dB.VI. CONCLUSIONIn this paper we proposed a novel algorithm which takes advantage of cooperation among sensor nodes in two ways: it not only compresses the set of sensor messages at the sensor nodes into one message, appropriate for final estimation but also encodes them into orthogonal space-time symbols which are easy to decode and energy-efficient. This algorithm is able to save energy as high as 10 dB.REFERENCES[1] J.Chou,D.Petrovic and K.Ramchandran “A distributed and adaptive signalprocessing approach to reducing energy consumption in sensornetworks,”Proc. IEEE INFOCOM,March 2003.[2] Z.Q.Luo, “Universal decentralized estimation in a bandwidth constrainedsensor network,” IEEE rmation The ory, vol.51,no.6,June 2005.[3] Z.Q.Luo,“An Isotropic Universal decentralized estimation scheme for abandwidth constrained Ad Hoc sensor network,”IEEEm. vol.23,no. 4,April 2005.[4] Z.Q.Luo and J.-J. Xiao, “Decentralized estimation i n an inhomogeneoussensing environment,” IEEE Trans. Information Theory, vol.51, no.10,October 2005.[5] J.J.Xiao,S.Cui,Z.-Q.Luo and A.J.Goldsmith, “Joint estimation in sensornetworks under energy constraints,” Proc.IEEE First conference on Sensor and Ad Hoc Communications and Networks, (SECON 04),October 2004.[6] S.Cui, A.J.Goldsmith, and A.Bahai,“Energy-efficiency of MIMO andcooperative MIMO techniques in sensor networks,”IEEEm,vol.22, no.6pp.1089–1098,August 2004.[7] S.K.Jayawe era and M.L.Chebolu, “Virtual MIMO and distributed signalprocessing for sensor networks-An integrated approach”,Proc.IEEEInternational Conf. Comm.(ICC 05)May 2005.[8] S.K.Jayaweera,"Energy efficient virtual MIMO-based CooperativeCommunications for Wireless Sensor Networks",2nd International Conf. on Intelligent Sensing and Information Processing (ICISIP 05),January 2005.[9] S.K.Jayaweera,“Energy Analysis of MIMO Techniques in Wireless SensorNetworks”, 38th Annual Conference on Information Sciences and Systems (CISS 04),March 2004.[10] S.K.Jayaweera and M.L.Chebolu,“Virtual MIMO and Distributed SignalProcessing for Sensor Networks - An Integrated Approach”,IEEEInternational Conf.on Communications (ICC 05),May 2005.[11] S.K.Jayaweera,“An Energy-efficient Virtual MIMO CommunicationsArchitecture Based on V-BLAST Processing for Distributed WirelessSensor Networks”,1st IEEE International Conf.on Sensor and Ad-hocCommunications and Networks (SECON 2004), October 2004.[12] J.Max,“Quantizing for minimum distortion,” IRE rmationTheory,vol.IT-6, pp.7 – 12,March 1960.[13] S.P.Lloyd,“Least squares quantization in PCM ,”IEEE rmationTheory,vol.IT-28, pp.129-137,March 1982.[14] D.Slepian and J.K.Wolf “Noiseless encoding of correlated inf ormationsources,” IEEE Trans. on Information Theory,vol.19, pp.471-480,July1973.[15] S.M.Alamouti,“A simple transmit diversity technique for wirelesscommunications,” IEEE m., vol.16,no.8,pp.1451–1458,October 1998.[16] V.Tarokh,H.Jafarkhani,and A.R.Calderbank. “Space-time block codesfrom orthogonal designs,’’IEEE rmationTheory,vol.45,no.5,pp.1456 -1467,July 1999.[17] Y.Oohama,“The Rate-Distortion Function for the Quadratic GaussianCEO Problem,” IEEE Trans. Informatio nTheory,vol.44,pp.1057–1070,May 1998.。
外文翻译及外文原文(参考格式)
外文翻译要求：1、外文资料与毕业设计（论文）选题密切相关，译文准确、质量好。
2、阅读2篇幅以上（10000字符左右）的外文资料，完成2篇不同文章的共2000汉字以上的英译汉翻译3、外文资料可以由指导教师提供，外文资料原则上应是外国作者。
严禁采用专业外语教材文章。
4、排序：“一篇中文译文、一篇外文原文、一篇中文译文、一篇外文原文”。
插图内文字及图名也译成中文。
5、标题与译文格式（字体、字号、行距、页边距等）与论文格式要求相同。
下页附：外文翻译与原文参考格式英文翻译 (黑体、四号、顶格)外文原文出处：(译文前列出外文原文出处、作者、国籍，译文后附上外文原文)《ASHRAE Handbook —Refrigeration 》.CHAPTER3 .SYSTEM Practices for ammonia 3.1 System Selection 3.2 Equipment3.10 Reciprocating Compressors第3章 氨制冷系统的实施3.1 系统选择在选择一个氨制冷系统设计时，须要考虑一些设计决策要素，包括是否采用（1）单级压缩（2）带经济器的压缩（3）多级压缩（4）直接蒸发（5）满液式（6）液体再循环（7）载冷剂。
单级压缩系统基本的单级压缩系统由蒸发器、压缩机、冷凝器、储液器（假如用的话）和制冷剂控制装置（膨胀阀、浮球阀等）。
1997 ASHRAE 手册——“原理篇”中的第一章讨论了压缩制冷循环。
图1.壳管式经济器的布置外文翻译的标题与译文中的字体、字号、行距、页边距等与论文格式相同。
英文原文(黑体、四号、顶格)英文翻译2（黑体，四号，顶格）外文原文出处：（黑体，四号，顶格）P. Fanning. Nonlinear Models of Reinforced and Post-tensioned Concrete Beams. Lecturer, Department of Civil Engineering, University College Dublin. Received 16 Jul 2001.非线形模型钢筋和后张法预应力混凝土梁摘要:商业有限元软件一般包括混凝土在荷载做用下非线性反应的专用数值模型。
毕业设计(论文)外文文献翻译要求
毕业设计（论文）外文文献翻译要求
根据《普通高等学校本科毕业设计（论文）指导》的内容，特对外文文献翻译提出以下要求：
一、翻译的外文文献一般为1～2篇，外文字符要求不少于1.5万（或翻译成中文后至少在3000字以上）。
二、翻译的外文文献应主要选自学术期刊、学术会议的文章、有关著作及其他相关材料，应与毕业论文（设计）主题相关，并作为外文参考文献列入毕业论文（设计）的参考文献。
并在每篇中文译文首页用“脚注”形式注明原文作者及出处，中文译文后应附外文原文。
三、中文译文的基本撰写格式为题目采用小三号黑体字居中打印，正文采用宋体小四号字，行间距一般为固定值20磅，标准字符间距。
页边距为左3cm，右2.5cm，上下各2.5cm，页面统一采用A4纸。
四、封面格式由学校统一制作（注：封面上的“翻译题目”指中文译文的题目，附件1为一篇外文翻译的封面格式，附件二为两篇外文翻译的封面格式），若有两篇外文文献，请按“封面、译文一、外文原文一、译文二、外文原文二”的顺序统一装订。
教务处
20XX年2月27日
杭州电子科技大学
毕业设计（论文）外文文献翻译
毕业设计（论文）题
目
翻译题目
学院
专业
姓名
班级
学号
指导教师
杭州电子科技大学
毕业设计（论文）外文文献翻译
毕业设计（论文）题
目
翻译（1）题目
翻译（2）题目
学院
专业
姓名
班级
学号指导教师。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
(二)外文翻译
每位学生必须阅读2篇以上(10000字符左右)的外文材料，应完成5000汉字以上的英译汉翻译。
加“外文翻译”封面，全文1.5倍行距。
原文可用A4纸复印,每篇原文后附译文(即中文不要直接翻译在原文的同一页)。
模板
外 文 翻 译
毕业设计题目：
原文1
译文1
原文2
译文2：
封面
左边距：3.0cm 右边距：2.5cm 上边距：2.5cm 下边距：2.5cm
(
(原文1)Headaches: A slowdown in traditional newspaper advertising. The proliferation of media choices, especially the Internet, threaten to cannibalize both readership and prestige.
出处：
正文
左边距：3.0cm 右边距：2.5cm
上边距：2.5cm
下边距：2.5cm
段落缩进：2字符
行距：1.5倍
另起一页(译文标题)
(译文1)最头痛的事：传统报纸广告量下降。
随着越来越多的媒体出现在人们面前，
出处：
特别说明：如原文系纸质的，请按A4尺寸复印，字迹清晰，页面正直(不要歪斜)，周边干净，如是PDF格式提供PDF文档，装订时再打印。