要求1:完成外文文献及译文的参考样式

合集下载

毕业论文外文翻译格式【范本模板】

毕业论文外文翻译格式【范本模板】

因为学校对毕业论文中的外文翻译并无规定,为统一起见,特做以下要求: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年的《实尾岛》,康佑硕导演了多部成功的电影。

外文翻译的格式样式

外文翻译的格式样式

外文翻译格式样式
标题(黑体小二加粗居中)
(宋体小四空一行)
外文作者署名(楷体小四号居中)
(宋体小四空一行)
1 内容(黑体三号加粗)
1.1内容(黑体四号加粗)
边坡是地壳表部一切具有临空面的地质体,具有一定的坡度和高度,包括人工边坡、自然边坡以及崩滑体。

在重力、风化、侵蚀和其它地质作用下,边坡不断地发生变化,应力重新分布,并且随着边(宋体小四号)……
说明:以上为外文翻译的格式,译文前应附有被翻译的外文原件复印件,为了反映文稿的科学依据和译者尊重他人研究成果的严肃态度及向读者提出有关信息的出处,要求译者按著录/题名/出版事项顺序排列注明,请同学们遵照执行。

期刊:著者,题名,期刊名称,出版年,卷号(期号),起始页码。

书籍:著者,书名、版次(第一版不标注),出版地,出版者,出版年,起始页码。

毕业论文外文文献翻译要求

毕业论文外文文献翻译要求

毕业论文外文文献翻译要求
一、翻译的外文文献可以是一篇,也可以是两篇,但英文字符要求不少于2万
二、翻译的外文文献应主要选自学术期刊、学术会议的文章、有关著作及其他相关材料,应与毕业论文(设计)主题相关,并在中文译文首页用“脚注”形式注明原文作者及出处,外文原文后应附中文译文。

三、中文译文的基本撰写格式为:
1.题目:采用三号、黑体字、居中打印;
2.正文:采用小四号、宋体字,行间距一般为固定值20磅,标准字符间距。

页边距为左3cm,右2.5cm,上下各2.5cm,页面统一采用A4纸。

四、英文的基本撰写格式为:
1.题目:采用三号、Times New Roman字、加黑、居中打印
2.正文:采用小四号、Times New Roman字。

行间距一般为固定值20磅,标准字符间距。

页边距为左3cm,右2.5cm,上下各2.5cm,页面统一采用A4纸.
3.脚注:五号,Times New Roman,顺序为作者.题目.出处,
五、封面格式由学校统一制作(注:封面上的“翻译题目”指中文译文的题目,封面中文小四号宋体,英文小四号Times New Roman),
六、装订:左侧均匀装订,上下共两个钉,并按“封面、外文原文、译文”的顺序统一装订。

七、忌自行更改表格样式
大连工业大学艺术与信息工程学院
毕业设计(论文)外文文献
外文题目
翻译题目
系别
专业班级
学生姓名
指导教师
大连工业大学艺术与信息工程学院
毕业设计(论文)开题报告
题目名称
系别
专业班级
学生姓名
指导教师
开题报告日期年月日。

外文翻译规范要求及模版格式

外文翻译规范要求及模版格式

外文翻译规范要求及模版格式
外文中文翻译规范要求及模板格式可以根据具体需求和要求有所不同,以下是一般常见的外文中文翻译规范要求及模板格式:
1.规范要求:
-符合语法、语言规范和语义准确性;
-译文流畅自然,符合中文表达习惯;
-忠实准确地传达原文信息;
-注意统一使用特定的术语翻译;
-文章结构、段落、标题等要与原文一致;
-保持适当的篇幅,不过度增加或删减内容;
-遵守保密原则。

2.模板格式:
-文章标题(与原文保持一致,可放在正文上方);
-标题(与原文保持一致);
-段落(与原文保持一致,首行缩进);
-字体(常用宋体或黑体,一般字号12或14);
-行间距(一般1.5倍,可根据需要调整);
-页边距(上下左右均为2.5厘米);
-段落间距(一般1.5倍,可根据需要调整);
以上是一般常见的外文中文翻译规范要求及模板格式,具体要求和格式可以根据具体的翻译项目和要求进行调整。

