毕业设计外文翻译译文格式
毕业论文 外文翻译格式
毕业论文外文翻译格式毕业论文外文翻译格式在撰写毕业论文时，外文翻译是一个重要的环节。
无论是引用外文文献还是翻译相关内容，都需要遵循一定的格式和规范。
本文将介绍一些常见的外文翻译格式，并探讨其重要性和应用。
首先，对于引用外文文献的格式，最常见的是使用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.翻译：工作场所有效沟通的重要性不容忽视。
在翻译相关内容时，需要注意保持原文的意思和语气。
尽量使用准确的词汇和语法结构，以便读者能够理解和接受翻译后的内容。
同时，还需要在翻译后的文本后面加上“翻译者”和“翻译日期”的信息，以便读者可以追溯翻译的来源和时间。
此外，对于长篇外文文献的翻译，可以考虑将其分成若干章节，并在每个章节前面加上章节标题。
这样可以使读者更容易理解和阅读翻译后的内容。
(范例)外文翻译格式
本科毕业设计（论文）外文翻译译文学生姓名：院（系）：经济管理学院专业班级：市场营销0301班指导教师：完成日期：2007年3 月22 日日本的分销渠道——对于进入日本市场的挑战与机会Distribution Channels in JapanChallenges and Opportunities for theJapanese Market Entry作者：Hokey Min起止页码：P22-35出版日期（期刊号）：0960-0035出版单位：MCB Univercity Press外文翻译译文：介绍尽管美国对日本的出口在过去两年已有大幅度的增长，然而美国对日本仍然存在着很大的贸易赤字。
尽管没有出现下降趋势，但越来越多的美国决策者及商务经理已经开始审查日本的贸易活动。
在这些人中，有一个很普遍的想法就是日本市场没有对美国产品开放，相反，美国市场对日本的贸易是开放的。
因此，克林顿政府试图采取强硬措施来反对日本的一系列贸易活动，包括商业习惯和政府政策，还企图通过贸易制裁的威胁来反对日本产品。
然而，这样的措施也会产生适得其反的结果。
它不仅会为美国消费者带来更高的商品价格和更少的商品选择，同时也会增加日本消费者的反美情绪。
最近Ginkota和Kotabe的调查表明：单独的贸易谈判不会提高美国商品进入日本市场的能力。
而对于提高美国公司进入日本市场能力的一个行之有效的方法就是研究日本近几个世纪以来所采用的商业活动。
由于法律障碍或者是日本公司对外封锁商业渠道，日本当地的分销渠道往往对外国公司不利，而这样的商业活动被认为是进入日本市场的主要障碍。
事实上，Yamawaki美国商品成功出口到日本市场在很大程度上取决于美国解决协议合同的能力。
尽管进入日本市场意义重大，然而对西方人而言，日本的经销体系经常会被人误以为是充满神秘感的。
这种误解源于日本复杂的分销惯例特征。
而这种分销惯例沿袭古老的而又严谨的建设体系。
在尝试美国贸易在日本市场成功获利减少不必要的贸易冲突过程中，我们揭露了日本分销中获利的事实，探索出了能成功进入日本市场的战略性武器。
外文翻译指导记录怎么写
外文翻译指导记录怎么写外文翻译指导记录怎么写外文翻译、开题报告要求一套完整的毕业设计(论文)材料由外文翻译、开题报告和毕业设计(论文)正文三部分组成，按照统一的封面和格式编写。
和字体大小将按照学院的规定。
文本格式和书写要求（一）外文翻译通过文献综述和翻译，进一步提高外语运用能力，熟悉本专业几大外文书刊，了解国内外毕业设计(论文)信息和动态。
1、格式：（1）外文（译文前面附被翻译的外文原件复印件）；（2）翻译成中文格式：①标题②署名（作者名）** 著译者：***③翻译正文④外文著录为了反映文稿的科学依据和译者尊重他人研究成果的严肃态度以及向读者提出有关信息的出处，要求译者按著录/题名/出版事项顺序排列注明：期刊——著者，题名，期刊名称，出版年，卷号（期号），起始页码。
书籍——著者，书名、版次（第一版不标注），出版地，出版者，出版年，起始页码。
2、内容要求：（1）阅读每位学生在文献查阅环节中，必须阅读5～10万个印刷符号的外语文献资料（最好阅读与课题或本专业有联系的内容），择其重要的翻译1～2万个印刷符号（约3000汉字）。
（2）翻译①标题应真实地反映出翻译外文的主体内容或原外文标题内容，一般控制在20个汉字以内。
可以用副标题对标题予以补充说明；②标题下方正中为外文作者署名；③外文翻译成中文的内容；④外文著录（二）开题报告1、格式：（1）课题名称；（2）学生、专业、指导教师和教学单位署名；（3）开题报告的正文撰写。
2、内容要求：（1）课题名称要求与毕业设计（论文）正文标题名称一致（一般控制在20个汉字以内，可以用副标题对标题予以补充说明）。
（2）学生、指导教师和教学单位署名：题目下方中间是学生签名，学生签名下方是专业名称，专业名称下方是指导老师签名，指导老师签名下方是教学单位签名(教学单位指学院)。
（3）开题报告的正文撰写要求包括（不少于2500字）：①课题来源②研究目的和意义③研究的内容与途径④国内外研究现状与发展趋势通过提问和分析问题，综合前人文献提出的理论和事实，比较各种学术观点，明确所提问题的历史、现状和发展方向。
3外文翻译模板格式及要求
杭州电子科技大学毕业论文外文文献翻译要求根据《普通高等学校本科毕业设计（论文）指导》的内容，特对外文文献翻译提出以下要求：一、翻译的外文文献可以是一篇，也可以是两篇，但总字符要求不少于1.5万（或翻译成中文后至少在3000字以上）。
二、翻译的外文文献应主要选自学术期刊、学术会议的文章、有关著作及其他相关材料，应与毕业论文（设计）主题相关，并作为外文参考文献列入毕业论文（设计）的参考文献。
并在每篇中文译文首页用“脚注”形式注明原文作者及出处，中文译文后应附外文原文。
脚注的方法：插入----引用---脚注和尾注三、中文译文的基本撰写格式为：1.题目:采用小三号、黑体字、居中打印；2.正文:采用小四号、宋体字，行间距为固定值20磅，标准字符间距。
页边距为左3cm，右2.5cm，上下各2.5cm，页面统一采用A4纸。
英文原文如为word文档，请用罗马字体排版，段前空两格。
从正文开始编写页码，页码居中。
四、封面格式由学校统一制作（注：封面上的“翻译题目”指中文译文的题目），填充内容为加粗小三号楷体_GB2312，并按“封面、译文一、外文原文一、译文二、外文原文二、考核表”的顺序统一装订。
五、忌自行更改表格样式，学号请写完整。
封面和考核表均为一页纸张，勿换行换页。
毕业论文外文文献翻译毕业设计（论文）题目Xxx翻译（1）题目指翻译后的中文译文的题目翻译（2）题目指翻译后的中文译文的题目学院会计学院（以本模板为准）专业会计学（以本模板为准）姓名XXXXXX（以本模板为准）班级XX020811（以本模板为准）学号XX023101（以本模板为准）指导教师XXXXXX（以本模板为准）外文翻译考核表。
毕业论文外文翻译格式
因为学校对毕业论文中的外文翻译并无规定，为统一起见，特做以下要求：1、每篇字数为1500字左右，共两篇；2、每篇由两部分组成：译文 +原文。
3 附件中是一篇范本，具体字号、字体已标注。
外文翻译（包含原文）（宋体四号加粗）外文翻译一（宋体四号加粗）作者：（宋体小四号加粗）Kim Mee Hyun Director, Policy Research & Development Team, Korean Film Council （小四号）出处：（宋体小四号加粗）Korean Cinema from Origins to RenaissanceP358~P34C）韩国电影的发展及前景（标题：宋体四号加粗）1996~现在在过去的十年间，韩国电影经历了难以置信的增长。
上个世纪60年代，韩国电影迅速崛起，然而很快便陷入停滞状态，直到90年代以后，韩国电影又重新进入繁盛时期。
在这个时期，韩国电影在数量上并没有大幅的增长，但多部电影的观影人数达到了上千万人次。
1996年，韩国本土电影的市场占有量只有23.1%。
但是到了1998年，市场占有量增长到35.8%,到2001年更是达到了50% 虽然从1996年开始，韩国电影一直处在不断上升的过程中，但是直到1999年姜帝圭导演的《生死谍变》的成功才诞生了韩国电影的又一个高峰。
虽然《生死谍变》创造了韩国电影史上的最高电影票房纪录，但是1999年以后最高票房纪录几乎每年都会被刷新。
当人们都在津津乐道所谓的“韩国大片”时，2000年朴赞郁导演的《共同警备区JSA〉和2001年郭暻泽导演的《朋友》均成功刷新了韩国电影最高票房纪录。
2003年康佑硕导演的《实尾岛》和2004年姜帝圭导演的又一部力作《太极旗飘扬》开创了观影人数上千万人次的时代。
姜帝圭和康佑硕导演在韩国电影票房史上扮演了十分重要的角色。
从1993年的《特警冤家》到2003年的《实尾岛》，康佑硕导演了多部成功的电影。
毕业设计(论文)外文资料和译文格式要求(模板)
成都东软学院外文资料和译文格式要求一、译文必须采用计算机输入、打印，幅面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的布局文件。
外文翻译标准格式
毕业设计（论文）
译文及原稿译文题目：[单击此处添加译文题目]
原稿题目：[单击此处添加原稿题目]
原稿出处：[单击此处添加原稿出处]
[单击此处添加译文题目]
[单击此处添加译文正文]
以下是说明文字，正式成文后请删除。
1、模板的使用方法
（1）请不要删除任何具有格式的模板文字。
（2）按照提示直接单击或单击后选择“编辑”→“选择性粘贴”—“无格式文本”就可添加相应内容。
2、在“原稿出处”中对原稿的来源进行说明，包括作者姓名、出处、出版信息等。
期刊类文献书写方法：作者（不超过3人，多者用“等”或“et al”表示）．题名[J]．刊名，出版年，卷号（期号）：起止页码．
论文集类文献书写方法：著者．题名[C]．编者．论文集名．出版地：出版社，出版年份：起止页码．
有一篇译文，按如下顺序列出：
译文题目一
原稿题目一
原稿出处一
3、检索和利用外文资料的能力是现阶段毕业设计（论文）环节中所要求掌握的基本能力之一。
外文翻译是在查阅外文文献时，将篇幅适当、内容与选题相关的外文资料翻译成中文。
通过翻译外文资料，可更深层次地了解国外相关领域的现状，同时也是对翻译能力的锻炼，并为考察和检验学生外语能力提供依据。
4、进行外文翻译应注意以下几点：
（1）翻译的外文文献内容应与论文选题相关；一般应选自国外学术期刊、学术会议的文章及其他相关材料。
（2）篇幅、深度和难度适当，可以由1篇文章组成。
5、外文翻译字符应达到2000字符。
[单击此处添加外文原稿题目] [单击此处添加外文原稿正文]。
毕业设计-外文翻译 正确格式范例
天津科技大学本科生毕业设计（论文）外文资料翻译学院：材料科学与化学工程学院专业：高分子材料与工程姓名：阮孝顺学号：10032411指导教师（签名）：2014年3月15日基底机械附着防水体系ACC板适宜性的确认及其高风压下的强度Michal Bartko a, Hiroyuki Miyauchi a,*, Kyoji Tanaka ba忠南大学，305-764，大田，南韩b日本东京工业大学，226-8503，神奈川县，日本2012年9月7日收到，2013年5月9日收到修改稿，2013年5月19日接受，2013年6月19日发表【摘要】受到强风的影响，机械连接防水体系的蒸气压混凝土板（AAC）的可靠性需要验证。
通过静态和动态拉伸试验研究AAC面板紧固件的优点。
对最常用的机械和化学紧固件的优点和AAC断裂类型进行测试观察。
静态强度值介于2.0至5.0kN之间，动态强度下降范围在１.5到2.2kN之间。
而且，我们创造性的应用了弹性粘合剂来代替常用的环氧树脂从而广泛的消除了ACC断裂。
我们使用专门设计和生产的恒定负载型动态测试仪，检查完整的机械连接的防水体系的特征。
我们测试了两种聚氯乙烯（PVC）卷材的类型和两种不同的卷材和圆盘连接方法。
重复实验，直到失败的次数高达100,000次，并记录在相同强度的强风下实际屋顶发生的断裂类型。
也发现了紧固件的动态强度和完全防水体系之间的关系，证明了AAC面板有足够承载力能够作为机械连接防水体系的基底，也探究出了确定紧固件最大间距的方法。
2013年爱思唯尔公司保留所有权。
【关键词】：机械连接防水体系；AAC镶基板；阻力风；静态和动态测试；断口模式；体系设计方法2013年爱思唯尔公司保留所有权。
1.前言机械连接防水体系是一种干式防水体系，有几个优势，比如不受裂缝和联合移动的影响。
该防水体系适用于多种类型的基板，安装简单容易，可以方便的修复，在技术上和经济上可行。
因此，该体系在日本和全球的使用量正在增长。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
计算机学院2011届
毕业设计译文的格式要求
根据教务处的相关文件的规定，2011 届毕业设计译文格式规范如下：
1）封皮：
译文的封皮采用学校统一的模板，模板的格式见“08届毕业设计指导手册及模板”要求，各位同学将封皮各项全部填写好以后用A4纸张打印出来，到经管学院文印室（D区组团2楼）加土黄色封皮（理工科统一封皮）进行装订；
2）内容：
a.译文部分的格式要求：
前面附翻译好的中文部分，按照学校的要求，可以打印或手写。
装订时在中文译文后面增加一空白页，供
指导老师写评语用。
手写的格式要求如下：
（1）采用“中原工学院毕业设计（论文）译文专用纸”，到计算机学院统一购买（由教务处统一印
发）；
（2）书写工整，必须用黑色钢笔（或黑色签字笔）书写；
（3）翻译的汉字部分要求3000字以上
打印的格式要求如下：
（1）采用W ord 格式排版
（2）中文：正文采用宋体小4号
（3）英文：采用新罗马体12
（4）题目用黑体小2号字
（5）纸张大小：A4
（6）行间距为2倍行距，便于老师批改
（7）页边距：采用A4默认的格式
（8）页眉：
中间标明：中原工学院毕业设计（论文）译文专用纸
右上角标明：第页
b.原文部分的格式要求
后面附英文原文，可以打印，或原件复印。
打印时，W ord 排版格式如下：
（1）英文：采用新罗马体12，1.5倍行距，内封题目用黑体小2号字；
（2）纸张大小：A4
（3）页边距：采用A4默认的格式
（4）页眉：
中间标明：中原工学院毕业设计（论文）译文专用纸
右上角标明：第页
（5）原文出处：在英文的首页注明原文出处
二O一O年十二月。