2016年外文翻译撰写要求与格式规范x
文献综述外文翻译写作规范及要求
文献综述外文翻译写作规范及要求
文献综述是对已经发表的学术文献进行系统的综合分析和评价的一种
学术写作形式。
在撰写文献综述的过程中，外文翻译是不可或缺的一部分。
下面是一些关于外文翻译的写作规范和要求。
1.准确：外文翻译要准确无误地表达原文的意思。
翻译过程中应注意
遵守语法规则、掌握专业术语以及正确理解上下文。
2.逻辑清晰：翻译后的中文句子要符合中文语法和表达习惯，并保持
逻辑上的连贯。
避免使用过于生硬或拗口的句子结构。
3.简洁明了：文献综述注重对已有文献的概括和总结，因此翻译过程
中应力求简洁明了，避免翻译过多的细节和废话。
4.专业术语准确翻译：外文翻译中的专业术语在翻译过程中要保持准
确性。
可以参考已有的专业词典、论文翻译表格等工具来确保专业术语的
正确翻译。
5.文体和语气恰当：根据不同的文献类型和句子语境，选择合适的文
体和语气进行翻译。
可以参考论文综述的写作规范和范例，避免过于口语
化或过于正式的翻译。
在撰写文献综述的过程中，准确和恰当的外文翻译是非常重要的。
只
有通过准确和规范的翻译，才能保证文献综述的质量和可信度。
因此，应
该注重提升外文翻译的能力并积极学习相关的写作规范和要求。
外文翻译规范要求及模版格式
外文翻译规范要求及模版格式
外文中文翻译规范要求及模板格式可以根据具体需求和要求有所不同，以下是一般常见的外文中文翻译规范要求及模板格式：
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的布局文件。
毕业论文外文翻译要求
毕业论文外文翻译要求
外国文献翻译是撰写毕业论文的重要环节之一，下面是一份要求700字的毕业论文外文翻译要求：
1. 翻译时间: 需在规定时间内完成翻译任务，以确保毕业论文
后续工作的顺利进行。
2. 原文准确性: 翻译必须准确无误，不得对原文进行任何删节、增补或变动。
3. 语言流畅度: 翻译应当具有良好的语言流畅度，不得过于生
硬或呆板。
4. 专业术语准确性: 翻译时要确保专业术语的准确性，避免词
义的混淆。
5. 语法错误及标点符号: 翻译应符合英文的语法规范，避免语
法错误和标点符号的错误使用。
6. 翻译风格: 翻译应当符合学术论文的要求，措辞恰当，语气
客观中立。
7. 格式要求: 翻译部分应与论文正文的格式一致，包括字体、
字号、行间距等。
8. 校对: 完成翻译后，需要进行一次仔细的校对工作，确保翻
译的正确性。
9. 原文附录: 翻译部分要同时附上原文，以便审查人员对翻译的准确性进行核对。
10. 翻译文档: 翻译文档要以电子文档的形式提交，确保方便审查人员查看。
以上要求旨在保证翻译的质量和准确性，对于撰写毕业论文非常重要。
翻译过程中，建议使用专业的翻译工具，如翻译记忆软件、专业词典等，以提高翻译的效率和准确性。
同时，积极与导师和专业领域的人进行交流和讨论，以解决翻译中的问题和困惑。
毕业论文外文翻译格式
毕业论文外文翻译格式毕业论文外文翻译格式在如今全球化的时代，学术研究的国际交流变得越来越重要。
而对于毕业论文来说，外文翻译是一个必不可少的环节。
毕业论文外文翻译格式的正确与否，不仅关系到论文的质量，还直接影响到读者对论文内容的理解和接受程度。
因此，本文将探讨毕业论文外文翻译的格式要求，以帮助学生们更好地完成这一环节。
首先，毕业论文外文翻译的格式应该与原文一致。
这意味着学生需要尽可能地保留原文的结构、段落和标点符号等要素。
这样做的目的是为了让读者能够更好地理解原文的内容，同时也方便学术界对研究成果进行评估和交流。
当然，在保持原文结构的基础上，学生也可以适当地进行调整和修饰，以使翻译更加流畅和易读。
其次，毕业论文外文翻译的格式还应包括适当的引用和注释。
在翻译过程中，学生可能会遇到一些特定的术语、名词或引文，这时需要在翻译文中进行相应的注释或解释。
这不仅有助于读者对论文内容的理解，还能提高论文的可信度和学术价值。
同时，在引用他人研究成果时，学生也需要按照学术规范进行引用，包括作者姓名、出版年份、文章标题等信息，并在文末提供详细的参考文献列表。
另外，毕业论文外文翻译的格式还应注意语言风格的统一和准确。
学生在翻译过程中应尽量使用专业术语和学术语言，以确保翻译的准确性和学术性。
同时，还需要注意语言风格的统一，避免在翻译中出现过多的个人化表达和口语化用语。
这样可以使翻译更加规范和正式，符合学术写作的要求。
此外，毕业论文外文翻译的格式还应注意排版和格式要求。
学生需要将翻译文与原文进行对照排列，以便读者对照阅读。
同时，还需要注意字体、字号、行距等排版要求，使翻译文看起来整洁、清晰。
另外，学生还可以根据需要在翻译文中加入图表、图像或表格等辅助材料，以更好地展示研究结果和论证过程。
最后，毕业论文外文翻译的格式还应注意语法和语义的准确性。
学生在翻译过程中需要注意语法结构的正确性，避免出现句子不通顺或语义不清的情况。
同时，还需要准确理解原文的意思，并用恰当的词语和表达方式进行翻译。
外文翻译格式要求：
外文翻译格式要求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、两篇文献。
二、基本格式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倍页眉页角：页眉的奇数页书写—浙江师范大学学士学位论文外文翻译。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
沈阳工业大学本科生毕业设计（论文）外文翻译撰写要求与格式规范根据《沈阳工业大学毕业设计（论文）工作的规定》，对本科生毕业设计（论文）外文翻译要求如下：一、参加毕业设计（论文）的学生必须翻译一篇外文原文资料（外语专业除外）。
二、外文文献应由指导教师审定，必须与所学专业及毕业设计内容密切相关。
三、外文文献应选自学术期刊、学术会议的文章、著作及其他相关材料，并列入毕业设计（论文）的参考文献。
四、外文文献要不少于一万二千个外文印刷符号（约三千汉字）。
五、指导教师应对学生外文翻译与毕业设计内容的相关性、翻译量及翻译的准确性等进行综合评价，手写不少于40字的评语并签名。
六、外文原文可以复印，也可以打印电子期刊原文。
七、译文采用A4纸印刷，边距：上下2.54厘米，左3.50厘米，右2.5厘米，左侧装订。
大标题黑体小三号字，一级标题黑体四号，二级标题黑体小四号，正文宋体小四号。
八、装订顺序依次为封面、原文、译文、指导教师评语。
教务处2016年3月本科生毕业设计（论文）外文翻译学院：文法学院学号：140607214专业班级：环境设计1402班学生姓名：辛萌指导教师：王磊2018年3 月14 日Landscape planning and design of residential green space1 topic sourcesThe project comes from the social production practice of the instructor.2 purpose and significance of research2.1 the purpose of the studyThe modern residential district is increasing with unprecedented speed and quantity, and the landscape design of residential area is becoming more and more important. The landscape is usually in a variety of ways to meet different users. The goal of the design is to create a space that combines society, environment, culture, aesthetics and practical functions. Therefore, the landscape is a system of living, dynamic, ecological and cultural. The landscape design of residential area is closely related to our relationship. It has its own characteristics and development trend. With the rapid development of modern Chinese cities, global integration has made frequent international exchanges and highly shared information. How to assimilate the latest technological achievements and design trend of the world with conditional self concept is one of the common concerns of contemporary designers. The purpose of this study is to analyze the landscape planning and design of modern residential areas at home and abroad, and to summarize the landscape planning and design scheme suitable for the two phase of Ziyun government. For the fusion of classical and modern, Qucuqujing, with European style as the theme, to learn the essence China garden, ideal residential environment, the creation of ecological environment protection and sustainable development, to create a good living environment for residents.2.2 significance of researchThe survival of mankind is inseparable from the necessities of life, and the content and content of life are all generated by living. This kind of living activity is called "the first activity of the city" in the Athens charter. As the main place of human activity - the residential area, it bears our needs for a good life. The advantages and disadvantages of human living environment not only relate to people's quality of life and health, but also reflect the culture of the city. As an index of improving the quality of people's life, urban landscape plays a decisive role. Landscape design of residential area has also become an indispensable part of urban landscape system. The design of anappropriate and sustainable ecological residential area integrating garden art and culture and art is not only a need for balancing the urban artificial ecosystem and creating the grade of the residential district, but also an important guarantee for the people to live and work in peace and contentment. For this reason, real estate developers have developed residential landscape residential areas with the theme of "landscape", "environmental protection", "ecology", "culture", "intelligence" and "green health".3 domestic and foreign present situation and development trend and the main direction of research3.1 landscape status of residential areas at home and abroadThe status quo of the landscape of 4.1.1 western residential areaAt the beginning of nineteenth Century, the industrial developed Europe produced a variety of environmental problems, so the emergence of a group of men and women with high ideals to how to avoid the pollution caused by industrialization and contradiction between urban and rural areas of the road, and thinking about how to protect nature resources and make full use of the ladder problem. Landscape design in early residential areas is often simply understood as greening design. Landscape layout is also dominated by horticultural landscaping. Landscape planning and design are often attached to architectural design in residential area planning and design. First, plan the building and make landscape planning and design. This method usually separates the close relationship between the architecture and the landscape, and brings about the disharmony between the architecture and the landscape design. In view of this phenomenon, the father of American landscape Olmsted proposed the concept of "landscape architecture", the landscape architecture as the research object of the professional. The most important feature is to plan and design the overall style of the residential area at the beginning of the planning and design of the residential area, and make a thematic study of the environmental landscape of the residential area, and put forward the concept planning of the landscape. In this way, from the very beginning, we must grasp the design of hard landscape, divide the buildings with ingenious buildings and enclose the space, so that buildings and landscapes can be melted in the overall design of residential areas.The present situation of residential landscape in 4.1.2The traditional western garden culture can be traced back to ancientEgypt. Chinese gardens originated from Shang and Zhou dynasties. Afterthousands of years of development, the Qing Dynasty reached the peak ofclassical gardens. At this time, Chinese gardens began to be influencedby western gardens, the most profound is the Old Summer Palace, with alarge number of European style architecture. Although the history ofgarden development in China has been thousands of years, the researchof modern landscape architecture is only for decades, and the conceptof residential landscape has been slowly appearing in people's view inrecent years, thus forming a superficial understanding of residential landscape. Unlike the royal gardens in order to express the authorityof the rulers, private gardens in the south of the Yangtze River put moreemphasis on natural aspirations and aspirations of literati under feudalautocratic rule. However, whether they are royal or private gardens, thecultural functions they carry are very different from those of Europeangardens. Since the reform and opening up, with the rise of the real estateindustry and the increasingly intensified globalization, thedevelopment of Chinese landscape is being strongly impacted by the worldculture, so there are many problems in the landscape design ofresidential area. People blindly pursue European style garden style,lack of ignoring the inherent spirit of European landscape, simpleimitation become mishap in the residential landscape, landscape patternmachine-made appearing in each city of the residential area, not onlylost also lost cultural characteristics.3.2 development at home and abroadTrend and main direction of research Research and development trend of3.2.1 western residential landscapeWestern gardens, as well as Chinese gardens, have a long history, bothof which are valuable wealth for the development of human civilization.The emergence of gardens should be when human desires have created beauty,that is, the return of the human expectation to the lost paradise.居住绿地景观规划设计1 题目来源课题来源于指导老师的社会生产实践。