在翻译过程中,保持准确、流畅、专业是非常重要的。

外文翻译与文献综述模板格式以及要求说明

外文翻译与文献综述模板格式以及要求说明

外文翻译与文献综述模板格式以及要求说明
外文中文翻译格式:
标题:将外文标题翻译成中文,可以在括号内标明外文标题
摘要:将外文摘要翻译成中文,包括问题陈述、研究目的、方法、结果和结论等内容。

关键词:将外文关键词翻译成中文。

引言:对外文论文引言进行翻译,概述问题的背景、重要性和研究现状。

方法:对外文论文方法部分进行翻译,包括研究设计、数据采集和分析方法等。

结果:对外文论文结果部分进行翻译,介绍研究结果和统计分析等内容。

讨论:对外文论文讨论部分进行翻译,对研究结果进行解释和评价。

结论:对外文论文结论部分进行翻译,总结研究的主要发现和意义。

附录:如果外文论文有附录部分,需要进行翻译并按照指定的格式进行排列。

文献综述模板格式:
标题:文献综述标题
引言:对文献综述的背景、目的和方法进行说明。

综述内容:按照时间、主题或方法等进行分类,对相关文献进行综述,可以分段进行描述。

讨论:对综述内容进行解释和评价,概括主要研究成果和趋势。

结论:总结文献综述,概括主要发现和意义。

要求说明:
1.外文中文翻译要准确无误,语句通顺流畅,做到质量高、符合学术
规范。

2.文献综述要选择与所研究领域相关的文献进行综述,覆盖面要广,
内容要全面、准确并有独立思考。

4.文献综述要注重整体结构和逻辑连贯性,内容要有层次感,段落间
要过渡自然。

5.外文中文翻译和文献综述要进行查重,确保原文与译文的一致性,
并避免抄袭和剽窃行为。

毕业设计(论文)外文资料和译文格式要求(模板)

毕业设计(论文)外文资料和译文格式要求(模板)

成都东软学院外文资料和译文格式要求一、译文必须采用计算机输入、打印,幅面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的布局文件。

毕业论文外文翻译格式【范本模板】

盐城师范学院毕业论文(设计)外文资料翻译学院:(四号楷体_GB2312下同)专业班级:学生姓名:学号:指导教师:外文出处:(外文)(Times New Roman四号) 附件: 1.外文资料翻译译文; 2.外文原文1.外文资料翻译译文译文文章标题×××××××××正文×××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××………….*注:(本注释不是外文翻译的部分,只是本式样的说明解释)1. 译文文章标题为三号黑体居中,缩放、间距、位置标准,无首行缩进,无左右缩进,且前空(四号)两行,段前、段后各0.5行间距,行间距为1。

25倍多倍行距;2. 正文中标题为小四号,中文用黑体,英文用Times New Roman体,缩放、间距、位置标准,无左右缩进,无首行缩进,无悬挂式缩进,段前、段后0。

5行间距,行间距为1.25倍多倍行距;3。

正文在文章标题下空一行,为小四号,中文用宋体,英文用Times New Roman体,缩放、间距、位置标准,无左右缩进,首行缩进2字符(两个汉字),无悬挂式缩进,段前、段后间距无,行间距为1。

要求1:完成外文文献及译文的参考样式

山东建筑大学毕业论文外文文献及译文
毕业论文要求1
1. 本次发给你四个文件:论文要求1,任务书,开题报告,论文的结构建议。

2. 阅读开题报告的文献综述一栏,然后阅读相关的书籍、著作、期刊文章或网络上查阅到的文章,主要阅读你的文章中的与你的论文主题相关的内容;
3. 在3月底以前完成“外文文献及译文”内容。

查找与你的论文题目有一定关
系的著作、期刊或网络文章上的英文内容,并将英文翻译成中文。

4. 请将英文原文与你的中文翻译部分按照下面给你的参考格式完成。

格式如后
面的第2页开始到最后。

其中文献、资料来源要注明是著作、网络、期刊等的哪一种,例如,参考的格式中注明的就是著作。

