外文参考文献及翻译稿的要求与格式

合集下载

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

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

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

2.模板格式:
-文章标题(与原文保持一致,可放在正文上方);
-标题(与原文保持一致);
-段落(与原文保持一致,首行缩进);
-字体(常用宋体或黑体,一般字号12或14);
-行间距(一般1.5倍,可根据需要调整);
-页边距(上下左右均为2.5厘米);
-段落间距(一般1.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的布局文件。

参考文献中英文格式

参考文献中英文格式

参考文献中英文格式
当涉及到引用参考文献时,不同的学科领域和期刊会有不同的要求和规范。

一般来说,英文参考文献的格式遵循着作者、文章标题、期刊名、出版日期和页码等信息的排列顺序。

下面是一些常见的参考文献格式示例:
期刊文章:
英文格式,Author(s). (Year). Title of article. Title of Journal, volume number(issue number), page range.
中文格式,作者. (年份). 文章标题. 期刊名称, 卷号(期号), 页码范围。

书籍:
英文格式,Author(s). (Year). Title of book. Publisher.
中文格式,作者. (年份). 书名. 出版社。

网页:
英文格式,Author(s). (Year). Title of webpage. Site name. URL (Accessed date).
中文格式,作者. (年份). 网页标题. 网站名称. 网址 (访问日期)。

这只是一些常见的引用格式示例,具体的要求可能会因期刊或学术机构的要求而有所不同。

在撰写学术论文或提交文章时,最好参考目标期刊的官方引用格式指南,以确保引用格式符合要求。

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

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

外文翻译要求: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.非线形模型钢筋和后张法预应力混凝土梁摘要:商业有限元软件一般包括混凝土在荷载做用下非线性反应的专用数值模型。

英语参考文献格式(英文版)

英语参考文献格式(英文版)



*、作者编者不详的书籍
• • 格式:
书名 (□□版.). (出版年). 出版城市, 州别简称:
出版者.
• •
范例:
Merriam-Webster’s collegiate dictionary (10th ed.). (1993)
Springfield, MA:
Merriam Webster.
Beyond redlining: Editing software that works. Poster session
七、电子网路资料
(一)电子期刊: 1. 电子版与纸本版并行之期刊:应注明电子版或 Electronic version 及页码 • 格式: • 作者(出版年)。文章名称﹝电子版﹞。期刊名 称,卷,页码。 • 范例: • 金成隆(2002)。生产科技对财务报表质量影响 之研究﹝电子版﹞。企业管理学报,54, 33-51。 • VandenBos, G., Knapp, S., & Doe, J. (2001). Role of reference elements in the selection of resources by psychology undergraduates [Electronic version]. Journal of Bibliographic Research, 5, 117-123.
• After the author(s) comes the year of publication, in parentheses and followed by a period. • Capitalize only the first letter of the first word of a title and subtitle (if any), and any proper names within a title. • The first line of the entry is flush left; hanging indents are applied starting with the second line of each reference with about 4 spaces indented. • APA 格式不采用文献编号的方式排列,

外文译文(格式要求)

外文译文(格式要求)

外文文献译文格式如下文献题目上角标(上角标以脚注形式给出原文的文献来源,文献来源标注请注意按照指导手册中关于参考文献的要求列出,必须真实可查)原文作者姓名(英文)译者姓名包括信息(班级学号姓名 [译])(译文正文)一、************(一级标题)(一)***********(二级标题)……注意:尽量保持译文完整,整篇翻译(包括摘要、关键词等),如有省略,请译出标题后加(略),中间内容可部分省略,但是结论最好要译出,此外文末有参考文献的译出参考文献字样,后面加(略)。

译文正文的格式要求同论文正文的格式,包括字体,行间距,页边距,图表等所有格式,详见指导手册。

黑色字体为格式说明项,红色字体为需要的信息。

所有文中所出现的序号请按照指导手册要求修改,例如一、()一……等。

外文原文的打印可以直接原文打印,若原文太长,可转换为word打印所译内容,其他省略翻译的列上标题后写略。

原文打印可不必再写文献来源,只需在打印的原文第一页上方空白处按序写上“班级学号姓名”等信息。

转换为word打印的,需按照指导手册要求调整好打印格式,并在标题后以脚注形式标注原文来源信息(指导手册要求)。

在打印的word原文第一页上方空白处写上“班级学号姓名”等信息(此时不需加[译]的字样)。

所有打印文件页脚上注意自动生成页码(如译文范文)。

定稿时发送的文件名称改成(专业班级学号姓名-外文原文)。

若是译文的话则文件名为(专业班级学号姓名-外文译文)。

其他文件定稿时也是这个要求。

范文:(见下一页)韩国**对经济影响的分析①原作者名可直接用英文经济学 061*班 2006*****6 张三[译][摘要] 本文研究的目的*******的影响。

在探讨*****影响各行业的产出、就业、收入、增值和进口中应用了投入产出模型。

*******************。

根据研究的结果,得出结论*********的作用。

[关键词] ***** 投入-产出模型 **效应 **效应一、引言在当今经济全球化***************。

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

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

杭州电子科技大学信息工程学院毕业论文外文文献翻译要求根据《普通高等学校本科毕业设计(论文)指导》的内容,特对外文文献翻译提出以下要求:一、翻译的外文文献可以是一篇,也可以是两篇,但总字符要求不少于1.5万(或翻译成中文后至少在3000字以上)。

二、翻译的外文文献应主要选自学术期刊、学术会议的文章、有关著作及其他相关材料,应与毕业论文(设计)主题相关,并作为外文参考文献列入毕业论文(设计)的参考文献。

并在每篇中文译文首页用“脚注”形式注明原文作者及出处,中文译文后应附外文原文。

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

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

四、封面格式由学校统一制作(注:封面上的“翻译题目”指中文译文的题目),并按“封面、译文一、外文原文一、译文二、外文原文二、考核表”的顺序统一装订。

五、忌自行更改表格样式。

毕业论文外文文献翻译毕业设计(论文)题目Xxx翻译(1)题目指翻译后的中文译文的题目翻译(2)题目指翻译后的中文译文的题目系会计系以本模板为准)专业XXXXXX(以本模板为准)姓名XXXXXX(以本模板为准)班级XXXXXX(以本模板为准)学号XXXXXX(以本模板为准)指导教师XXXXXX(以本模板为准)正文指导教师对外文翻译的评语:指导教师(签名)年月日建议成绩(百分制)评阅小组或评阅人对外文翻译的评语:评阅小组负责人或评阅人(签名)年月日建议成绩(百分制)杭州电子科技大学信息工程学院本科毕业论文文献综述的写作要求为了促使学生熟悉更多的专业文献资料,进一步强化学生搜集文献资料的能力,提高对文献资料的归纳、分析、综合运用能力及独立开展科研活动的能力,现对本科学生的毕业设计(论文)提出文献综述的写作要求,具体要求如下:一、文献综述的概念文献综述是针对某一研究领域或专题搜集大量文献资料的基础上,就国内外在该领域或专题的主要研究成果、最新进展、研究动态、前沿问题等进行综合分析而写成的、能比较全面地反映相关领域或专题历史背景、前人工作、争论焦点、研究现状和发展前景等内容的综述性文章。

