毕业论文 外文翻译格式
本科毕业论文外文翻译【范本模板】
本科毕业论文外文翻译外文译文题目:不确定条件下生产线平衡：鲁棒优化模型和最优解解法学院：机械自动化专业：工业工程学号: 201003166045学生姓名: 宋倩指导教师：潘莉日期: 二○一四年五月Assembly line balancing under uncertainty: Robust optimization modelsand exact solution methodÖncü Hazır , Alexandre DolguiComputers ＆Industrial Engineering，2013,65：261–267不确定条件下生产线平衡：鲁棒优化模型和最优解解法安库·汉泽，亚历山大·多桂计算机与工业工程，2013，65：261–267摘要这项研究涉及在不确定条件下的生产线平衡，并提出两个鲁棒优化模型。
假设了不确定性区间运行的时间。
该方法提出了生成线设计方法,使其免受混乱的破坏。
基于分解的算法开发出来并与增强策略结合起来解决大规模优化实例.该算法的效率已被测试,实验结果也已经发表。
本文的理论贡献在于文中提出的模型和基于分解的精确算法的开发.另外，基于我们的算法设计出的基于不确定性整合的生产线的产出率会更高，因此也更具有实际意义。
此外,这是一个在装配线平衡问题上的开创性工作,并应该作为一个决策支持系统的基础。
关键字：装配线平衡；不确定性; 鲁棒优化；组合优化；精确算法1.简介装配线就是包括一系列在车间中进行连续操作的生产系统。
零部件依次向下移动直到完工。
它们通常被使用在高效地生产大量地标准件的工业行业之中。
在这方面，建模和解决生产线平衡问题也鉴于工业对于效率的追求变得日益重要。
生产线平衡处理的是分配作业到工作站来优化一些预定义的目标函数。
那些定义操作顺序的优先关系都是要被考虑的,同时也要对能力或基于成本的目标函数进行优化。
就生产（绍尔，1999）产品型号的数量来说，装配线可分为三类：单一模型（SALBP）,混合模型(MALBP）和多模式（MMALBP）。
毕业论文外文翻译要求
毕业论文外文翻译要求The requirements for the translation of the foreign language section of the graduation thesis are as follows:1. Word Count: The translated foreign language section should be around 700 words.2. Accuracy: Ensure the translated text accurately reflects the original meaning and intent of the foreign language source. It should be free from any substantial errors or omissions.3. Language Style: Maintain a professional and academic tone throughout the translation. Use appropriate terminology and vocabulary to convey the subject matter effectively.4. Grammar and Syntax: Follow the rules of grammar and syntax in the target language. Pay attention to sentence structure, verb agreement, and correct word order.5. Consistency: Ensure consistency throughout the translation. Use the same terminology and style for recurring words, phrases, and concepts.6. Flow and Cohesion: Maintain the flow and cohesion of the translated text. Use appropriate transition words and phrases to connect ideas and ensure a smooth reading experience.7. Cultural Sensitivity: Take into account any cultural nuances or references that might require adaptation or explanation in the translated text. Consider the target audience's cultural backgroundand adapt the language accordingly.8. Formatting: Format the translated text to match the formatting requirements of the graduation thesis. Ensure proper indentation, paragraph spacing, and font style.9. Proofreading: Thoroughly proofread the translated text to identify and correct any typos, spelling errors, or grammatical mistakes.10. Delivery: Submit the translated foreign language section within the specified deadline. Provide the translated text in a compatible format, such as a Word document or PDF file.By adhering to these requirements, the translated foreign language section of the graduation thesis will meet the desired standards of quality and accuracy.。
本科毕业设计(论文)外文翻译基本规范
本科毕业设计（论文）外文翻译基本规范一、要求1、与毕业论文分开单独成文。
2、两篇文献。
二、基本格式1、文献应以英、美等国家公开发表的文献为主（Journals from English speaking countries）。
2、毕业论文翻译是相对独立的，其中应该包括题目、作者（可以不翻译）、译文的出处（杂志的名称）（5号宋体、写在文稿左上角）、关键词、摘要、前言、正文、总结等几个部分。
3、文献翻译的字体、字号、序号等应与毕业论文格式要求完全一致。
4、文中所有的图表、致谢及参考文献均可以略去，但在文献翻译的末页标注：图表、致谢及参考文献已略去(见原文)。
（空一行，字体同正文）5、原文中出现的专用名词及人名、地名、参考文献可不翻译，并同原文一样在正文中标明出处。
二、毕业论文（设计）外文翻译（一）毕业论文（设计）外文翻译的内容要求外文翻译内容必须与所选课题相关，外文原文不少于6000个印刷符号。
译文末尾要用外文注明外文原文出处。
原文出处：期刊类文献书写方法：[序号]作者（不超过3人，多者用等或et al表示）.题（篇）名[J].刊名（版本）,出版年，卷次（期次）：起止页次.原文出处：图书类文献书写方法：[序号]作者.书名[M].版本.出版地：出版者,出版年.起止页次.原文出处：论文集类文献书写方法：[序号]作者.篇名[A].编著者.论文集名[C]. 出版地：出版者，出版年.起止页次。
要求有外文原文复印件。
（二）毕业论文（设计）外文翻译的撰写与装订的格式规范第一部分：封面1.封面格式:见“毕业论文（设计）外文翻译封面”。
普通A4纸打印即可。
第二部分：外文翻译主题1.标题一级标题，三号字，宋体，顶格，加粗二级标题，四号字，宋体，顶格，加粗三级标题，小四号字，宋体，顶格，加粗2.正文小四号字，宋体。
第三部分：版面要求论文开本大小：210mm×297mm（A4纸）版芯要求：左边距：25mm，右边距：25mm，上边距：30mm，下边距：25mm，页眉边距：23mm，页脚边距：18mm字符间距：标准行距：1.25倍页眉页角：页眉的奇数页书写—浙江师范大学学士学位论文外文翻译。
毕业论文外文翻译(中英文)
译文交通拥堵和城市交通系统的可持续发展摘要:城市化和机动化的快速增长,通常有助于城市交通系统的发展，是经济性，环境性和社会可持续性的体现,但其结果是交通量无情增加，导致交通拥挤。
道路拥挤定价已经提出了很多次，作为一个经济措施缓解城市交通拥挤，但还没有见过在实践中广泛使用，因为道路收费的一些潜在的影响仍然不明。
本文首先回顾可持续运输系统的概念,它应该满足集体经济发展,环境保护和社会正义的目标.然后,根据可持续交通系统的特点，使拥挤收费能够促进经济增长，环境保护和社会正义。
研究结果表明,交通拥堵收费是一个切实有效的方式，可以促进城市交通系统的可持续发展。
一、介绍城市交通是一个在世界各地的大城市迫切关注的话题。
随着中国的城市化和机动化的快速发展,交通拥堵已成为一个越来越严重的问题,造成较大的时间延迟,增加能源消耗和空气污染，减少了道路网络的可靠性．在许多城市,交通挤塞情况被看作是经济发展的障碍.我们可以使用多种方法来解决交通挤塞,包括新的基础设施建设，改善基础设施的维护和操作,并利用现有的基础设施,通过需求管理策略,包括定价机制,更有效地减少运输密度.交通拥堵收费在很久以前就已提出，作为一种有效的措施,来缓解的交通挤塞情况。
交通拥堵收费的原则与目标是通过对选择在高峰拥挤时段的设施的使用实施附加收费,以纾缓拥堵情况．转移非高峰期一些出行路线,远离拥挤的设施或高占用车辆，或完全阻止一些出行,交通拥堵收费计划将在节省时间和降低经营成本的基础上,改善空气中的质量，减少能源消耗和改善过境生产力。
此计划在世界很多国家和地方都有成功的应用。
继在2０世纪70年代初和8０年代中期挪威与新加坡实行收费环,在20０３年2月伦敦金融城推出了面积收费；直至现在,它都是已经开始实施拥挤收费的大都市圈中一个最知名的例子。
然而,交通拥堵收费由于理论和政治的原因未能在实践中广泛使用。
道路收费的一些潜在的影响尚不清楚,和城市发展的拥塞定价可持续性,需要进一步研究。
毕业论文正文、文献综述和外文翻译文本编辑排版格式要求
附12-2：毕业论文正文、文献综述和外文翻译文本编辑排版格式要求1、标题：三号宋体居中。
2、作者姓名，学号，班级小四号宋体，居中。
3、中文摘要，中文关键词。
中文摘要和关键词用小五号宋体。
其中“摘要，关键词”用黑体小五号，后面加冒号，关键词之间用分号隔开，关键词一般不超过5个。
4、正文的一级标题用四号宋体，二级标题用小四号黑体，三级标题用五号黑体，正文中文字符用五号宋体。
标题统一采用1; 1.1; 1.1.1; 2; 2.1; 2.1.2; …的样式。
标题最多为三级。
5、文中引用参考文献，统一用[1]的格式，上标。
6、参考文献用小五号字体，中文用宋体。
“参考文献”四字用宋体四号。
参考文献著录格式：序号（统一用[1]的格式）著者（如有多个作者，列出前三名，其余用“等”表示，英文用“et al”表示。
）. 文献题名[文献类型代码]（其中，专著为M，期刊为J，标准为S，学位论文为D，报告为R，论文集为C，专利为P，报刊新闻为N，论文集中析出文献为A）. 期刊名，年，卷（期）：起止页码. 其中卷加粗。
著录格式如下例：[1] 王子健,吕怡兵,王毅等. 淮河水体多介质取代苯类污染及其生态健康风险[J]. 环境科学学报, 2002,22(3): 300~304.[2] Lueking A D, Huang W, Soderstrom-Schwarz S, et al. The chemical structure of soil /sediment organic matter and its role in the sequestration and bioavailability of sorb ed organic contaminants[J]. Journal of Environment Quality, 2000,29(1):317~323. [3] 史忠宝. 建设项目环境影响评价[M]. 北京：中国环境科学出版社，1994.。
毕业论文外文翻译格式
因为学校对毕业论文中的外文翻译并无规定，为统一起见，特做以下要求：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．原文必须选用与课题相关的国外学者所著的学术专著或学术文章，不能选用教材类作品或中国作者撰写的英文文章。
2．中文译文不少于3000汉字。
3．原文资料用毕业论文稿纸单面复印，页边距与毕业论文稿纸一致，便于装订。
装订时，原文在前，译文在后。
原文和译文合计页码总数，在文本每页右上角用五号Times New Roman 标明页码。
4．原文的处理方式针对所选资料不同，区别对待：1）复印书本、期刊、论文集，需包含书的封面、选译章节；2）节选自网络文章，应调整好电子文档格式，按照英文Times New Roman，标题四号加粗（若有副标题，小四号加粗），正文五号。
中文译文宋体，标题四号加粗，正文五号。
原文及译文正均采用1.5倍行距，文中若有小标题，一律五号加粗。
5．外文著录格式按照正规参考文献的范式进行，“著录-题名-出版事项”的顺序排列注明。
1）若选自期刊：著者，题名，期刊名称，出版年，卷号（期号），起始页码。
外文著录：Liu Shaozhong, Liao Fengrong. S tudies of negative pragmatic transfer in interlanguage pragmatics[J]. Journal of Guangxi Normal University, 2002, (4):34-45.2）若选自论文集：著者，题名，论文集名称，编者，出版地，出版社，出版年，起始页码。
例如：外文著录：Thomas, J. Cross-Cultural Pragmatic Failure[A]. Edited by He Zhaoxiong. Selected Reading For Pragmatics[C]. Shanghai: Shanghai Foreign Language Education Press, 2003:677-714.3）若选自书籍：著者，书名，版次（第一版不标注），出版地，出版者，出版年，起始页码。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
毕业论文外文翻译格式
毕业论文外文翻译格式
在撰写毕业论文时，外文翻译是一个重要的环节。
无论是引用外文文献还是翻译相关内容，都需要遵循一定的格式和规范。
本文将介绍一些常见的外文翻译格式，并探讨其重要性和应用。
首先，对于引用外文文献的格式，最常见的是使用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.
翻译：
工作场所有效沟通的重要性不容忽视。
在翻译相关内容时，需要注意保持原文的意思和语气。
尽量使用准确的词汇和语法结构，以便读者能够理解和接受翻译后的内容。
同时，还需要在翻译后的文本后面加上“翻译者”和“翻译日期”的信息，以便读者可以追溯翻译的来源和时间。
此外，对于长篇外文文献的翻译，可以考虑将其分成若干章节，并在每个章节前面加上章节标题。
这样可以使读者更容易理解和阅读翻译后的内容。
同时，还可以在每个章节后面加上总结或评论，以便读者对该章节的内容有更深入的理解和思考。
总之，外文翻译在毕业论文中起着重要的作用。
遵循适当的格式和规范可以确保翻译的准确性和可追溯性。
同时，注意保持原文的意思和语气，以便读者能够理解和接受翻译后的内容。
此外，对于长篇外文文献的翻译，可以考虑分章节并添加章节标题，以便读者更好地理解和阅读。
在撰写毕业论文时，我们应该重视外文翻译的格式，并努力提高翻译的质量和准确性。