5. 注意参考格式中的页眉、页脚、题目字号、字体、正文内容字体、字号。


撰写的外文文献要与参考格式的要求一致。

6. 外文文献部分要求字数在5000字以上。

即中文翻译内容的字数要达到5页以
上,含表格、图样等。

7. 对照论文的结构建议,查阅相应的内容,开始构思论文。

8. 外文文献及译文完成后,及时发给老师电子版。

以便审校。

老师:徐宁,
2014年3月9号
- 1 -。

外文文献及翻译格式模版

毕业设计外文文献及译文文献、资料题目:INTELLIGENT BUILDING ALARM 文献、资料来源:网络文献、资料发表(出版)日期:2012,2院(部):信息与电气工程学院专业:电气工程与自动化班级:电气084姓名:邓红坤学号: 2008121017指导教师:王克河翻译日期:2012、2、29外文文献:INTELLIGENT BUILDING ALARMBACKGROUND OF THE INVENTIONThis invention relates to an intelligent alarm system for 5 detecting hazardous situations ina building informing building occupants of optimal escape routes or survival strategies and assisting emergency personnel in rescuing people inside the building。

Building hazards, including fire,earthquakes,intruders,etc., have the potential for large numbers of casualties. Effective building alarm systems must have the capability to process a plurality of input types to determine the nature of the situation involving danger to persons in thebuilding. The building alarm system must also have more than simple audio/visual outputs for helping people in the building find safe escape routes.Use of the term building in this invention refers to any structure including,but not limited to, office buildings, commercial buildings,factory/warehouses, residential homes, etc. Aspectsof building alarm systems are described 20 in, U.S。

外文翻译及外文原文(参考格式)

外文翻译要求:1、外文资料与毕业设计(论文)选题密切相关,译文准确、质量好。

2、阅读2篇幅以上(10000字符左右)的外文资料,完成2篇不同文章的共2000汉字以上的英译汉翻译3、外文资料可以由指导教师提供,外文资料原则上应是外国作者。

严禁采用专业外语教材文章。

4、排序:“一篇中文译文、一篇外文原文、一篇中文译文、一篇外文原文”。

插图内文字及图名也译成中文。

5、标题与译文格式(字体、字号、行距、页边距等)与论文格式要求相同。

下页附:外文翻译与原文参考格式2英文翻译 (黑体、四号、顶格)外文原文出处:(译文前列出外文原文出处、作者、国籍,译文后附上外文原文)《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. 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
  2. 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
  3. 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。

毕业论文要求11.本次发给你四个文件:论文要求1,任务书,开题报告,论文的结构建议。

2.阅读开题报告的文献综述一栏,然后阅读相关的书籍、著作、期刊文章或网络上查阅到的文章,主要阅读你的文章中的与你的论文主题相关的内容;3.在3月底以前完成“外文文献及译文”内容。

查找与你的论文题目有一定关系的著作、期刊或网络文章上的英文内容,并将英文翻译成中文。

4.请将英文原文与你的中文翻译部分按照下面给你的参考格式完成。

格式如后面的第2页开始到最后。

其中文献、资料来源要注明是著作、网络、期刊等的哪一种,例如,参考的格式中注明的就是著作。

5.注意参考格式中的页眉、页脚、题目字号、字体、正文内容字体、字号。

你撰写的外文文献要与参考格式的要求一致。

6.外文文献部分要求字数在5000字以上。

即中文翻译内容的字数要达到5页以上,含表格、图样等。

7.对照论文的结构建议,查阅相应的内容,开始构思论文。

8.外文文献及译文完成后,及时发给老师电子版。

以便审校。