外文参考文献的格式

外文参考文献的格式

外文参考文献的格式篇一:英语论文参考文献格式用Times New Roman。

每一条目顶格, 如某一条目超过一行,从第二行起“悬挂缩进”2字符。

参考文献中所有标点与符号均在英文状态下输入,标点符号后空一格。

参考文献条目排列顺序:英文文献、中文文献、网络文献。

分别按作者姓氏字母顺序排列。

文献前不用序号。

1)英文参考文献(1)专著与编著排列顺序为:作者姓、名、专著名、出版地、出版社、出版年。

例如:Brinkleyork: Knopf, 1993.专著名中如果还包含其他著作或作品名,后者用斜体。

例如:Dunn, Richard J ed. Charlotte Bront?: Jane EyreNew York: Norton, 1971.A.两个至三个作者第一作者的姓在前,名在后,中间用逗号隔开;其余作者名在前,姓在后,中间无逗号;每个作者之间用逗号隔开,最后一个作者的姓名前用“and”,后用句号。

例如:B. 三个以上作者第一作者姓名(姓在前,名在后,中间加逗号)后接“et al.”,其他作者姓名省略。

例如:University of Hawaii Press, 1997.C. 同一作者同一年出版的不同文献,参照下例:Widdowson, Hey G1998a.Widdowson, Hey G. Cambridge:Cambridge University Press, 1998b.(2)论文集参照下例:Thompson, Pett. “Modal Verbs in Academic Writing”. In Ben Kettlemann & York: Rodopi, 2019: 305-323.(3)百科全书等参考文献参照下例:Fagan, Jeffrey. “Gangs and Drugs”. ork: Macmillan, 2019.(4)学术期刊论文参照下例:Murphy, Karen. “Meaningful Connections: Using Technology in PrimaryClassrooms”.(5)网络文献参照下例:----“Everything You Ever Wanted to Know About URL”..2)中文参考文献(1)专著参照下例:皮亚杰.结构主义[M] .北京:商务印书馆,1984.(2)期刊文章参照下例:杨忠,张韶杰.认知语音学中的类典型论[J] .外语教学与研究,1999,(2):1-3.(3)学位论文参照下例:梁佳.大学英语四、六级测试试题现状的理论分析与问题研究[D] .湖南大学,2019.(4)论文集参照下例:许小纯.含义和话语结构[A].李红儒.外国语言与文学研究[C] .哈尔滨:黑龙江人民出版社,1999:5-7.(5)附录篇二:中英文参考文献格式中文参考文献格式参考文献(即引文出处)的类型以单字母方式标识:M——专著,C——论文集,N——报纸文章,J——期刊文章,D——学位论文,R——报告,S——标准,P——专利;对于不属于上述的文献类型,采用字母“Z”标识。

  1. 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
  2. 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
  3. 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。

