2021年毕业设计论文外文文献翻译要求及封面

合集下载

毕业设计(论文)文献翻译封面

重庆理工大学文献翻译二级学院应用技术学院班级108217401学生姓名谢靖学号40译文要求1译文内容Leabharlann 须与课题或专业内容相关并需注明详细出处
重庆理工大学
文献翻译
二级学院应用技术学院
班级108217401
学生姓名谢靖学号40
译文要求
1、译文内容必须与课题（或专业）内容相关，并需注明详细出处。
2、外文翻译不少于1万外文字符；外文参考资料阅读量至少3篇（相当于10万外文字符以上）。
3、译文原文（或复印件）应附在译文后备查。
译文评阅
导师评语（应根据学校“译文要求”，对学生外文翻译的准确性、翻译数量以及译文的文字表述情况等作具体的评价）
（要求手写）
指导教师：
年月日

2021年毕业设计论文开题报告及英文翻译撰写要求

毕业设计论文开题报告及英文翻译撰写要求
毕业设计（论文）开题报告及英文翻译撰写要求
毕业设计(论文)撰写要求：
1.开题报告的主要内容
1)所选课题国内、外研究及发展状况
2)课题研究的目的和意义;
3)课题研究的`主要内容、难点及关键技术;
4)研究方法及技术途径;
5)实施计划。

2.主要：不少于5篇，其中外文文献不少于1篇。

3.开题报告的字数不少于3000字，格式按《华中科技大学武昌分校本科毕业设计(论文)撰写规范》的要求撰写。

4.开题报告单独装订，本附件为封面。

毕业设计(论文)外文文献翻译要求：
1.外文文献翻译的内容应与毕业设计(论文)课题相关。

2.外文文献翻译的字数：艺术类专业不少于2000汉字，其他专业不少于5000汉字，格式按《华中科技大学武昌分校本科毕业设计(论文)撰写规范》的要求撰写。

3.外文文献翻译单独装订：第1部分为译文，第2部分为外文文献原文，本附件为封面。

模板,内容仅供参考。

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

外文翻译规范要求及模版格式
外文中文翻译规范要求及模板格式可以根据具体需求和要求有所不同，以下是一般常见的外文中文翻译规范要求及模板格式：
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的布局文件。

3-外文翻译模板格式及要求

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

二、翻译的外文文献应主要选自学术期刊、学术会议的文章、有关著作及其他相关材料，文献作者最好为国外的专家或学者；应与毕业论文（设计）主题相关，并作为外文参考文献列入毕业论文（设计）的参考文献。

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

脚注的方法：插入----引用---脚注和尾注三、中文译文的基本撰写格式为：1.题目:采用小三号、黑体字、居中打印，段前段后1行间距；；2.正文:采用小四号、宋体字，行间距为固定值20磅，标准字符间距。

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

英文原文如为word文档，请用罗马字体排版，段前空两格，段间距20磅。

页眉为“杭州电子科技大学本科毕业论文外文翻译”，5号宋体字从正文开始编写页码，页码居中。

四、封面格式由学校统一制作（注：封面上的“翻译题目”指中文译文的题目），填充内容为加粗小三号楷体_GB2312，并按“封面、译文一、外文原文一、译文二、外文原文二、考核表”的顺序统一装订。

五、忌自行更改表格样式，学号请写完整。

封面和考核表均为一页纸张，勿换行换页。

注意：1.除了封面和考核表之外，外文翻译有页眉和页码。

2.外文翻译中各级标题统一为段前空两格；若标题无序号，也可按与原文一致的原则处理。

题目段前段后1行一级标题小四宋体加黑，段前段后0.5行其他各级标题段前空两格，小四宋体不加黑，其他与正文要求一致。

毕业论文外文文献翻译毕业设计（论文）题目Xxx（单击此处添加论文题目）翻译（1）题目指翻译后的第一篇中文译文的题目翻译（2）题目指翻译后的第二篇中文译文的题目若无，则本栏留空学院经贸学院专业国际经济与贸易（单击此处添加专业）姓名XXXXXX（单击此处添加姓名）班级XX020811（单击此处添加班级）学号XX023101（单击此处添加班级）指导教师XXXXXX（单击此处添加指导教师）单击此处添加翻译后的第一篇中文译文的题目1 [单击此处添加译文正文]一、单击此处添加一级标题1[单击此处添加译文正文]1.[单击此处添加译文正文]2.[单击此处添加译文正文]3.[单击此处添加译文正文]二、单击此处添加一级标题2[单击此处添加译文正文]1.[单击此处添加译文正文]2.[单击此处添加译文正文]3.[单击此处添加译文正文]三、单击此处添加一级标题3……………………………以下是模板的使用方法说明文字，正式成文后请删除。

毕业设计论文中英文翻译要求

毕业设计论文中英文翻译要求Graduation Thesis Translation RequirementsEnglish translation of Graduation Thesis:1. Accuracy: The English translation of the Graduation Thesis should accurately reflect the content and meaning of the original Chinese text. It should convey the same ideas and arguments as presented in the original text.2. Clarity: The translation should be clear and easy to understand. The language used should be appropriate and the sentences should be well-structured.3. Grammar and Syntax: The translation should follow the rules of English grammar and syntax. There should be no grammatical errors or awkward sentence constructions.4. Vocabulary: The translation should make use of appropriate vocabulary that is relevant to the topic of the Graduation Thesis. Technical terms and concepts should be accurately translated.5. Style: The translation should maintain the academic style and tone of the original Chinese text. It should use formal language and avoid colloquial or informal expressions.6. References: If the Graduation Thesis includes citations or references, the English translation should accurately reflectthese citations and references. The formatting of citations and references should follow the appropriate style guide.7. Proofreading: The English translation should be thoroughly proofread to ensure there are no spelling or punctuation errors. It should also be reviewed for any inconsistencies or inaccuracies.Minimum word count: The English translation of the Graduation Thesis should be at least 1200 words. This requirement ensures that the translation adequately captures the main points and arguments of the original text.It is important to note that there may be specific guidelines or requirements provided by your academic institution or supervisor for the translation of your Graduation Thesis. Please consult these guidelines and follow them accordingly.。

外文文献翻译要求及封面

根据《普通高等学校本科毕业设计（论文）指导》地内容，特对外文文献翻译提出以下要求：
一、翻译地外文文献一般为～篇，外文字符要求不少于万（或翻译成中文后至少在字以上）.
二、翻译地外文文献应主要选自学术期刊、学术会议地文章、有关著作及其他相关材料，应与毕业论文（设计）主题相关，并作为外文参考文献列入毕业论文（设计）地参考文献.并在每篇中文译文首页用“脚注”形式注明原文作者及出处，中文译文后应附外文原文.个人收集整理勿做商业用途
三、中文译文地基本撰写格式为题目采用小三号黑体字居中打印，正文采用宋体小四号字，行间距一般为固定值磅，标准字符间距.页边距为左，右，上下各，页面统一采用纸.个人收集整理勿做商业用途
四、封面格式由学校统一制作（注：封面上地“翻译题目”指中文译文地题目，附件为一篇外文翻译地封面格式，附件二为两篇外文翻译地封面格式），若有两篇外文文献，请按“封面、译文一、外文原文一、译文二、外文原文二”地顺序统一装订.个人收集整理勿做商业用途
信息工程学院教科办
年月日
杭州电子科技大学信息工程学院
毕业设计（论文）外文文献翻译
毕业设计（论文）题
目
翻译题目
系
专业
姓名
班级
学号
指导教师
杭州电子科技大学信息工程学院毕业设计（论文）外文文献翻译
毕业设计（论文）题
目
翻译（）题目
翻译（）题目
系
专业
姓名
班级
学号
指导教师。

本科生英文文献翻译格式要求

外文文献翻译格式要求：外文文献翻译是本科生毕业的过程之一，有些格式需要我们注意一下。

（1）摘要，关键词：宋体五号（其中“摘要”和“关键词”为宋体五号加粗），行间距设置为18磅，段前段后间距设置为行，对齐方式选择“两端对齐”方式；各个关键词之间以分号（；）或者（，）隔开，最后一个关键词后不加标点；（2）正文一级标题：采用黑体小三号加粗，行间距设置为20磅，段前段后间距设置为行，一般采用“1 引言”样式，其中1和“引言”之间用一个空格分开；正文二级标题：采用黑体小三号，行间距设置为20磅，段前段后间距设置为行，一般采用“系统原理”样式，其中1和“系统原理”之间用一个空格分开；；一级标题和二级标题采用“左对齐”方式；（3）正文内容：采用宋体小四号，行间距设置为20磅，段前段后间距设置为0行，首行缩进2字符，正文对齐方式在段落格式设置中选择“两端对齐”，遇正文中有公式的，设置该行（段）行间距为“单倍行距”（4）插图：请设置图片版式为“浮于文字上方”，并勾选“居中”，图片大小根据版面，按比例适当进行缩放，图示说明采用“图 1 主控制器的结构图”样式置于图下，图序与说明以一个空格字符间隔，图示说明采用宋体五号，居中对齐，行间距设置为“单倍行距”，段前段后距设置为行；（5）表格：在表格属性中选择“居中”对齐方式，表格说明采用“表1 两种方法试验数据比较”样式置于表格上方，表序与说明以一个空格字符间隔，表格说明采用宋体五号，居中对齐，行间距设置为“单倍行距”，段前段后距设置为行；（6）参考文献：“参考文献”格式同一级标题格式，参考文献内容采用宋体五号，行间距设置为18磅，段前段后间距设置为0行，对齐方式选择“左对齐”方式，其中出现的标点一律采用英文标点；以上摘要，关键词，正文，标题及参考文献中出现的英文字符和数字，一律设置为“Times New Roman”字体。

外文文献翻译附于开题报告之后：第一部分为译文，第二部分为外文文献原文，译文与原文均需单独编制页码（底端居中）并注明出处。

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

外文翻译规范要求及模版格式
外文中文翻译规范要求及模板格式可以根据不同的需求和行业标准而有所不同。

以下是一些常见的外文中文翻译规范要求及模板格式的建议：1.规范要求：
-准确性和完整性：翻译应准确无误地传达原文的意思，并尽可能保持原文的完整性。

-语法和拼写：翻译应符合中文语法和拼写规范，避免使用口语化或地方性的表达方式。

-文化适应性：翻译应根据目标读者的背景和文化习俗进行适当增删或修改，以确保易于理解。

-确保一致性：在同一文档中，相同的术语和表达应保持一致，以避免混淆和歧义。

2.模板格式：
-标题：可以使用与原文相同或相似的标题格式，并在括号中注明翻译为中文。

-段落和换行：根据原文的段落结构进行适当的调整，并在新段落前留出空行。

-标点符号：根据中文标点符号使用习惯进行调整，保持句子的结构和逻辑清晰。

-术语和专业名词：对于特定的术语和专业名词，可以在括号或脚注中提供更详细的解释或注释。

-引用和注释：如有必要，可以在翻译中包含引用和注释，以提供更多的背景信息和解释。

此外，根据具体需求，还可以根据公司或机构的翻译要求进行格式调整，例如使用特定的字体、字号、页边距等。

因此，在进行外文中文翻译之前，最好与相关方沟通明确具体的规范要求。

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

东北大学东软信息学院外文资料和译文格式要求一、译文必须采用计算机输入、打印，幅面A4。

外文资料原文（复印或打印）在前，译文在后，于左侧装订。

二、具体要求1、至少翻译一篇内容与所选课题相关的外文文献。

2、译文汉字字数不少于4000字。

3、正文格式要求：宋体五号字。

附：外文资料和译文封面、空白页外文资料和译文专业：班级：姓名：学号：指导教师：2010年12月23日5.2.5. Read/Write Spin LocksRead/write spin locks have been introduced to increase the amount of concurrency inside the kernel. They allow several kernel control paths to simultaneously read the same data structure, as long as no kernel control path modifies it. If a kernel control path wishes to write to the structure, it must acquire the write version of the read/write lock, which grants exclusive access to the resource. Of course, allowing concurrent reads on data structures improves system performance.Figure 5-2 illustrates two critical regions (C1 and C2) protected by read/write locks. Kernel control paths R0 and R1 are reading the data structures in C1 at the same time, while W0 is waiting to acquire the lock for writing. Kernel control path W1 is writing the data structures inC2, while both R2 and W2 are waiting to acquire the lock for reading and writing, respectively.Figure 5-2. Read/write spin locksEach read/write spin lock is a rwlock_t structure; its lock field is a 32-bit field that encodes two distinct pieces of information:∙ A 24-bit counter denoting the number of kernel control paths currently reading the protected data structure. The two's complement value of this counter is stored in bits 023 of the field.∙An unlock flag that is set when no kernel control path is reading or writing, and clear otherwise. This unlock flag is stored in bit 24 of the field.Notice that the lock field stores the number 0x01000000 if the spin lock is idle (unlock flag set and no readers), the number 0x00000000 if it has been acquired for writing (unlock flag clear and no readers), and any number in the sequence 0x00ffffff, 0x00fffffe, and so on, if it has been acquired for reading by one, two, or more processes (unlock flag clear and the two's complement on 24 bits of the number of readers). As the spinlock_t structure, the rwlock_t structure also includes a break_lock field.The rwlock_init macro initializes the lock field of a read/write spin lock to 0x01000000 (unlocked) and the break_lock field to zero.5.2.5.1. Getting and releasing a lock for readingThe read_lock macro, applied to the address rwlp of a read/write spin lock, is similar to thespin_lock macro described in the previous section. If the kernel preemption option has been selected when the kernel was compiled, the macro performs the very same actions as those of spin_lock( ), with just one exception: to effectively acquire the read/write spin lock in step 2, the macro executes the _raw_read_trylock( ) function:int _raw_read_trylock(rwlock_t *lock){atomic_t *count = (atomic_t *)lock->lock;atomic_dec(count);if (atomic_read(count) >= 0)return 1;atomic_inc(count);return 0;}The lock fieldthe read/write lock counteris accessed by means of atomic operations. Notice, however, that the whole function does not act atomically on the counter: for instance, the counter might change after having tested its value with the if statement and before returning 1. Nevertheless, the function works properly: in fact, the function returns 1 only if the counter was not zero or negative before the decrement, because the counter is equal to 0x01000000 for no owner, 0x00ffffff for one reader, and 0x00000000 for one writer.If the kernel preemption option has not been selected when the kernel was compiled, theread_lock macro yields the following assembly language code:movl $rwlp->lock,%eaxlock; subl $1,(%eax)jns 1fcall _ _read_lock_failed1:where _ _read_lock_failed( ) is the following assembly language function:_ _read_lock_failed:lock; incl (%eax)1: pausecmpl $1,(%eax)js 1block; decl (%eax)js _ _read_lock_failedretThe read_lock macro atomically decreases the spin lock value by 1, thus increasing the number of readers. The spin lock is acquired if the decrement operation yields a nonnegative value; otherwise, the _ _read_lock_failed( ) function is invoked. The function atomically increases the lock field to undo the decrement operation performed by the read_lock macro, and then loops until the field becomes positive (greater than or equal to 1). Next, _ _read_lock_failed( ) tries to get the spin lock again (another kernel control path could acquire the spin lock for writing right after the cmpl instruction).Releasing the read lock is quite simple, because the read_unlock macro must simply increase the counter in the lock field with the assembly language instruction:lock; incl rwlp->lockto decrease the number of readers, and then invoke preempt_enable( ) to reenable kernel preemption.5.2.5.2. Getting and releasing a lock for writingThe write_lock macro is implemented in the same way as spin_lock( ) andread_lock( ). For instance, if kernel preemption is supported, the function disables kernel preemption and tries to grab the lock right away by invoking_raw_write_trylock( ). If this function returns 0, the lock was already taken, thus the macro reenables kernel preemption and starts a busy wait loop, as explained in the description of spin_lock( ) in the previous section.The _raw_write_trylock( ) function is shown below:int _raw_write_trylock(rwlock_t *lock){atomic_t *count = (atomic_t *)lock->lock;if (atomic_sub_and_test(0x01000000, count))return 1;atomic_add(0x01000000, count);return 0;}The _raw_write_trylock( ) function subtracts 0x01000000 from the read/write spin lock value, thus clearing the unlock flag (bit 24). If the subtraction operation yieldszero (no readers), the lock is acquired and the function returns 1; otherwise, the function atomically adds 0x01000000 to the spin lock value to undo the subtraction operation.Once again, releasing the write lock is much simpler because the write_unlock macro must simply set the unlock flag in the lock field with the assembly language instruction:lock; addl $0x01000000,rwlpand then invoke preempt_enable().5.2.6. SeqlocksWhen using read/write spin locks, requests issued by kernel control paths to perform a read_lock or a write_lock operation have the same priority: readers must wait until the writer has finished and, similarly, a writer must wait until all readers have finished.Seqlocks introduced in Linux 2.6 are similar to read/write spin locks, except that they give a much higher priority to writers: in fact a writer is allowed to proceed even when readers are active. The good part of this strategy is that a writer never waits (unless another writer is active); the bad part is that a reader may sometimes be forced to read the same data several times until it gets a valid copy.Each seqlock is a seqlock_t structure consisting of two fields: a lock field of type spinlock_t and an integer sequence field. This second field plays the role of a sequence counter. Each reader must read this sequence counter twice, before and after reading the data, and check whether the two values coincide. In the opposite case, a new writer has become active and has increased the sequence counter, thus implicitly telling the reader that the data just read is not valid.A seqlock_t variable is initialized to "unlocked" either by assigning to it the value SEQLOCK_UNLOCKED, or by executing the seqlock_init macro. Writers acquire and release a seqlock by invoking write_seqlock( ) and write_sequnlock( ). The first function acquires the spin lock in the seqlock_t data structure, then increases the sequence counter by one; the second function increases the sequence counter once more, then releases the spin lock. This ensures that when the writer is in the middle of writing, the counter is odd, and that when no writer is altering data, the counter is even. Readers implement a critical region as follows:unsigned int seq;do {seq = read_seqbegin(&seqlock);/* ... CRITICAL REGION ... */} while (read_seqretry(&seqlock, seq));read_seqbegin() returns the current sequence number of the seqlock; read_seqretry() returns 1 if either the value of the seq local variable is odd (a writer was updating the data structure when the read_seqbegin( ) function has been invoked), or if the value of seq does not match the current value of the seqlock's sequence counter (a writer started working while the reader was still executing the code in the critical region).Notice that when a reader enters a critical region, it does not need to disable kernel preemption; on the other hand, the writer automatically disables kernel preemption when entering the critical region, because it acquires the spin lock.Not every kind of data structure can be protected by a seqlock. As a general rule, the following conditions must hold:∙The data structure to be protected does not include pointers that are modified by the writers and dereferenced by the readers (otherwise, a writer couldchange the pointer under the nose of the readers)∙The code in the critical regions of the readers does not have side effects (otherwise, multiple reads would have different effects from a single read) Furthermore, the critical regions of the readers should be short and writers should seldom acquire the seqlock, otherwise repeated read accesses would cause a severe overhead. A typical usage of seqlocks in Linux 2.6 consists of protecting some data structures related to the system time handling (see Chapter 6).5.2.7. Read-Copy Update (RCU)Read-copy update (RCU) is yet another synchronization technique designed to protect data structures that are mostly accessed for reading by several CPUs. RCU allows many readers and many writers to proceed concurrently (an improvement over seqlocks, which allow only one writer to proceed). Moreover, RCU is lock-free, that is, it uses no lock or counter shared by all CPUs; this is a great advantage over read/write spin locks and seqlocks, which have a high overhead due to cache line-snooping and invalidation.How does RCU obtain the surprising result of synchronizing several CPUs without shared data structures? The key idea consists of limiting the scope of RCU as follows:1.Only data structures that are dynamically allocated and referenced by meansof pointers can be protected by RCU.2.No kernel control path can sleep inside a critical region protected by RCU.When a kernel control path wants to read an RCU-protected data structure, it executes the rcu_read_lock( ) macro, which is equivalent to preempt_disable( ). Next, the reader dereferences the pointer to the data structure and starts reading it. As stated above, the reader cannot sleep until it finishes reading the data structure; the end of the critical region is marked by the rcu_read_unlock( ) macro, which is equivalent to preempt_enable( ).Because the reader does very little to prevent race conditions, we could expect that the writer has to work a bit more. In fact, when a writer wants to update the data structure, it dereferences the pointer and makes a copy of the whole data structure. Next, the writer modifies the copy. Once finished, the writer changes the pointer to the data structure so as to make it point to the updated copy. Because changing the value of the pointer is an atomic operation, each reader or writer sees either the old copy or the new one: no corruption in the data structure may occur. However, a memory barrier is required to ensure that the updated pointer is seen by the other CPUs only after the data structure has been modified. Such a memory barrier is implicitly introduced if a spin lock is coupled with RCU to forbid the concurrent execution of writers.The real problem with the RCU technique, however, is that the old copy of the data structure cannot be freed right away when the writer updates the pointer. In fact, the readers that were accessing the data structure when the writer started its update could still be reading the old copy. The old copy can be freed only after all (potential) readers on the CPUs have executed the rcu_read_unlock( ) macro. The kernel requires every potential reader to execute that macro before:∙The CPU performs a process switch (see restriction 2 earlier).∙The CPU starts executing in User Mode.∙The CPU executes the idle loop (see the section "Kernel Threads" in Chapter 3).In each of these cases, we say that the CPU has gone through a quiescent state.The call_rcu( ) function is invoked by the writer to get rid of the old copy of the data structure. It receives as its parameters the address of an rcu_head descriptor (usually embedded inside the data structure to be freed) and the address of a callback function to be invoked when all CPUs have gone through a quiescent state. Once executed, the callback function usually frees the old copy of the data structure.The call_rcu( ) function stores in the rcu_head descriptor the address of the callback and its parameter, then inserts the descriptor in a per-CPU list of callbacks. Periodically, once every tick (see the section "Updating Local CPU Statistics" in Chapter 6), the kernel checks whether the local CPU has gone through a quiescent state. When all CPUs have gone through a quiescent state, a local taskletwhose descriptor is stored in the rcu_tasklet per-CPU variableexecutes all callbacks in the list.RCU is a new addition in Linux 2.6; it is used in the networking layer and in the Virtual Filesystem.5.2.8. SemaphoresWe have already introduced semaphores in the section "Synchronization and Critical Regions" in Chapter 1. Essentially, they implement a locking primitive that allows waiters to sleep until the desired resource becomes free.Actually, Linux offers two kinds of semaphores:∙Kernel semaphores, which are used by kernel control paths∙System V IPC semaphores, which are used by User Mode processesIn this section, we focus on kernel semaphores, while IPC semaphores are described in Chapter 19.A kernel semaphore is similar to a spin lock, in that it doesn't allow a kernel control path to proceed unless the lock is open. However, whenever a kernel control path tries to acquire a busy resource protected by a kernel semaphore, the corresponding process is suspended. It becomes runnable again when the resource is released. Therefore, kernel semaphores can be acquired only by functions that are allowed to sleep; interrupt handlers and deferrable functions cannot use them.A kernel semaphore is an object of type struct semaphore, containing the fields shown in the following list.countStores an atomic_t value. If it is greater than 0, the resource is free that is, itis currently available. If count is equal to 0, the semaphore is busy but noother process is waiting for the protected resource. Finally, if count isnegative, the resource is unavailable and at least one process is waiting for it.waitStores the address of a wait queue list that includes all sleeping processes that are currently waiting for the resource. Of course, if count is greater than orequal to 0, the wait queue is empty.sleepersStores a flag that indicates whether some processes are sleeping on thesemaphore. We'll see this field in operation soon.The init_MUTEX( ) and init_MUTEX_LOCKED( ) functions may be used to initialize a semaphore for exclusive access: they set the count field to 1 (free resource with exclusive access) and 0 (busy resource with exclusive access currently granted to the process that initializes the semaphore), respectively. The DECLARE_MUTEX and DECLARE_MUTEX_LOCKED macros do the same, but they also statically allocate the struct semaphore variable. Note that a semaphore could also be initialized with an arbitrary positive value n for count. In this case, at most n processes are allowed to concurrently access the resource.5.2.8.1. Getting and releasing semaphoresLet's start by discussing how to release a semaphore, which is much simpler than getting one. When a process wishes to release a kernel semaphore lock, it invokes the up( ) function. This function is essentially equivalent to the following assembly language fragment:movl $sem->count,%ecxlock; incl (%ecx)jg 1flea %ecx,%eaxpushl %edxpushl %ecxcall _ _uppopl %ecxpopl %edx1:where _ _up( ) is the following C function:__attribute__((regparm(3))) void _ _up(struct semaphore *sem){wake_up(&sem->wait);}The up( ) function increases the count field of the *sem semaphore, and then it checks whether its value is greater than 0. The increment of count and the setting of the flag tested by the following jump instruction must be atomically executed, or else another kernel control path could concurrently access the field value, with disastrousresults. If count is greater than 0, there was no process sleeping in the wait queue, so nothing has to be done. Otherwise, the _ _up( ) function is invoked so that one sleeping process is woken up. Notice that _ _up( ) receives its parameter from the eax register (see the description of the _ _switch_to( ) function in the section "Performing the Process Switch" in Chapter 3).Conversely, when a process wishes to acquire a kernel semaphore lock, it invokes the down( ) function. The implementation of down( ) is quite involved, but it is essentially equivalent to the following:down:movl $sem->count,%ecxlock; decl (%ecx);jns 1flea %ecx, %eaxpushl %edxpushl %ecxcall _ _downpopl %ecxpopl %edx1:where _ _down( ) is the following C function:__attribute__((regparm(3))) void _ _down(struct semaphore * sem){DECLARE_WAITQUEUE(wait, current);unsigned long flags;current->state = TASK_UNINTERRUPTIBLE;spin_lock_irqsave(&sem->wait.lock, flags);add_wait_queue_exclusive_locked(&sem->wait, &wait);sem->sleepers++;for (;;) {if (!atomic_add_negative(sem->sleepers-1, &sem->count)) {sem->sleepers = 0;break;}sem->sleepers = 1;spin_unlock_irqrestore(&sem->wait.lock, flags);schedule( );spin_lock_irqsave(&sem->wait.lock, flags);current->state = TASK_UNINTERRUPTIBLE;}remove_wait_queue_locked(&sem->wait, &wait);wake_up_locked(&sem->wait);spin_unlock_irqrestore(&sem->wait.lock, flags);current->state = TASK_RUNNING;}The down( ) function decreases the count field of the *sem semaphore, and then checks whether its value is negative. Again, the decrement and the test must be atomically executed. If count is greater than or equal to 0, the current process acquires the resource and the execution continues normally. Otherwise, count is negative, and the current process must be suspended. The contents of some registers are saved on the stack, and then _ _down( ) is invoked.Essentially, the _ _down( ) function changes the state of the current process from TASK_RUNNING to TASK_UNINTERRUPTIBLE, and it puts the process in the semaphore wait queue. Before accessing the fields of the semaphore structure, the function also gets the sem->wait.lock spin lock that protects the semaphore wait queue (see "How Processes Are Organized" in Chapter 3) and disables local interrupts. Usually, wait queue functions get and release the wait queue spin lock as necessary when inserting and deleting an element. The _ _down( ) function, however, uses the wait queue spin lock also to protect the other fields of the semaphore data structure, so that no process running on another CPU is able to read or modify them. To that end, _ _down( ) uses the "_locked" versions of the wait queue functions, which assume that the spin lock has been already acquired before their invocations.The main task of the _ _down( ) function is to suspend the current process until the semaphore is released. However, the way in which this is done is quite involved. To easily understand the code, keep in mind that the sleepers field of the semaphore is usually set to 0 if no process is sleeping in the wait queue of the semaphore, and it is set to 1 otherwise. Let's try to explain the code by considering a few typical cases. MUTEX semaphore open (count equal to 1, sleepers equal to 0)The down macro just sets the count field to 0 and jumps to the nextinstruction of the main program; therefore, the _ _down( ) function is notexecuted at all.MUTEX semaphore closed, no sleeping processes (count equal to 0, sleepers equal to 0)The down macro decreases count and invokes the _ _down( ) function withthe count field set to -1 and the sleepers field set to 0. In each iteration of theloop, the function checks whether the count field is negative. (Observe thatthe count field is not changed by atomic_add_negative( ) because sleepers isequal to 0 when the function is invoked.)∙If the count field is negative, the function invokes schedule( ) tosuspend the current process. The count field is still set to -1, and thesleepers field to 1. The process picks up its run subsequently insidethis loop and issues the test again.∙If the count field is not negative, the function sets sleepers to 0 and exits from the loop. It tries to wake up another process in thesemaphore wait queue (but in our scenario, the queue is now empty)and terminates holding the semaphore. On exit, both the count fieldand the sleepers field are set to 0, as required when the semaphore isclosed but no process is waiting for it.MUTEX semaphore closed, other sleeping processes (count equal to -1, sleepers equal to 1)The down macro decreases count and invokes the _ _down( ) function withcount set to -2 and sleepers set to 1. The function temporarily sets sleepers to 2, and then undoes the decrement performed by the down macro by addingthe value sleepers-1 to count. At the same time, the function checks whethercount is still negative (the semaphore could have been released by theholding process right before _ _down( ) entered the critical region).∙If the count field is negative, the function resets sleepers to 1 andinvokes schedule( ) to suspend the current process. The count field isstill set to -1, and the sleepers field to 1.∙If the count field is not negative, the function sets sleepers to 0, tries to wake up another process in the semaphore wait queue, and exitsholding the semaphore. On exit, the count field is set to 0 and thesleepers field to 0. The values of both fields look wrong, becausethere are other sleeping processes. However, consider that anotherprocess in the wait queue has been woken up. This process doesanother iteration of the loop; the atomic_add_negative( ) functionsubtracts 1 from count, restoring it to -1; moreover, before returningto sleep, the woken-up process resets sleepers to 1.So, the code properly works in all cases. Consider that the wake_up( ) function in _ _down( ) wakes up at most one process, because the sleeping processes in the wait queue are exclusive (see the section "How Processes Are Organized" in Chapter 3).Only exception handlers , and particularly system call service routines , can use the down( ) function. Interrupt handlers or deferrable functions must not invoke down( ),because this function suspends the process when the semaphore is busy. For this reason, Linux provides the down_trylock( ) function, which may be safely used by one of the previously mentioned asynchronous functions. It is identical to down( ) except when the resource is busy. In this case, the function returns immediately instead of putting the process to sleep.A slightly different function called down_interruptible( ) is also defined. It is widely used by device drivers, because it allows processes that receive a signal while being blocked on a semaphore to give up the "down" operation. If the sleeping process is woken up by a signal before getting the needed resource, the function increases the count field of the semaphore and returns the value -EINTR. On the other hand, if down_interruptible( ) runs to normal completion and gets the resource, it returns 0. The device driver may thus abort the I/O operation when the return value is -EINTR.Finally, because processes usually find semaphores in an open state, the semaphore functions are optimized for this case. In particular, the up( ) function does not execute jump instructions if the semaphore wait queue is empty; similarly, the down( ) function does not execute jump instructions if the semaphore is open. Much of the complexity of the semaphore implementation is precisely due to the effort of avoiding costly instructions in the main branch of the execution flow.5.2.9. Read/Write SemaphoresRead/write semaphores are similar to the read/write spin locks described earlier in the section "Read/Write Spin Locks," except that waiting processes are suspended instead of spinning until the semaphore becomes open again.Many kernel control paths may concurrently acquire a read/write semaphore for reading; however, every writer kernel control path must have exclusive access to the protected resource. Therefore, the semaphore can be acquired for writing only if no other kernel control path is holding it for either read or write access. Read/write semaphores improve the amount of concurrency inside the kernel and improve overall system performance.The kernel handles all processes waiting for a read/write semaphore in strict FIFO order. Each reader or writer that finds the semaphore closed is inserted in the last position of a semaphore's wait queue list. When the semaphore is released, the process in the first position of the wait queue list are checked. The first process is always awoken. If it is a writer, the other processes in the wait queue continue to sleep. If it is a reader, all readers at the start of the queue, up to the first writer, are also woken up and get the lock. However, readers that have been queued after a writer continue to sleep.Each read/write semaphore is described by a rw_semaphore structure that includes the following fields:countStores two 16-bit counters. The counter in the most significant word encodesin two's complement form the sum of the number of nonwaiting writers(either 0 or 1) and the number of waiting kernel control paths. The counter inthe less significant word encodes the total number of nonwaiting readers andwriters.wait_listPoints to a list of waiting processes. Each element in this list is arwsem_waiter structure, including a pointer to the descriptor of the sleepingprocess and a flag indicating whether the process wants the semaphore forreading or for writing.wait_lockA spin lock used to protect the wait queue list and the rw_semaphorestructure itself.The init_rwsem( ) function initializes an rw_semaphore structure by setting the count field to 0, the wait_lock spin lock to unlocked, and wait_list to the empty list. The down_read( ) and down_write( ) functions acquire the read/write semaphore for reading and writing, respectively. Similarly, the up_read( ) and up_write( ) functions release a read/write semaphore previously acquired for reading and for writing. The down_read_trylock( ) and down_write_trylock( ) functions are similar todown_read( ) and down_write( ), respectively, but they do not block the process if the semaphore is busy. Finally, the downgrade_write( ) function atomically transforms a write lock into a read lock. The implementation of these five functions is long, but easy to follow because it resembles the implementation of normal semaphores; therefore, we avoid describing them.5.2.10. CompletionsLinux 2.6 also makes use of another synchronization primitive similar to semaphores: completions . They have been introduced to solve a subtle race condition that occurs in multiprocessor systems when process A allocates a temporary semaphore variable, initializes it as closed MUTEX, passes its address to process B, and then invokes down( ) on it. Process A plans to destroy the semaphore as soon as it awakens. Later。

外文文献翻译封面格式及要求(模版)

毕业论文外文文献翻译院年级专业：2009级XXXXXXXXXXX 姓名：学号：附件：备注：（注意：备注页这一整页的内容都不需要打印，看懂了即可）1.从所引用的与毕业设计（论文）内容相近的外文文献中选择一篇或一部分进行翻译（不少于3000实词）；2.外文文献翻译的装订分两部分，第一部分为外文文献；第二部分为该外文文献的中文翻译，两部分之间用分页符隔开。

也就是说，第一外文文献部分结束后，使用分页符，另起一页开始翻译。

3.格式方面，外文文献的格式，除了字体统一使用Times new roman 之外，其他所有都跟中文论文的格式一样。

中文翻译的格式，跟中文论文的格式一样。

（注意：备注页这一整页的内容都不需要打印，看懂了即可,定稿后,请删除本页.）范文如下：注意,下面内容每一部份均已用分页符分开了,如果用本模板,请将每一模块单独删除,直接套用到每一模板里面,不要将全部内容一次性删除.【Abstract】This paper has a systematic analysis on outside Marco-environment of herbal tea beverage industry and major competitors of brands inside the herbal tea market. Based onthe theoretic framework, this paper takes WONG LO KAT and JIA DUO BAO herbal tea as an example, and researches the strategy on brand positioning and relevant marketing mix of it. Through analysis on the prevention sense of WONG LO KAT herbal tea, it was positioned the beverage that can prevent excessive internal heat in body, a new category divided from the beverage market. the process of brand positioning of it in Consumers brain was finished. Based on this positioning strategy, WONG LO KAT reasonably organized and arranged its product strategy, price strategy, distribution strategy and promotion strategy, which not only served for and further consolidated the position of preventing excessive internal heat in body, but also elevated the value of brand. The JDB and WONG LO KAT market competition brings us enlightenment. Reference the successful experience from the JDB and lessons from the failure of the WONG LO KAT.，Times New Roman.【Key Words】Brand positioning; Marketing mix; Positioning Strategy; enlightenment, lessons；ABC（本页为英文文献摘要，关键词两项一起单独一页，字体为：Times New Roman，小四号，1.5倍行距）(注:以下为英文文献正文内容,英文全文3000字.具体标题以原文为准.全文字体为Times New Roman.行间距为1.5倍.字号大小与论文正文的各级标题一致.如下:)I.Times New Roman ，Times New Roman，Times New RomanTimes New Roman, Times New Roman, Times New Roman, Times New Roman,This paper has a systematic analysis on outside Marco-environment of herbal tea beverage industry and major competitors of brands inside the herbal tea market. Based on the theoretic framework, this paper takes WONG LO KAT and JIA DUO BAO herbal tea as an example, and researches the strategy on brand positioning and relevant marketing mix of it. Through analysis on the prevention sense of WONG LO KAT herbal tea, it was positioned the beverage that can prevent excessive internal heat in body, a new category divided from the beverage market. the process of brand positioning of it in Consumers brain was finished. Based on this positioning strategy, WONG LO KAT reasonably organized and arranged its product strategy, price strategy, distribution strategy and promotion strategy, which not only served for and further consolidated the position of preventing excessive internal heat in body, but also elevated the value of brand. The JDB and WONG LO KAT market competition brings us enlightenment. Reference the successful experience from the JDB and lessons from the failure of the WONG LO KAT.This paper has a systematic analysis on outside Marco-environment of herbal tea beverage industry and major competitors of brands inside the herbal tea market. Based on the theoretic framework, this paper takes WONG LO KAT and JIA DUO BAO herbal tea as an example, and researches the strategy on brand positioning and relevant marketing mix of it. Through analysis on the prevention sense of WONG LO KAT herbal tea, it was positioned the beverage that can prevent excessive internal heat in body, a new category divided from the beverage market. the process of brand positioning of it in Consumers brain was finished. Based on this positioning strategy, WONG LO KAT reasonably organized and arranged its product strategy, price strategy, distribution strategy and promotion strategy, which not only served for and further consolidated the position of preventing excessive internal heat in body, but also elevated the value of brand. The JDB and WONG LO KAT market competition brings us enlightenment. Reference the successful experience from the JDB and lessons fromthe failure of the WONG LO KAT.II.Times New Roman ，Times New Roman，Times New RomanTimes New Roman, Times New Roman, Times New Roman, Times New Roman,This paper has a systematic analysis on outside Marco-environment of herbal tea beverage industry and major competitors of brands inside the herbal tea market. Based on the theoretic framework, this paper takes WONG LO KAT and JIA DUO BAO herbal tea as an example, and researches the strategy on brand positioning and relevant marketing mix of it. Through analysis on the prevention sense of WONG LO KAT herbal tea, it was positioned the beverage that can prevent excessive internal heat in body, a new category divided from the beverage market. the process of brand positioning of it in Consumers brain was finished. Based on this positioning strategy, WONG LO KAT reasonably organized and arranged its product strategy, price strategy, distribution strategy and promotion strategy, which not only served for and further consolidated the position of preventing excessive internal heat in body, but also elevated the value of brand. The JDB and WONG LO KAT market competition brings us enlightenment. Reference the successful experience from the JDB and lessons from the failure of the WONG LO KAT.This paper has a systematic analysis on outside Marco-environment of herbal tea beverage industry and major competitors of brands inside the herbal tea market. Based on the theoretic framework, this paper takes WONG LO KAT and JIA DUO BAO herbal tea as an example, and researches the strategy on brand positioning and relevant marketing mix of it. Through analysis on the prevention sense of WONG LO KAT herbal tea, it was positioned the beverage that can prevent excessive internal heat in body, a new category divided from the beverage market. the process of brand positioning of it in Consumers brain was finished. Based on this positioning strategy, WONG LO KAT reasonably organized and arranged its product strategy, price strategy, distribution strategy and promotion strategy, which not only served for and further consolidated the position of preventing excessive internal heat in body, but also elevated the value of brand. The JDB and WONG LO KAT market competition brings us enlightenment. Reference the successful experience from the JDB and lessons from the failure of the WONG LO KAT.III.Times New Roman ，Times New Roman，Times New RomanTimes New Roman, Times New Roman, Times New Roman, Times New Roman,This paper has a systematic analysis on outside Marco-environment of herbal tea beverage industry and major competitors of brands inside the herbal tea market. Based on the theoretic framework, this paper takes WONG LO KAT and JIA DUO BAO herbal tea as an example, and researches the strategy on brand positioning and relevant marketing mix of it. Through analysis on the prevention sense of WONG LO KAT herbal tea, it was positioned the beverage that can prevent excessive internal heat in body, a new category divided from the beverage market. the process of brand positioning of it in Consumers brain was finished. Based on this positioning strategy, WONG LO KAT reasonably organized and arranged its product strategy, price strategy, distribution strategy and promotion strategy, which not only served for and further consolidated the position of preventing excessive internal heat in body, but also elevated the value of brand. The JDB and WONG LO KAT market competition brings us enlightenment. Reference the successful experience from the JDB and lessons from the failure of the WONG LO KAT.This paper has a systematic analysis on outside Marco-environment of herbal tea beverage industry and major competitors of brands inside the herbal tea market. Based on the theoretic framework, this paper takes WONG LO KAT and JIA DUO BAO herbal tea as an example, and researches the strategy on brand positioning and relevant marketing mix of it. Through analysis on the prevention sense of WONG LO KAT herbal tea, it was positioned the beverage that can prevent excessive internal heat in body, a new category divided from the beverage market. the process of brand positioning of it in Consumers brain was finished. Based on this positioning strategy, WONG LO KAT reasonably organized and arranged its product strategy, price strategy, distribution strategy and promotion strategy, which not only served for and further consolidated the position of preventing excessive internal heat in body, but also elevated the value of brand. The JDB and WONG LO KAT market competition brings us enlightenment. Reference the successful experience from the JDB and lessons from the failure of the WONG LO KAT.This paper has a systematic analysis on outside Marco-environment of herbal teabeverage industry and major competitors of brands inside the herbal tea market. Based on the theoretic framework, this paper takes WONG LO KAT and JIA DUO BAO herbal tea as an example, and researches the strategy on brand positioning and relevant marketing mix of it. Through analysis on the prevention sense of WONG LO KAT herbal tea, it was positioned the beverage that can prevent excessive internal heat in body, a new category divided from the beverage market. the process of brand positioning of it in Consumers brain was finished. Based on this positioning strategy, WONG LO KAT reasonably organized and arranged its product strategy, price strategy, distribution strategy and promotion strategy, which not only served for and further consolidated the position of preventing excessive internal heat in body, but also elevated the value of brand. The JDB and WONG LO KAT market competition brings us enlightenment. Reference the successful experience from the JDB and lessons from the failure of the WONG LO KAT.This paper has a systematic analysis on outside Marco-environment of herbal tea beverage industry and major competitors of brands inside the herbal tea market. Based on the theoretic framework, this paper takes WONG LO KAT and JIA DUO BAO herbal tea as an example, and researches the strategy on brand positioning and relevant marketing mix of it. Through analysis on the prevention sense of WONG LO KAT herbal tea, it was positioned the beverage that can prevent excessive internal heat in body, a new category divided from the beverage market. the process of brand positioning of it in Consumers brain was finished. Based on this positioning strategy, WONG LO KAT reasonably organized and arranged its product strategy, price strategy, distribution strategy and promotion strategy, which not only served for and further consolidated the position of preventing excessive internal heat in body, but also elevated the value of brand. The JDB and WONG LO KAT market competition brings us enlightenment. Reference the successful experience from the JDB and lessons from the failure of the WONG LO KAT.【摘要】本文是对凉茶饮料的宏观环境以及凉茶市场内部主要品牌的竞争对手进行了系统分析。

毕业论文的外文翻译要求

毕业论文的外文翻译要求毕业论文是学生完成学业的重要标志，而其中的外文翻译部分更是为了提供更全面的学术支持和国际交流。

为了确保翻译的准确性和专业性，我们有一些明确的要求和规定。

一、译稿准确性要求1.1 语义准确：译稿应准确地传达原文的含义，翻译词语和句子应与原文相对应，确保不出现歧义或误解。

1.2 文法准确：译稿应符合外语语法规范，句子结构要清晰连贯，语法错误应予避免。

1.3 词汇准确：译稿应使用准确的词汇，能够准确表达原文中的专业术语和概念。

1.4 表达准确：译稿应能充分表达原文作者的意图和观点，不改变原意，不添加任何无关信息。

二、格式要求2.1 页面设置：译稿与正文部分应保持一致，包括页边距、字体、字号和行间距等方面。

2.2 段落格式：译稿应采用适当的段落划分，确保内容结构清晰，段落之间应有明显的过渡关系。

2.3 标点符号：译稿中的标点符号应准确无误，与原文保持一致。

2.4 图表翻译：如原文中包含图表、图片等内容，应准确翻译并清晰插入，保持与原文的对应关系。

三、语言风格要求3.1 学术性语言：译稿应以学术性的语言进行表达，避免使用口语或俚语词汇。

3.2 表达简明：译稿应尽量使用简明扼要的语言，避免冗长和啰嗦的表达。

3.3 文体恰当：译稿应根据原文的文体特点，保持与之一致的语言风格，如正式、客观等。

3.4 遵循学科要求：根据不同学科的要求，译稿应遵循相应的学科规范和术语。

四、参考文献要求4.1 引用准确：如译稿中涉及引用原文中的内容，应准确标注出处，遵循学术引用规范。

4.2 参考文献著录：如译稿中有参考文献部分，应按照规范的著录格式进行排版，确保引用的准确性。

4.3 翻译标注：如译稿中对参考文献进行翻译或添加注释，应将其清晰标注，以区分原文与译文。

总结：毕业论文的外文翻译要求是多方面的，从译稿准确性、格式要求、语言风格要求到参考文献要求，都需要学生严格遵循。

合理的格式和清晰的语言表达是展示学术水平和专业素养的重要方面，而译稿的准确性更是毕业论文的基石。

外文文献翻译格式要求

外文文献翻译格式要求
外文文献中文翻译的格式要求通常包括以下几个方面：
2.翻译稿的标题应与原文保持一致，通常在文献翻译稿的第一页的中间位置，使用加粗、居中排版。

3.每一段落开始时空两行，段落间距可以根据需要适当调整。

4. 翻译稿中的引用部分，应在文中用中括号标注原文引用部分的位置，如 "[Original text]"
5.翻译稿中的图表、表格等内容，需要在相应位置插入，并在上方标明图表或表格编号，并在下方进行说明。

7.在翻译稿的最后，需要标注翻译人员的签名，并附上日期。

总之，翻译稿与原文应尽量保持一致，在排版和格式上遵循一定的要求和规范。

具体格式要求也可以根据翻译机构或期刊的要求进行调整。

外文文献翻译要求

外文文献翻译要求
1.译文封面
（1）文献题目：分两行填写，第一行填文献原题，题目中每个实词的首字母要大写；第二行填中文题目。

两行题目的字号均为三号，加粗；英文字体用新罗马体（Times New Roman），中文字体用宋体；行距均为1.5倍行距。

（2）班级、学号、姓名、指导教师：这几项要在相应栏内的横线上居中填写，不要改动原字体格式（方正姚体、三号、加粗）；班级、学号均要完整，不能简写；学生、指导教师的姓若只有两个字的，两字间要空两个半角空格。

2.译文正文
（1）从文献原文的摘要部分开始翻译，译文字数不少于2000字，译文各部分的格式按“信息工程系本科学士学位论文（设计）撰写规范”的规定设置。

（2）文献的页眉、页脚不用翻译，译文页脚部分只设置页码。

（3）译文中若要放入原文的图、表，要按论文格式要求排版。

3.装订顺序
译文一律用A4纸单面打印，装订顺序为：译文封面→外文文献原文→译文，其中原文由原pdf文件直接打印出来。

学生要求外文参考资料及译文封面

毕业设计（论文）外文参考
资料及译文
译文题目：英文题目
中文题目（题目外面不加括号）学生姓名：学号：
专业：
所在学院：
指导教师：
职称：
年月日
1、说明：
要求学生结合毕业设计（论文）课题参阅一篇以上的外文资料，并翻译至少一万印刷符（或译出3千汉字）以上的译文。

2、整篇文档的结构为（封面+英文+中文）。

中文需要另起一页，不要直接接在英文后面。

中文用宋体小四号字，英文用新罗马体12号字，行距为固定值20磅，首行缩进。

版面上空2.5cm，下空2cm，左空2.5cm，右空2cm。

（1）一级标题（如“1”，也可用“一”）（格式：小三号黑体居左）
（2）二级标题（如“1.1”，也可用“（一）”）（格式：四号黑体体居左）
（3）三级标题（如“1.1.1”，也可用“1”）（格式：小四号宋体居左）
3、英文资料若不是word文档，（例如pdf格式等），则另外附上英文原文。

毕业设计(论文)外文资料及译文(模板)

大连东软信息学院
毕业设计（论文）外文资料及译文
系所：
专业：
班级：
姓名：
学号：
大连东软信息学院
Dalian Neusoft University of Information
外文资料和译文格式要求
一、装订要求
1、外文资料原文（复印或打印）在前、译文在后、最后为指导教师评定成绩。

2、译文必须采用计算机输入、打印。

3、A4幅面打印，于左侧装订。

二、撰写要求
1、外文文献内容与所选课题相关。

2、本科学生译文汉字字数不少于4000字，高职学生译文汉字字数不少于2000字。

三、格式要求
1、译文字号：中文小四号宋体，英文小四号“Times New Roman”字型，全文统一，首行缩进2个中文字符，1.5倍行距。

2、译文页码：页码用阿拉伯数字连续编页，字体采用“Times New Roman”字体，字号小五，页底居中。

3、译文页眉：眉体使用单线，页眉说明五号宋体，居中“大连东软信息学院本科毕业设计（论文）译文”。

大连东软信息学院毕业设计（论文）译文
大连东软信息学院毕业设计（论文）译文
大连东软信息学院毕业设计（论文）译文
大连东软信息学院毕业设计（论文）译文
大连东软信息学院毕业设计（论文）译文。

毕业设计外文翻译撰写格式规范

嘉兴学院（南湖学院）毕业论文（设计）外文翻译撰写格式规范一、外文翻译形式要求1、要求本科生毕业论文（设计）外文翻译部分的外文字符不少于1.5万字, 每篇外文文献翻译的中文字数要求达到2000字以上，一般以2000~3000字左右为宜。

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

3、外文翻译应包括外文文献原文和译文，译文要符合外文格式规范和翻译习惯。

二、打印格式嘉兴学院（南湖学院）毕业论文（设计）外文翻译打印纸张统一用A4复印纸，页面设置：上：2.8；下：2.6；左：3.0；右：2.6；页眉：1.5；页脚：1.75。

段落格式为：1.5倍行距，段前、段后均为0磅。

页脚设置为：插入页码，居中。

具体格式见下页温馨提示：正式提交“嘉兴学院（南湖学院）毕业论文（设计）外文翻译”时请删除本文本中说明性的文字部分（红字部分）。

文档标题采用楷体_GB2312，三号字体，加粗，居中。

一级标题采用楷体_GB2312，四号字体，加粗，左侧顶格。

二级标题采用宋体，小四号字体，加粗，缩进两个中文字符。

三级标题采用宋体，五号字体，缩进两个中文字符。

正文采用五号宋体字，数字用阿拉伯数字，字母和数字用Times New Roman。

嘉兴学院（南湖学院）毕业设计外文翻译题目：系别：专业：班级：学号：学生姓名：一、外文摘要及关键词英文文章题目（Times New Roman小三号，1.5倍行距，居中）（作者工作单位，省略）ABSTRACT：（Times New Roman小四号加粗，顶格）：英文原文（Times New Roman五号，1.5倍行距）KEYWORDS：（Times New Roman小四号加粗，顶格）：同行接关键词，关键词之间用逗号分割，用五号Times New Roman字体。

二、中文摘要及关键词翻译文章题目（黑体小三号，1.5倍行距，居中）摘要：由于消费者的需求和汽车市场竞争力的提高，汽车检测标准越来越高。

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

杭州电子科技大学毕业设计（论文）外文文献翻译毕业设计（论文）题目液压制动器基本翻译（1）题目有用产品翻译（2）题目学院机械学院专业车辆工程姓名班级学号指引教师液压制动基本空气制动系统得到更多关注，但更多车辆上安装液压制动器。

理解它们是如何工作，是安全，具成本效益诊断和修复第一步。

有无想过为什么不能只是其中一种制动？这是由于空气和液压制动器，使一种或某些应用程序其她抱负经营特色。

重型组合车辆，空气是明确选取，由于将需要大量液体阿卡迪亚所有分泵。

此外，布满液压油与制动分泵和软管将是混乱。

但对于轻型和中型卡车直应用，液压制动器提供优势涉及：•制动感觉- 那就是，踏板越往下压，努力增长;高线压力，容许使用更轻，更紧凑制动组件;•更少初始费用，由于用更小和更少元件;•卫生，液压制动器是封闭系统;•易于定位泄漏，由于液体是可见。

液压制动系统有更多排列，比在空气系统中发现，但都基本相似。

液压系统所有液压制动系统包括流体水库，主缸，液压，液压管路，对制动器进行加压流体软管和一种或各种轮缸（S）对每个车轮产生。

分泵扩大流体压力下，迫使制动蹄对鼓内侧。

如果使用盘式制动器，卡钳与不可分割气瓶打击转子时施加压力。

由于车辆必要可以更迅速，它可以加速到停止，需要大量刹车力。

因而，必要减速刹车产生马力发动机作用多次。

为了发展须持有对鼓或盘制动器衬片力量，实现受控减速，这是要乘原始力量施加在刹车踏板。

当使用液压系统，机械杠杆是在脚踏板联动。

然而，不同分泵或卡尺直径直径，关系到主缸内径，提供了一种额外增长比率。

液压系统中，各分泵交付压力，直接影响由活塞地区。

例如，如果一种轮缸活塞面积2平方英寸，另一种活塞面积1平方英寸，系统压力为400磅，2平方英寸活塞将针对制动器推一种迫使800磅。

1平方英寸活塞施加一种400磅力量。

总泵和分泵地区之间比例拟定在轮缸活塞力量倍增。

为保持在头脑，直径较大轮缸，更流畅，必要提供由主缸行程较长研究生转化。

请记住，直径较大轮缸，更流畅，必要由主缸提供，以弥补它。

这意味着进入一种较长主缸行程。

如果主缸孔直径增长和相似申请依然有效，更少压力将在系统开发，但一种更大轮缸活塞可以用来实当前轮缸所需压力。

显然，必要更换主缸，轮缸或卡尺相似设计，并作为原单位承担。

液压系统中，各分泵交付压力，直接影响由活塞地区。

例如，如果一种轮缸活塞面积2平方英寸，另一种活塞面积1平方英寸，系统压力为400磅，2平方英寸活塞将针对制动鞋推一种迫使800磅。

1平方英寸活塞施加一种400磅力量。

总泵和分泵地区之间比例拟定在轮缸活塞力量倍增。

液压制动系统分割系统，涉及两个谨慎制动电路。

一主缸活塞和水库是一种单独活塞及伺服制动器上其她桥（S）水库，用来驱动一轴刹车。

虽然罕见，某些轻型制动系统分裂对角线而非桥桥。

分割系统因素是，如果一种液压回路泄漏发展，将停止车辆。

固然，不应当被驱动车辆远超过必要制动系统修复。

当液压回路发生故障，压力差开关感官两个电路之间不平等压力。

互换机包括由弹簧片，并在每年年终电触头位于活塞。

从一种液压回路中流体压力提供压力差开关一端，并从其她电路压力提供应另一端。

随着压力一种电路，其她电路正常压力，迫使活塞失效一边，关闭接触，并照亮仪表板警示灯。

动力辅助协助电力单位，或助推器，减少运营商努力，在刹车踏板。

真空助力器，轻型汽车流行，使发动机真空隔膜一侧，对对方大气压力。

一种阀门，使真空作用于刹车踏板行程中比例隔膜。

这有助于踏板努力，并增长对制动液压力，无需过度增长在踏板努力。

其她类型助推器使用液压压力- 无论是从车辆动力转向泵，或从一种单独电动泵，或两者兼而有之- 协助刹车踏板被踩下踏板作用，阀门液压升压室申请增长压力在增长主缸活塞。

有些系统使用真空和液压助力。

在其她系统中，从船上压缩机空气压力产生液压系统压力。

阀杆液压制动系统中常用阀门涉及：•配比，或压力平衡阀门。

这些限制液压比例后轮刹车系统压力达到预设高阻值。

提高前轮/后轮在高速制动制动平衡时，某些车辆先后重量转移，并有助于防止后轮配料阀高度传感器。

也就是说，她们调节后轮制动压力，在车辆荷载响应。

随着车辆负载增长（减少高度）液压后轮刹车是不容许；•测光阀门。

这些保持了前盘式制动器压力，让后轮鼓式制动蹄克服返回弹簧压力，使接触后鼓。

这可以防止锁定在湿滑路面上前刹车灯制动应用。

这些阀门不来硬制动过程中发挥作用。

泊车停车功能液压制动系统之间差别很大。

许多轻型车辆使用与后轮鼓式制动器杆和电缆相配合，逐渐加大杆或脚踏拉电缆，这反过来，拉杠杆总成，每个后轮结束客运车类型。

杠杆迫使制动蹄外，她们对鼓机械棘轮被释放，直到举起。

其她泊车系统涉及弹簧腔，像那些用于空气制动系统。

这是弹簧控制，但由液压脱开而不是空气。

防抱死许多轻型卡车液压制动，防抱死制动系统上使用后轮保持轻载时，这些车辆制动稳定性。

前面和后轮防抱死普通是一种选项，GVWR超过10,000磅车辆，这是需要引导和驱动桥防抱死关闭。

在当前液压防抱死系统，转储阀释放压力到一种累加器在即将车轮锁死状况下液压油。

电子控制箱接受来自传感器传播和/或在车轮速度信号（S）。

当施加制动，控制箱检测在后轮速度，减少和激活转储阀（S），如果减速率超过预定限制。

控制箱通电一系列流血轮液压迅速脉冲单向阀。

继续转储阀是脉冲在防抱死模式，以保持车轮转动，同步保持控制减速。

在最后停止，阀门勉励和累加器中任何液体返回到主缸，恢复正常刹车操作。

基本刹车在液压系统基本制动器可以是鼓或光盘。

在许多应用中，光盘上使用前轴后方鼓。

鼓式制动器说是自激。

这是由于制动蹄扩大和联系一种旋转滚筒，引导或向前制动蹄被推向对刹车制动箍由移动鼓力量。

这个成果在更高衬里鼓比将仅由轮缸产生压力。

随着制动器衬片磨损，必要定期移近鼓，以保证在制动过程中恰当接触。

虽然某些旧鼓式制动器总成，手动调节，大某些都是自动。

这些使用一种星轮或棘轮大会，这感官分泵时已超过其正常行程前去，并扩大在另一端制动蹄支点。

除了摩擦元素之一，制动鼓或转子也充当散热器。

它必要迅速制动过程中吸取热量，并保持它，直到它可以将空气中消散。

鼓或转子较重是，它可以容纳更多热量。

这是很重要，由于制动器衬片热，她们更容易受到热衰退。

热衰退是诱发重复硬盘停止和成果减少鼓形轮子连接摩擦和增长车辆制动距离。

作为一项规则，高品质衬里，将显示低于劣质热褪色。

此外碟式刹车比鼓式制动器耐热褪色性能更好。

另一种褪色类型，刹车容易褪色水。

鼓式制动器，其表面积大，在安全范畴内比盘式制动器每平方英寸之间需要更少衬力和鼓力。

加上鼓保水形状，鞋和鼓之间潮湿条件下增进水面滑行。

成果是制动距离大大增长。

盘式制动器，具备较小摩擦表面和高夹紧力，做一种良好工作从转子擦水，并显示在潮湿时停止能力几乎没有减少。

HYDRAULIC BRAKE BASICSAir brakes get more attention，but hydraulic brakes are installed on more vehicles. Understanding how they work is the first step to safe，cost-effective diagnosis and repair.Ever wonder why there can't be just one kind of brake? It's because air and h ydraulic brakes each have operating characteristics that make one or the other ideal for certain applications.In heavy-duty combination vehicles，air is the clear choice because of the large volume of liquid that would be needed to acadia all the wheel cylinders. Plus，dealing with gladhands and hoses filledwith hydraulic fluid would be messy.But for light and medium-duty straight-truck applications, hydraulic brakes offer advantages including: •Brake feel — that is，as the pedal is pressed farther down，effort increases;•High line pressures，which permit the use of lighter，more compact braking components; •Less initial expense，due to smaller and fewer components;•Cleanliness — hydraulic brakes are closed systems;•Ease of locating leaks，since fluid is visible.There are many more permutations of hydraulic brake systems than found in air systems，but all have basic similarities.THE HYDRAULIC SYSTEMAll hydraulic brake systems contain a fluid reservoir，a master cylinder，whichproduces hydraulic pressure, hydraulic lines and hoses to carry pressurized fluid to the brakes，and one or more wheel cylinder(s) on each wheel.The wheel cylinders expand under fluid pressure，and force the brake shoes against the insides of the drums. If disc brakes are used，calipers，with integral cylinders，clamp down on the rotors when pressure is applied.Because a vehicle must be able to stop much more quickly than it can accelerate，a tremendous amount of braking force is needed. Therefore，the retarding horsepower generated by the brakes must be several times that of the engine.In order to develop the forces required to hold the brake linings against the drums or discs，and to achieve controlled deceleration，it is necessary to multiply the original force applied at the brake pedal. When a hydraulic system is used，the only mechanical leverage is in the foot pedal linkage. However，varying the diameter of the wheel cylinders or caliper diameters，in relation to the master cylinder bore diameter，provides an additional increase in ratio.In a hydraulic system，the pressure delivered by the various wheel cylinders is directly affected by the areas of their pistons. For example，if one wheel-cylinder piston has an area of 2 square inches，and another piston has an area of 1 square inch，and the system pressure is 400 psi，the 2-square-inch piston will push against the brake shoes with a force of 800 pounds. The 1-square-inch piston will exert a force of 400 pounds. The ratio between the areas of the master cylinder and the wheel cylinders determine the multiplication of force at the wheel cylinder pistons.Keep in mind that the larger a wheel cylinder's diameter，the more fluid must be supplied by the master cylinder to fill it. This translates into a longer master-cylinder stroke.If the master cylinder bore diameter is increased and the applying force remains the same，less pressure will be developed in the system，but a larger wheel-cylinder piston can be used to achieve the desired pressure at the wheel cylinder. Obviously，a replacement master cylinder，wheel cylinder or caliper must be of the same design and bore as the original unit.Hydraulic brake systems are split systems，comprising two discreet braking circuits. Onemaster-cylinder piston and reservoir is used to actuate the brakes on one axle，with a separate piston and reservoir actuating the brakes on the other axle(s). Although rare，some light-duty brake systems are split diagonally rather than axle by axle.The reason for the split system is that if a leak develops in one hydraulic circuit，the other will stop the vehicle. Of course，the vehicle shouldn't be driven any farther than necessary to have the brake system repaired.When one of the hydraulic circuits fails，a pressure-differential switch senses unequal pressure between the two circuits. The switch contains a piston located by a centering spring and electrical contacts at each end. Fluid pressure from one hydraulic circuit is supplied to one end of the pressure-differential switch，and pressure from the other circuit is supplied to the other end. As pressure falls in one circuit，the other circuit's normal pressure forces the piston to the inoperative side，closing the contacts and illuminating a dashboard warning light.POWER ASSISTPower assist units，or boosters，reduce operator effort at the brake pedal. Vacuum boosters，popular on light-duty vehicles，make use of an engine vacuum on one side of a diaphragm，and atmospheric pressure on the other side. A valve allows the vacuum to act on the diaphragm in proportion to brake pedal travel. This assists the pedal effort，and allows increased pressure on the brake fluid，without an undue increase in pedal effort.Other types of boosters use hydraulic pressure — either from the vehicle's power steering pump or from a separate electric pump，or both — to assist pedal effort. As the brake pedal is depressed，a valve increases hydraulic pressure in a boost chamber to apply increased pressure to the master cylinder pistons.Some systems use both vacuum and hydraulic assist. In other systems，air pressure from an onboard compressor is used to generate hydraulic system pressure.VALVINGValves commonly found in hydraulic brake systems include：Proportioning，or pressure-balance valves. These restrict a percentage of hydraulic pressure to the rear brakes when system pressurereaches a preset high value. This improves front/rear brake balance during high-speed braking，when some of a vehicle's rear weight is transferred forward，and helps prevent rear-wheel lockup. Some proportioning valves are height-sensing. That is，they adjust rear-brake pressure in response to vehicle load. As a vehicle's load increases (decreasing height) more hydraulic pressure to the rear brake s is allowed；Metering valves. These hold off pressure to front disc brakes to allow rear drum brake shoes to overcome return-spring pressure and make contact with the rear drums. This prevents locking thefront brakes on slippery surfaces under light braking applications. These valves do not come into play during hard braking.PARKINGThe parking function varies greatly among hydraulic brake systems. Many light-duty vehicles with rear drum brakes use a passenger-car type lever-and-cable setup. A ratcheted lever or foot pedal pulls a cable，which，in turn，pulls a lever assembly at each rear wheel end. The lever forces the brake shoes apart，and they are mechanically held against the drums until the ratchet is released.Other parking systems include spring chambers，like those used on air-brake systems. These are spring-engaged，but are disengaged by hydraulic pressure instead of air.ANTILOCKOn many hydraulically braked light-duty trucks，antilock brakes are used on the rear wheels to preserve braking stability when these vehicles are lightly loaded. Front and rear-wheel antilock is usually an option，except for vehicles over 10,000 pounds GVWR，which are required to have steer and drive-axle antilock. In current hydraulic antilock systems，a dump valve releases pressurized hydraulic fluid into an accumulator in the event of an impending wheel lockup.An electronic control box receives speed signal(s) from sensors in the transmission and/or at the wheels. When the brakes are applied，the control box senses the decrease in rear wheel speed，and activates the dump valve(s) if the rate of deceleration exceeds a predetermined limit.The control box energizes the dump valve with a series of rapid pulses to bleed-offwheel hydraulic pressure. Continuing in antilock mode，the dump valve is pulsed to keep the wheels rotating，while maintaining controlled deceleration.At the end of such a stop，the valve de-energizes and any fluid in the accumulator is returned to the master cylinder. Normal brake operation resumes.FOUNDATION BRAKESFoundation brakes in hydraulic systems can be either drum or disc. In many applications，discs are used on the front axle and drums on the rear.Drum brakes are said to be self-energizing. That's because when the brake shoes expand and contact a rotating drum，the leading，or forward, brake shoe is pushed against the trailing shoe by the force of the moving drum. This results in higher lining-to-drum pressure than would be produced by the wheel cylinder alone.As brake linings wear，the shoes periodically must be moved closer to the drums to ensure proper contact during braking. While some older drum brake assemblies are manually adjusted，most are automatic. These use a star wheel or ratchet assembly，which senses when the wheel cylinder has traveled beyond its normal stroke，and expands the pivot point at the other end of the brake shoes.In addition to being one of the friction elements，the brake drum or rotor also acts as a heat sink. It must rapidly absorb heat during braking，and hold it until it can be dissipated into the air. The heavier a drum or rotor is，the more heat it can hold.This is important，since the hotter the brake linings get，the more susceptible they are to heat fade. Heat fade is induced by repeated hard stops and results in reduced lining-to-drum/rotor friction and increased vehicle stopping distance. As a rule，high-quality linings will display less heat fade than inferior ones. Also，discbrakes are far more resistant to heat fade than drum brakes.Another type of fade that brakes are susceptible to is water fade. Drum brakes，with their large surface areas，apply fewer pounds per square inch of force between lining and drum during a stop thandisc brakes. This，added to the drum's water-retaining shape，promotes hydroplaning between shoe and drum under wet conditions. The result is greatly increased stopping distance.Disc brakes，with their smaller friction surfaces and high clamping forces，do a good job of wiping water from rotors，and display little reduction in stopping capability when wet.有用产品气动钢瓶。