老师:徐宁,2014年3月9号- 1 -本科毕业论文外文文献及译文文献、资料题目:Preface to the Chinese Edition文献、资料来源注明期刊(著作、网络等)著作:学习与认知发展文献、资料发表(出版)日期:2011.6.30院(部):理学院专业:信息与计算科学班级:信计071姓名:鲍文操学号:2007121230指导教师:徐宁翻译日期:2011.6.30- 2 -外文文献:Preface to the Chinese EditionThe patient construction of embedded structures is the only developmental mechanism preserving maturation and learning as factors of cognitive growth in a rational,coherent and cogent fashion .Learning is not the sole motor of knowledge.On the other hand,the maturation of the growing mind is useless if not in interaction with learning experience.The interest of this book resides in its demonstration that the encounter between maturation and learning cannot happen any time,any way,anyhow but by a system of logical checks and balances amongthese competing factors. It has to come when a new level of equilibrium among the various factors involved in the act of knowing has been reached.Otherwise,more learning,further maturation are a waste of time as it is so often the case in methods centered around rote learning, drill and conditioning , on the one hand,and in educational settings in which freedom,spontaneity and improvisation,on the other hand,reign as masters of pedagogy. It is this special chemistry of transition that hasbeen tracked down in the studies composing this book.This process resembles in many ways Waddington's notion of chreod in embryology.As chreods are sorts of necessary pathways for the development of embryo,so are transitional processes in cognitive development.The analogy can be pushed further into details that seem revealing.C. Waddington regards the genetic system as composed of the interaction of different spaces,genotypic,epigenetic,phenotype and fitness spaces.This multiplicity is required by the necessity for the embryologist to distinguish life from mere information. The genotypic space is characterized by the transmission of mere information, the genes,- 3 -from one generation to the next one.This is trivial and fairlyuninteresting.The phenotype is the result of what is transmitted in the DNA(or memory store)the genotype or mere information and what is produced,on the basis of DNA instruction,to the protein composing the organism.The fitness space(the number of offspring a phenotype leaves behind) is the space on which operates natural selection. The epigenetic space stabilizes the time trajectory so that each genotype can instruct the phenotype on which it acts to produce,thanks to a system of appropriate interesting differentiation,an organism with different and distinct organs out of what was,at an earlier stage,a single mass of undifferentiated tissue.This stabilized time trajectory is called chreod by Waddington.The epigenetic space is characterized by a number of such chreods that keep development in the embryo on its tracks by virtue of its own mathematical properties(double randomness of initial conditions).These mathematical properties impose a necessary,obligatory pathway to the system as well as an upper limit in which the system reaches equilibrium.stops to develop and becomes mature.But , as the organism evolves,it changes the balance among surrounding organisms and systems leading to the production of random mutations to the recombination of existing phenotypes and stress adaptation(a process repeated over time producing a phenotype alteration modifying its corresponding chreod in such always as to make the existence of any further stress unnecessary for the alteration to appear :thus,the phenotypic alteration has been assimilated to the genotype) As the reader can see,the analogy is striking between Waddington's genetic assimilation and Piaget's theory of development. But, it is even more so with the present volume, as well as try to show now. In cognition,hereditary behavior could be the functional equivalentof genes in biological development.It provides basic information to- 4 -survive.The responses of the child form the phenotype. The fitness space is the amount of activity displayed by the child. The epigenetic space is precisely what all this book is about:it demonstrates the stability of the developmental sequence over time and how every piece of puzzle has to come into the picture at the fight moment. But the analogy could be read in a different way. In our experimental situation ,first comes a perturbation,which is disregarded by the child.Then it is taken into consideration. At last,it is anticipated and be comes inherent to the child's mental organization prior to any contact with reality.This process of equilibration is facilitated by training procedures.But these procedures are not the cause of progress.Here,one should distinguish between knowledge acquired from experience,which is learning sensu and knowledge acquired in experience,or equilibration.So,many of the criticism made to this book become obsolete,since they rely on the general assumption of learning from experience and not learning in experience.Learning in experience requires the formation of mental structures.These structures,in addition,are hierarchically organized.They are also constructed from procedures are shown in this book. A procedure is inherently particularistic since it is attributed to an individual person in a certain context differs from a structure is temporal and not goal-oriented but properties that make them precursor of structures . These properties are essentially two : recursion (a procedure can be re-activated endlessly )and generality (a procedure can be generalized to new context in variable ways). These two properties pave the way for the emergence of structures that are characterized by objectivity and intersubjectivity.- 5 -中文译文:学习与认知发展对固有内部认知结构加以耐心的构建,才是认知发展的唯一机制。

相关文档
最新文档