外文参考文献及翻译稿的要求及格式
一、外文参考文献的要求
1、外文原稿应与本研究项目接近或相关联;
2、外文原稿可选择相关文章或节选章节,正文字数不少于1500字。

3、格式:外文文献左上角标注“外文参考资料”字样,小四宋体。

1.5倍行距。

标题:三号,Times New Roman字体加粗,居中,行距1.5倍。

段前段后空一行。

作者(居中)及正文:小四号,Times New Roman字体,首行空2字符。

4、A4纸统一打印。

二、中文翻译稿
1、中文翻译稿要与外文文献匹配,翻译要正确;
2、中文翻译稿另起一页;
3、格式:左上角标“中文译文”,小四宋体。

标题:宋体三号加粗居中,行距1.5倍。

段前、段后空一行。

作者(居中)及正文:小四号宋体,数字等Times New Roman字体,1.5倍行距,首行空2字符。

正文字数1500左右。

4、A4纸统一打印。

格式范例如后所示。

medium-sized pow er
Stephen Ryan internal control system execution ability and dynamics, it is the one whole set behavior and the technical system, is unique competitive advantage which the enterprise has; Is a series of ……
……
……
…………
中文译文
史蒂芬.为和技术体系,是企业所具有的独特竞争优势;是一系列价值准则、行为规范、运行模式、制度体系、技术支撑。

长期以来,执行力一直为许多企业所忽视。

《财富》杂志调查结论:“只有
10%的有效战略得到了有效执行;70%企业失败的原因不是因为缺乏好的战略,而是缺乏有效的执行。

”内部控制同样如此:许多企业并不缺乏内部控制制度,只是执行力度太差,导致控制无效。

中小企业内部控制执行力相对更为薄弱。

因此,研究中小企业内部控制必须关注其执行力。

......
......
(摘自XXX。

相关文档
最新文档