heart towards sea

The benefits of being a female software engineer[zt]

2011-03-07T10:38:00.001Z

track from http://www.jeanhsu.com/?p=263

There aren't a lot of female software engineers out there, but being one is not all that bad! I love being a software engineer, for many reasons that are not gender-specific: the excitement of new releases that impact real users, working with an awesome team, being an active part of the thriving Palo Alto startup community... But then there are a lot of reasons that I love being a female software engineer.

Casual attire
While I'm sure lots of male engineers appreciate the casual engineer dress code, I really appreciate it. For men, assorted button-down shirts and slacks will suffice for business-casual attire, but women seem to have some pressure to "update their wardrobe" and "accessorize." As for me? My college wardrobe transitioned seamlessly into my work wardrobe. Now, standard work apparel is t-shirt and jeans, accessorized with a pair of flip-flops, sneakers, sanuks, or if I am feeling particularly fun, my vibrams. I don't really enjoy or have time to go shopping, so this works out well.

The Odds
The odds are really freaking good, and only some of the goods are odd. Sure there are a bunch of socially awkward engineers, but because of the sheer scarcity of women in the field, if you are a single female you can have first pick of a lot of really nice available guys. I met my husband Tyler while we were both working for Google in NY, and he has said that he's glad he met me before he moved out to California. With the scarcity of women in software, I don't envy any of the single male software engineers in Silicon Valley.

Less Drama
I've actually never worked somewhere that has more women than men, but I suspect that working with mostly men keeps the workplace drama-free. Not that all or most women are moody drama queens, but you know, it happens. It just seems to happen less with men.

Being Memorable
While I would of course love to see more women in the industry, a perk of being one of the few is that people remember you. If you go to a tech event or conference and meet 30 male developers and 2 female developers, you will probably remember their names, or at least their faces. You also get the added bonus of seeing people's confused reactions when they ask you if you're in marketing, and you tell them that you are a developer.

Being Liked
It's just nice to have some women in a male-dominated workspace. They generally remember to shower every so often, and if you ever bring brownies to work, you're suddenly everyone's favorite person for at least a few minutes (though this is true for males as well). Sure, if you're a real bitch, no one's going to like you, but most female engineers are easy to get along with and are well-liked and appreciated in their team. It makes it a little less like, hey look at all this testosterone fueling our coding hackathons in this smelly room.

If you're a female software engineer, feel free to comment on any benefits you've experienced either compared to men in the field, or compared to women in other fields!

swimming style

2010-08-28T23:07:00.001+01:00

    * Breaststroke 蛙泳
    * Backstroke 仰泳
    * Butterfly 蝶泳
    * front crawl 自由泳
Recreational Styles

There are a large number of different recreational swimming styles. Some of them are swum on the breast, some on the back, and some on the side. Of course, all the competition strokes can be swum recreationally.
On the Breast

    * Front Crawl is the fastest swimming style.
          o Trudgen (also known as Trudgeon): The trudgen is similar to the front crawl, except it is swum with a scissor kick
          o Trudgen Crawl: Similar to the trudgen, but with a flutter kick between the scissor kicks
          o Double Trudgen: Similar to the trudgen, but the sides of the scissor kick alternate
          o Double Trudgen Crawl: Similar to the double trudgen, but with a flutter kick between the scissor kicks
          o Dolphin Crawl: Similar to front crawl, but with a dolphin kick. One kick per arm or two kicks per cycle. This style is often used in training.
          o Catch up stroke: A variation of the front crawl where one arm always rests at the front while the other arm performs one cycle.
    * Breaststroke
    * Heads-Up Breaststroke: Similar to the breaststroke, but the head stays out of the water. This style is very popular for recreational and swimmers and also for rescue swimmers approaching a victim.
    * Butterfly
    * Slow Butterfly (also known as Moth stroke): Similar to butterfly, but with an extended gliding phase, Breathing during the pull/push phase, return head into water during recovery. This style uses four kicks or more per cycle.
    * Dog Paddle: face over water and paddling alternatingly with the hands.
    * Human Stroke: Similar to the dog paddle, but the arms reach out more and pull farther down.
    * Survival Travel Stroke: Alternating underwater arm stroke, one cycle for propulsion, one for lift to stay on the surface. This style is slow but sustainable.
    * Snorkeling: Swimming on the breast using a snorkel, usually in combination with masks and fins. Any stroke on the breast can be used, and there is no need to lift or turn the head for breathing.

On the Back

    * Backstroke (also known as Back Crawl)
    * Elementary Backstroke: Both arms move synchronized with a small synchronized kick. This is also sometimes known as the Lifesaving Kick
    * Inverted Breaststroke: Similar to Elementary Backstroke, but with a breaststroke kick.
    * Inverted Butterfly: Similar to Elementary backstroke, but with a dolphin kick. This is often used for training.
    * Back Double Trudgen: Similar to the Backstroke, but with a scissor kick to alternating sides.
    * Flutter Back Finning: Symmetrically underwater arm recovery with flutter kick.
    * Feet First Swimming: A very slow stroke on the back where a breaststroke movement with the arms propels the body forward feet first. This is often used for training.

On the Side

    * Side Stroke: Lying on the side with alternating underwater recovery and a scissor kick
    * Overarm Sidestroke: Similar to the side stroke, but with a over water recovery of the top arm

Other

    * Corkscrew Swimming: Alternating between Front crawl and backstroke every arm. This leads to a constant rotation of the swimmer. The stroke is used mainly for training purposes
    * Underwater Swimming: any style with underwater recovery can be swum under water for certain distances depending on the need for air. Underwater swimming on the back has the additional possibility of water entering the nose. The swimmer can breathe out through the nose or wear a nose clip. Some swimmers can close their nostrils with the upper lip.
    * Gliding: The swimmer is stretched with the arms to the front, the head between the arms and the feet to the back. This streamlined shape minimizes resistance and allows the swimmer to glide, for example after a start, a push off from a wall, or to rest between strokes.
    * Turtle stroke: on the breast, extend right arm then pull, after pushing with the left leg (while opposite limbs are recovering), then opposite limbs repeat this process, i.e. left arm pulls after right leg pushes. Uses muscles of the waist. Head can easily be above or below water: this is a slow but very sustainable stroke, popular with turtles and newts.
from: http://www.wordiq.com/definition/List_of_swimming_styles

电影俚语

2010-08-20T16:12:00.001+01:00

A
A Feather in sb.’s Cap 令某人引以为傲的成就、功绩或荣誉
A Fly in the Ointment 令人扫兴的人或事
A Horse of a Different Color 完全是另一回事，风马牛不相及
A Little Bird Told Me…有（知情）人私下告诉我了
A Mount / Hill of Beans 微不足道，无足轻重
A Piece of Cake 小菜一碟，小事一桩，非常容易，很简单
A Price on sb.’s Head 缉拿或杀死某人的悬赏金
A Shot in the Dark （没有根据的）乱猜或瞎蒙
Achilles’ Heel 性格上的致命弱点或缺陷
Add Insult to Injury 加倍伤害，落井下石
An Eye for an Eye 以牙还牙，以眼还眼
Apple of sb.’s Eye 某人的掌上明珠
Apple-pie Order 有条不紊，井然有序，井井有条
At Loggerheads (with sb.) （和某人）不和，（和某人）势不两立
At the Drop of a Hat 立刻，马上；毫不迟疑，刻不容缓
At the End of One’s Ropes 束手无策，筋疲力尽，忍无可忍

B
Back to Square One 回到起点，从头再来
Bark up the Wrong Tree 找错目标，错怪了人，白费精力
Basket Case 废物，疯狂的人
Be All Ears 洗耳恭听
Be All Thumbs 笨手笨脚，不能胜任
Beat around / about the Bush 拐弯抹角（浪费时间），旁敲侧击
Behind the Eight-ball 受到挫折，不顺心
Below the Belt 暗箭伤人
Beyond the Pale 出格，越轨
Bite the Bullet 咬紧牙关应对，硬着头皮应付
Black Sheep 害群之马，败类
Blow off Steam 发泄，释放压力
Blow One’s Cover 暴露身份，揭穿秘密（使无法隐瞒）
Blow the Whistle 揭发，告发，检举
Born with a Silver Spoon in One’s Mouth 出身富贵，生于富贵人家
Break a Leg 祝你好运
Bury / Hide One’s Head in the Sand 躲避问题的态度，采取驼鸟政策
Bury the Hatchet / Tomahawk 休战，讲和，摈弃前嫌
By Jove! 天啊！老天爷啊！

C
Call a Spade a Spade 实事求是地说
Call sb. Names 辱骂某人，诋毁某人
Call the Shots 发号施令，掌控全局
Carry a Torch for sb. 暗恋某人
Cast Pearls before Swine 明珠暗投，对牛弹琴
Close Shave 十分惊险
Close, but No Cigar 差一点，几乎就要猜对了
Compare Apples and Oranges 把风马牛不相及的两个人或两种事物作比较
Cook sb.’s Goose 毁掉某人成功的机会
Crocodile Tears 假哭，假慈悲
Cross One’s Heart 我发誓，我说的是实话
Cry over Spilt / Spilled Milk 浪费时间做无能为力、于事无补的事情
Curiosity Killed the Cat 好奇害死猫
Cut Corners 减少费用，节省时间
Cut No Ice 不起作用，不能让人相信
Cut sb. Some Slack 放某人一马
Cut the Crap 废话少说
Cut to the Chase 别再浪费时间，切入正题，干正事

D
Down in the Mouth(英) / down in the Dumps(美) 郁郁不乐，垂头丧气，心情不好
Drown One’s Sorrows / Troubles 借酒消愁

E
Easy Come, Easy Go. 来得容易，去得快
Eat Crow 被迫认错，道歉

F
Face the Music 接受批评，承担后果
Faster than You Can Say Jack Robinson 一眨眼的工夫
Fifth Wheel 不受欢迎的人，多余的人
Fish in a Barrel 瓮中鳖
Fish to Fry 重要的事情
Fly by the Seat of One’s Pants 凭自己的感觉做事，摸着石头过河
Fly off the Handle 勃然大怒
Fly on the Wall 暗中观察或监视别人的人
For the Birds 荒唐可笑的，毫无价值的，无意义的，不重要的
Forty Winks 小睡，打盹

G
Get Hitched 结婚
Get off on the Wrong Foot 一开始就没把事情做对
Get / Put sb. Back up 惹恼某人，惹怒某人
Get sb.’s Nose to the Grindstone 努力干活，毫不停歇
Get sth. up (in) One’s Sleeve 留有一手，有锦囊妙计
Get the Blues 情绪低落，郁郁寡欢
Get Wind of sth. 听到……的风声
Give It a Shot 试试吧，来吧
Give Me Five! 来击个掌吧！
Give sb. a Knuckle Sandwich 用拳头打某人，给某人拳头吃
Give sb. the Bird 给某人喝倒彩，存心奚落某人
Give sb. the Boot 开除某人，解雇某人
Give sb. the Cold Shoulder 对某人冷淡，冷眼相待
Give sb. the Green Light 给某人开绿灯
Go / Walk down the Aisle 走上红地毯，结婚
Goody Two-shoes 老好人，伪善家
Gravy Train 肥差
Green-eyed Monster 妒忌
Grow Eyes in / at the Back of One’s Head 多长只眼睛，警觉

H
Half the Battle 成功的一半，至关重要
Have a Bee in One’s Bonnet 胡思乱想
Have a Crush on sb. 暗恋某人，迷恋某人
Have Butterflies in One’s Stomach 很紧张，（心里）七上八下的
Have / Get Deep Pockets 有很多钱，腰包鼓鼓的
Have sb. over a Barrel 使某人处于掌控之中
Head Honcho 管理人，负责人，老板，头儿
High Horse 傲慢，趾高气扬的架势
Hold Your Horses 不要操之过急，等一下，别着急
Hot Cakes 卖得非常快，十分畅销

I
If I Had a Nickel for Every Time 比喻好多次
In the Driver’s / Driving Seat 处于主导地位，担任负责人，控制局势，左右/掌控一切
In the Pink 身体健康，气色好
It Goes in One Ear and out the Other. 左耳朵进，右耳朵出
It’s Always Greener on the Other Side. 这山望着那山高，别处的草儿更绿，得陇望蜀

J
Jack of All Trades 多面手，博而不精的人

K
Keep One’s Nose out of 别管闲事，不要干涉别人的事
Keep Your Shirt on 请镇定，稍安勿躁
Kick Butt / Ass 很厉害，很棒

L
Let Sleeping Dogs Lie 别惹麻烦，别多事，别惹是非
Let the Cat out of the Bag 泄露秘密，露出马脚，说漏嘴
(Like a Bolt) out of / from the Blue 突如其来，从天而降，出其不意
Like a Duck to Water 如鱼得水
Look What the Cat Coughed up / Dragged in 瞧瞧什么人来了

M
Make Ends Meet 勉强度日，勉强糊口
Make Waves 有所作为，出人头地；兴风作浪
Million Dollar Question 很难回答的问题
Miss the Boat 错失良机，无法了解
Monkey Business 不正经的事情，不规矩的事情

N
Name Is Mud 名誉扫地，声名狼藉
Nip in the Bud 把……扼杀于萌芽状态，防患于未然
No Shit 别废话，别扯淡；不带扯的，真的
No Skin off One’s Nose 跟本人毫不相干，本人不在乎
Nosy Parker 好事者，爱管闲事的人
Not a Bed of Roses 不轻松安逸，不尽如人意
Not Know sb. from Adam 根本就不认识某人，压跟儿就不认识某人

O
Off the Sauce 戒酒
On a Silver Platter 轻易地，不费劲地
On One’s Toes 保持警觉，随时准备行动
On the Rebound （感情）处于疗伤期
On the Wagon 戒酒
Once in a Blue Moon 破天荒，极其罕见，千载难逢
One Foot in the Grave 行将就木，处于危险之中
Open a Can of Worms 自找烦恼
Out of the Woods 走出困境，摆脱危险

P
Pandora’s Box 灾祸的根源或源头
Pass the Hat 捐款，筹钱
Peaches and Cream 完美无缺的，美好的
Pick sb.’s Brain 向某人询问消息，征求意见，向某人取经
Pipe Dream 白日梦，幻想，空想
Play Ball 合作，互相帮忙
Play sth. by Ear 随机应变，见机行事
Prince Charming 白马王子
Prodigal Son 回头的浪子，改邪归正的人
Pull the Wool over sb.’s Eyes 故意欺骗某人，蒙骗某人
Puppy Love / Calf Love （青涩年代的）初恋
Put All (One’s) Eggs in One Basket 孤注一掷
Put One’s Foot in One’s Mouth 不小心说错话，不会说话
Put One’s Money Where One’s Mouth Is 拿钱来证实，用行动来证明
Put / Get the Cart before the Horse 本末倒置，主次不分，颠倒次序

R
Reap the Whirlwind 遭到恶报，得到报应
Red Carpet 隆重接待
Red Herring 转移别人注意力的东西，障眼法
Red-letter Day 值得纪念的日子
Ring a Bell 提醒，想起来
Rock the Boat 兴风作浪，破坏现状，惹事生非

S
Salad Days少不更事的青涩时代，年轻缺乏经验时期，最佳时期，全盛时期
Saved by the Bell 如释重负，终于解脱了
Sb.’s Eyes Are Bigger than His Stomach / Belly 眼睛大，肚子小；眼高手低
Second Thought 再三考虑，认真思索
Sell One’s Soul 出卖自己的灵魂
Shake a Leg 快点，赶紧
Shoot from the Hip （行事或者说话）鲁莽，直来直去，冲动
Shoot the Breeze 瞎聊
Shotgun Wedding 奉子成婚
Show sb. the Ropes 告诉某人诀窍，告知某人内情
Speak of the Devil 说曹操，曹操到
Spill the Beans 泄漏秘密，泄密
Split Hairs 斤斤计较，吹毛求疵，钻牛角尖
Stand sb. up 放某人鸽子，爽约
Steal sb.’s Thunder 抢某人的风头，抢某人的功劳
Step on sb.’s Toes 得罪某人，触犯某人，侵犯某人的领地或职权
Strong Suit 长处，特长
Swan Song 最后的事物，临终遗言，最后的作品

T
Take a Rain Check 下次吧，改天吧，以后吧
Take French Leave 不辞而别，擅自缺席
Take over the Reins 主持大局，掌握支配权
Take the Bull by the Horns 不畏艰险，勇敢面对困难
Take the Cake 得头奖，得第一名（最佳或最差）
Take the Rap （替别人）背黑锅，（因某事）无辜受罚
Talk sb.’s Ear off 喋喋不休，唠叨，费尽口舌
That’s the Way the Cookie Crumbles. 这就是命，人生就是这样，这是无法改变的事实
The Call of Nature 想小便
The Cat Gets sb.’s Tongue 不吭声，不说话
The Salt of the Earth 诚实、善良的普通人
Think on sb.’s Feet （头脑）反应快，不用想也知道
Third Degree 拷问，逼问，逼供
Three Sheets in / to the Wind 酩酊大醉
Throw / Cast / Fling Caution to the Winds 不顾一切冒险行事
Throw in the Sponge / Towel 认输
Tie the Knot 结婚，主持婚礼
Tilt at Windmills 浪费时间和精力与假想中的敌人搏斗
Touch Wood 但愿好运常在
Turn in One’s Grave 死不暝目

U
Under the Gun 承受很大的压力
Use Your Head 你用用脑子；你动动脑子，好好想一想

W
Walls Have Ears 隔墙有耳（，小心被人听见了）
Wash One’s Hands of 一刀两断，撒手不管，抛开
Wet One’s Whistle 喝酒
White Hope 被支持者们寄予希望能获得巨大成功的人
White Lie 善意的谎言，无伤大雅的谎言
Word of Mouth 口耳相传
Worth sb.’s Salt 称职的，胜任工作的

Y
You Haven’t Even Gotten Your Feet Wet. 你（要做某件事情，）却根本就没有开始呢

英语学术论文常用句型[zz]

2010-08-19T22:18:00.001+01:00

    Beginning
    1. In this paper, we focus on the need for
    2. This paper proceeds as follow.
    3. The structure of the paper is as follows.
    4. In this paper, we shall first briefly introduce fuzzy sets and related concepts
    5. To begin with we will provide a brief background on the

    Introduction
    1. This will be followed by a description of the fuzzy nature of the problem and a detailed presentation of how the required membership functions are defined.
    2. Details on xx and xx are discussed in later sections.
    3. In the next section, after a statement of the basic problem, various situations involving possibility knowledge are investigated: first, an entirely possibility model is proposed; then the cases of a fuzzy service time with stochastic arrivals and non fuzzy service rule is studied; lastly, fuzzy service rule are considered.

    Review
    1. This review is followed by an introduction.
    2. A brief summary of some of the relevant concepts in xxx and xxx is presented in Section 2.
    3. In the next section, a brief review of the .... is given.
    4. In the next section, a short review of ... is given with special regard to ...
    5. Section 2 reviews relevant research related to xx.
    6. Section 1.1 briefly surveys the motivation for a methodology of action, while 1.2 looks at the difficulties posed by the complexity of systems and outlines the need for development of possibility methods.

    Body
    1. Section 1 defines the notion of robustness, and argues for its importance.
    2. Section 1 devoted to the basic aspects of the FLC decision making logic.
    3. Section 2 gives the background of the problem which includes xxx
    4. Section 2 discusses some problems with and approaches to, natural language understanding.
    5. Section 2 explains how flexibility which often ... can be expressed in terms of fuzzy time window
    6. Section 3 discusses the aspects of fuzzy set theory that are used in the ...
    7. Section 3 describes the system itself in a general way, including the ….. and also discusses how to evaluate system performance.
    8. Section 3 describes a new measure of xx.
    9. Section 3 demonstrates the use of fuzzy possibility theory in the analysis of xx.
    10. Section 3 is a fine description of fuzzy formulation of human decision.
    11. Section 3, is developed to the modeling and processing of fuzzy decision rules
    12. The main idea of the FLC is described in Section 3 while Section 4 describes the xx strategies.
    13. Section 3 and 4 show experimental studies for verifying the proposed model.
    14. Section 4 discusses a previous fuzzy set based approach to cost variance investigation.
    15. Section 4 gives a specific example of xxx.
    16. Section 4 is the experimental study to make a fuzzy model of memory process.
    17. Section 4 contains a discussion of the implication of the results of Section 2 and 3.
    18. Section 4 applies this fuzzy measure to the analysis of xx and illustrate its use on experimental data.
    19. Section 5 presents the primary results of the paper: a fuzzy set model ..
    20. Section 5 contains some conclusions plus some ideas for further work.
    21. Section 6 illustrates the model with an example.
    22. Various ways of justification and the reasons for their choice are discussed very briefly in Section 2.
    23. In Section 2 are presented the block diagram expression of a whole model of human DM system
    24. In Section 2 we shall list a collection of basic assumptions which a ... scheme must satisfy.
    25. In Section 2 of this paper, we present representation and uniqueness theorems for the fundamental measurement of fuzziness when the domain of discourse is order dense.
    26. In Section 3, we describe the preliminary results of an empirical study currently in progress to verify the measurement model and to construct membership functions.
    27. In Section 5 is analyzed the inference process through the two kinds of inference experiments...

This Section
    1. In this section, the characteristics and environment under which MRP is designed are described.
    2. We will provide in this section basic terminologies and notations which are necessary for the understanding of subsequent results.Next Section
    2. The next section describes the mathematics that goes into the computer implementation of such fuzzy logic statements.
    3. However, it is cumbersome for this purpose and in practical applications the formulae were rearranged and simplified as discussed in the next section.
    4. The three components will be described in the next two section, and an example of xx analysis of a computer information system will then illustrate their use.
    5. We can interpret the results of Experiments I and II as in the following sections.
    6. The next section summarizes the method in a from that is useful for arguments based on xx

    Summary
    1. This paper concludes with a discussion of future research consideration in section 5.
    2. Section 5 summarizes the results of this investigation.
    3. Section 5 gives the conclusions and future directions of research.
    4. Section 7 provides a summary and a discussion of some extensions of the paper.
    5. Finally, conclusions and future work are summarized
    6. The basic questions posed above are then discussed and conclusions are drawn.
    7. Section 7 is the conclusion of the paper.

    Chapter 0. Abstract
    1. A basic problem in the design of xx is presented by the choice of a xx rate for the measurement of experimental variables.
    2. This paper examines a new measure of xx in xx based on fuzzy mathematics which overcomes the difficulties found in other xx measures.
    3. This paper describes a system for the analysis of the xx.
    4. The method involves the construction of xx from fuzzy relations.
    5. The procedure is useful in analyzing how groups reach a decision.
    6. The technique used is to employ a newly developed and versatile xx algorithm.
    7. The usefulness of xx is also considered.
    8. A brief methodology used in xx is discussed.
    9. The analysis is useful in xx and xx problem.
    10. A model is developed for a xx analysis using fuzzy matrices.
    11. Algorithms to combine these estimates and produce a xx are presented and justified.
    12. The use of the method is discussed and an example is given.
    13. Results of an experimental applications of this xx analysis procedure are given to illustrate the proposed technique.
    14. This paper analyses problems in
    15. This paper outlines the functions carried out by ...
    16. This paper includes an illustration of the ...
    17. This paper provides an overview and information useful for approaching
    18. Emphasis is placed on the construction of a criterion function by which the xx in achieving a hierarchical system of objectives are evaluated.
    19. The main emphasis is placed on the problem of xx
    20. Our proposed model is verified through experimental study.
    21. The experimental results reveal interesting examples of fuzzy phases of: xx, xx
    22. The compatibility of a project in terms of cost, and xx are likewise represented by linguistic variables.
    23. A didactic example is included to illustrate the computational procedure

    Chapter 1. Introduction
    Time
    1. Over the course of the past 30 years, .. has emerged form intuitive
    2. Technological revolutions have recently hit the industrial world
    3. The advent of ... systems for has had a significant impact on the
    4. The development of ... is explored
    5. During the past decade, the theory of fuzzy sets has developed in a variety of directions
    6.The concept of xx was investigated quite intensively in recent years
    7. There has been a turning point in ... methodology in accordance with the advent of ...
    8. A major concern in ... today is to continue to improve...
    9. A xx is a latecomer in the part representation arena.
    10. At the time of this writing, there is still no standard way of xx
    11. Although a lot of effort is being spent on improving these weaknesses, the efficient and effective method has yet to be developed.
    12. The pioneer work can be traced to xx [1965].
    13. To date, none of the methods developed is perfect and all are far from ready to be used in commercial systems.

    Objective / Goal / Purpose
    1. The purpose of the inference engine can be outlined as follows:
    2. The ultimate goal of the xx system is to allow the non experts to utilize the existing knowledge in the area of manual handling of loads, and to provide intelligent, computer aided instruction for xxx.
    3. The paper concerns the development of a xx
    4. The scope of this research lies in
    5. The main theme of the paper is the application of rule based decision making.
    6. These objectives are to be met with such thoroughness and confidence as to permit ...
    7. The objectives of the ... operations study are as follows:
    8. The primary purpose/consideration/objective of
    9. The ultimate goal of this concept is to provide
    10. The main objective of such a ... system is to
    11. The aim of this paper is to provide methods to construct such probability distribution.
    12. In order to achieve these objectives, an xx must meet the following requirements:
    13. In order to take advantage of their similarity
    14. more research is still required before final goal of ... can be completed
    15. In this trial, the objective is to generate...
    16. for the sake of concentrating on ... research issues
    17. A major goal of this report is to extend the utilization of a recently developed procedure for the xx.
    18. For an illustrative purpose, four well known OR problems are studied in presence of fuzzy data: xx.
    19. A major thrust of the paper is to discuss approaches and strategies for structuring ..methods
    20. This illustration points out the need to specify
    21. The ultimate goal is both descriptive and prescriptive.
    22. Chapter 2. Literature Review
    23. A wealth of information is to be found in the statistics literature, for example, regarding xx
    24. A considerable amount of research has been done .. during the last decade
    25. A great number of studies report on the treatment of uncertainties associated with xx.
    26. There is considerable amount of literature on planning
    27. However, these studies do not provide much attention to uncertainty in xx.
    28. Since then, the subject has been extensively explored and it is still under investigation as well in
    methodological aspects as in concrete applications.
    29. Many research studies have been carried out on this topic.
    30. Problem of xx draws recently more and more attention of system analysis.
    31. Attempts to resolve this dilemma have resulted in the development of
    32. Many complex processes unfortunately, do not yield to this design procedure and have, therefore, not yet been automated.
    33. Most of the methods developed so far are deterministic and /or probabilistic in nature.
    34. The central issue in all these studies is to
    35. The problem of xx has been studied by other investigators, however, these studies have been based upon classical statistical approaches.
    36. Applied ... techniques to
    37. Characterized the ... system as
    38. Developed an algorithm to
    39. Developed a system called ... which
    40. Uses an iterative algorithm to deduce
    41. Emphasized the need to
    42. Identifies six key issues surrounding high technology
    43. A comprehensive study of the... has been undertaken
    44. Much work has been reported recently in these filed
    45. Proposed/Presented/State that/Described/Illustrated/
    Indicated/Has shown / showed/Address/Highlights
    46. Point out that the problem of
    47. A study on ...was done / developed by []
    48. Previous work, such as [] and [], deal only with
    49. The approach taken by [] is
    50. The system developed by [] consists
    51. A paper relevant to this research was published by []
    52. []'s model requires consideration of...
    53. []' model draws attention to evolution in human development
    54. []'s model focuses on...
    55. Little research has been conducted in applying ... to
    56. The published information that is relevant to this research...
    57. This study further shows that
    58. Their work is based on the principle of
    59. More history of ... can be found in xx et al. [1979].
    60. Studies have been completed to established
    61. The ...studies indicated that
    62. Though application of xx in the filed of xx has proliferated in recent years, effort in analyzing xx, especially xx, is lacking.
    Problem / Issue / Question
    63. Unfortunately, real-world engineering problems such as manufacturing planning do not fit well with this narrowly defined model. They tend to span broad activities and require consideration of multiple aspects.
    64. Remedy / solve / alleviate these problems
    67. ... is a difficult problem, yet to be adequately resolved
    68. Two major problems have yet to be addressed
    69. An unanswered question
    70. This problem in essence involves using x to obtain a solution.
    71. An additional research issue to be tackled is ....
    72. Some important issues in developing a ... system are discussed
    73. The three prime issues can be summarized:
    74. The situation leads to the problem of how to determine the ...
    75. There have been many attempts to
    76. It is expected to be serious barrier to
    77. It offers a simple solution in a limited domain for a complex

track from:http://blog.renren.com/share/244036495/3052373980

应该脱口而出的英语口语[zt]

2010-07-14T11:03:00.001+01:00

人人网校内- 日志分享

Any day will do？哪一天都可以？

　　Any messages for me？有我的留言吗？

　　Are you by yourself？你一个人来吗？

　　All right with you？你没有问题吧？

　　Are you free tomorrow？明天有空吗？

　　Are you kidding me？你在跟我开玩笑吧？

　　As soon as possible！尽可能快！

　　Back in a moment！马上回来！

　　Believe it or not！信不信由你！

　　Better luck next time！下次会更好！

　　Boy will be boys本性难移！

　　Come to the point！有话直说！

　　Do you accept plastic？收不收行用卡？

　　Does it keep long？可以保存吗？

　　Don't be so fussy！别挑剔了！

　　Don't count to me！别指望我！

　　Don't fall for it！不要上当！

　　Don't get me wrong！你搞错了！

　　Don't give me that！少来这套！

　　Don't let me down！别让我失望！

　　Don't lose your head！别乐昏了头！

　　Don't over do it！别做过头了！

　　Don't sit there daydreaming！别闲着做白日梦！

　　Don't stand on ceremony！别太拘束！

　　Drop me a line！要写信给我！

　　Easy come easy go！来得容易去得也快！

　　First come first served！先到先得！

　　Get a move on！快点吧！

　　Get off my back！不要嘲笑我！

　　Give him the works！给他点教训！

　　Give me a break！饶了我吧！

　　Give me a hand！帮我一个忙！

　　Great minds think alike！英雄所见略同！

　　I'll treat you to lunch.午餐我请你！

　　In one ear，out the other ear.一耳进，一耳出！

　　I'm spaced-out！我开小差了！

　　I beg your pardon！请你再说一遍！

　　I can't afford that！我付不起！

　　I can't follow you！我不懂你说的！

　　I can't help it！我情不自禁！

　　I couldn't reach him！我联络不上他！

　　I cross my heart！我发誓是真的！

I don't mean it！我不是故意的！

　　I feel very miserable！我好沮丧！

　　I have no choice！我别无选择了！

　　I watch my money！视财如命！

　　I'll be in touch！保持联络！

　　I'll check it out！我去看看！

　　I'll show you around！我带你四处逛逛！

　　I'll see to it！我会留意的！

　　I'm crazy for you！我为你疯狂！

　　You make me jump！你下了我一跳！

　　Make up your mind.作个决定吧！

　　Make yourself at home！就当在家一样！

　　My mouth is watering！我要流口水了！

　　Never heard of it！没听说过！

　　Nice talking to you！很高兴和你聊天！

　　No doubt about it！勿庸置疑！

　　No pain no gain！不经一事，不长一智！

　　None of your business！要你管？

　　There is nothing on your business！这没你的事！

　　Now you are really talking！说得对！

　　Please don't rush me！请不要吹促我！

　　Please keep me informed！请一定要通知我！

　　She looks blue today.她今天很忧郁！

　　She is under the weather.她心情不好！

　　So far，so good.过得去。

　　Speaking of the devil！一说曹操，曹操就到！

　　Stay away from me！离我远一点！

　　Stay on the ball！集中注意力！

　　That makes no difference.不都一样吗？

　　That's a touchy issue！这是个辣手得问题！

　　That's always the case！习以为常！

　　That's going too far！这太离谱了！

　　That's more like that！这才象话嘛！

　　The answer is zero！白忙了！

　　The dice is cast！已成定局了！

　　The same as usual！一如既往！

　　The walls have ears！隔墙有耳！

　　There you go again！你又来了！

　　Time is running out！没有时间了！

We better get going！最好马上就走！

Absence makes the heart grow fonder. 小别胜新婚。
After you．您先。
Allow me．让我来。
Any day will do．哪一天都行夕
Any messages for me? 有我的留言吗?
Any thing else? 还要别的吗?
Any urgent thing？有急事吗？
Are you kidding? 你在开玩笑吧!
Are you sure? 你肯定吗?
As soon as possible! 越快越好!
Be careful! 注意!
Be quiet! 安静点!
Believe it or not! 信不信由你!
Between us. 你知，我知。
Big mouth! 多嘴驴！
Bless you! 祝福你!
Bottle it! 閉嘴！
Bottoms up! 干杯！
Bottoms up! 干杯(见底)!
Boy! （表示惊奇，兴奋等）哇！好家伙！
Break the rules. ?#;反規則。
Break the rules. 违反规则。
Can I have this. 可以给我这个吗？
Can I help you? 我能帮你吗?
Can you dig it？你搞明白了吗？
Can－do. 能人。
Cheap skate! 小气鬼！
Cheer up! 振作起来!
Chin up. 不气，振作些。
Close－up. 特寫鏡頭。
Clothes make the man．人要衣装。
Come on! 快点，振作起来！
Come on, be reasonable. 嗨，你怎么不讲道理。
Come on．来吧(赶快)
Come seat here. 来这边坐。
Congratulations! 祝贺你!
Control yourself! 克制一下!
Count me on 算上我。
Daring! 亲爱的！
Dead end. 死胡同。
December heartbeat. 黄昏恋。
Did you miss the bus? 你错过公共汽车了?
Dinner is on me. 晚饭我请。
Do l have to 非做不可吗?
Do me a favor? 帮个忙，好吗?
Do you have any money on you？你身上带钱了吗？
Do you have straw？你有吸管吗？
Does it serve your purpose？对你有用吗？
Doggy bag. 打包袋。
Don't be so childish. 别这么孩子气。
Don't be so modest．别谦虚了。
Don't count on me．别指望我。
Don't fall for it! 别上当!
Don't flatter me. 过奖了。
Don't get high hat. 别摆架子。
Don't get loaded. 别喝醉了。
Don't get me wrong. 别误会我。
Don't give me that! 少来这套!
Don't let me down．别让我失望。
Don't let me down. 别让我失望。
Don't lose your head。不要惊慌失措。
Don't make up a story. 不要捏造事实。
Don't mention it. 没关系，别客气。
Don't move! 不许动!
Don't over do it. 别太过分了。
Don't play possum! 別裝蒜！
Don't push me. 别逼我。
Don't take ill of me. 别生我气。
Don't trust to chance! 不要碰运气。
Don't worry．别担心。
Drop it! 停止！
Easy come easy go．来得容易，去得快。
Easy does it. 慢慢来。
Enjoy yourself! 祝你玩得开心!
Excuse me，Sir．先生，对不起。
Fasten your seat belt．系好你的安全带。
Feel better? 好点了吗?
Follow me．跟我来。
Follow my nose. 凭直觉做某事。
Forget it! 休想! (算了!)
Fresh paint! 油漆未干！
Get an eyeful. 看个够。
Get cold feet. 害怕做某事。
Get out of here! 滚出去！
Gild the lily. 画蛇添足。
Give me a hand! 帮帮我!
Go ahead. 继续。
Go down to business. 言归正传。
God works. 上帝的安排。
Good for you! 好得很！
Good job! 做得好!
Good luck! 祝好运!
Good luck! 祝你好运！
Guess what? 猜猜看?
Hang on! 抓紧（别挂电话）！
Have a good of it.玩的很高兴。
Have fun! 玩得开心!
He always talks big．他总是吹牛。
He came by train．他乘火车来。
He can hardly speak．他几乎说不出话来。
He can't take a joke．他开不得玩笑。
He has a quick eye. 他的眼睛很锐利。
He has an ax to grind. 他另有企图。
He is a fast talker. 他是个吹牛大王。
He is a smart boy．他是个小机灵鬼。
He is ill in bed．他卧病在床。
He is just a child．他只是个孩子。
He is my age．他和我同岁。
He is the pain on neck. 他真让人讨厌。
He lacks courage．他缺乏勇气。
He neither drinks nor smokes. 他既不喝酒也不抽烟。
He neither drinks nor smokes. 他既不喝酒也不抽煙。
He owes my uncle $．他欠我叔叔美元。
He pushes his luck. 他太贪心了。
He won an election．他在选举中获胜。
Help me out. 帮帮我。
Help yourself．别客气。
Here we are! 我们到了！
Here ye! 说得对！
Here you are．给你。
High jack! 举起手来（抢劫）！
Hit the ceiling. 大发雷霆。
Hold on．等一等。
Hope so. 希望如此。
How about eating out？外面吃饭怎样？
How are things going? 事情进展得怎样?
How are you recently? 最近怎么样?
How big of you! 你真棒！
How big of you! 你真棒！
How come… 怎么回事，怎么搞的。
How much? 多少钱?
How's everything? 一切还好吧?
How's it going? 怎么样?
I agree。我同意。
I am a football fan．我是个足球迷。
I am all ears. 我洗耳恭听。
I am the one wearing pants in the house. 我当家。
I beg your pardon．请你原谅。
I beg your pardon? 请您再说一遍(我没有听清)。
I can't follow you．我不懂你说的。
I can't make both ends meet. 我上个月接不到下个月，缺钱。
I decline! 我拒绝!
I don't care. 我不在乎。
I don't have anywhere to be. 没地方可去。
I don't mean it. 我不是故意的。
I doubt it 我怀疑。
I felt sort of ill. 我感觉有点不适。
I have a good idea! 我有一个好主意。
I have no choice．我别无选择。
I have no idea．我没有头绪。
I have to be late and keep my date waiting. 我不喜欢迟到而让别人久等。
I just made it! 我做到了!
I know all about it．我知道有关它的一切。
I like ice-cream．我喜欢吃冰淇淋。
I lost my way. 我迷路了。
I love this game．我钟爱这项运动。
I love you! 我爱你!
I might hear a pin drop. 非常寂静。
I promise．我保证。
I quit! 我不干了!
I see．我明白了。
I stay at home a lot. 我多半在家里。
I swear by the god. 我对天发誓。
I think so．我也这么想。
I wonder if you can give me a lift？能让我搭一程吗？
If only I could fly．要是我能飞就好了。
I'll be back soon．我马上回来。
I'll be right there．我马上就到。
I'll be seeing you. 再见。
I'll check it out．我去查查看。
I'll fix you Up．我会帮你打点的。
I'll get even with him one day. 我总有一天跟他扯平
I'll see to it 我会留意的。
I'll see you at six．我六点钟见你。
I'll try my best．我尽力而为。
I'm afraid I can't. 我恐怕不能。
I'm bored to death. 我无聊死了。
I'm dying to see you. 我很想见你。
I'm full．我饱了。
I'm going to go. 我這就去。
I'm his fan。我是他的影迷。
I'm home．我回来了。
I'm in a hurry! 我在赶时间!
I'm lost．我迷路了。
I'm not going. 我不去了。
I'm not it a good mood. 没有心情（做某事）。
I'm on a diet．我在节食。
I'm On your side．我全力支持你。
I'm single．我是单身贵族。
IS it true or false? 这是对的还是错的?
Is it yours? 这是你的吗?
Is that so？是这样吗？
It can be a killer. 这是个伤脑筋的问题。
It doesn't make any differences. 没关系。
It doesn't take much of you time. 这不花你好多时间。
It doesn't work. 不管用。
It is a deal！一言为定！
It is a long story. 一言难尽。
It is a small world! 世界真是小！
It is growing cool．天气渐渐凉爽起来。
It is not a big deal! 没什么了不起！
It is of high quality. 它质量上乘。
It is raining. 要下雨了。
It is urgent. 有急事。
It really takes time．这样太耽误时间了。
It seems all right．看来这没问题。
It sounds great!．听起来很不错。
It was something that happens once in the blue moon. 这是千载难逢的事。
It’s a long story．说来话长。
It’s Sunday today．今天是星期天。
It's a fine day。今天是个好天。
It's against the law．这是违法的。
It's going too far．太离谱了。
It's her field．这是她的本行。
It's up in the air. 尚未确定。
It's up to you. 由你决定。
It's up to you．由你决定。
Just read it for me．就读给我听好了。
Just wait and see! 等着瞧!
Just wonderful! 简直太棒了!
Keep in Touch．保持联络。
Keep it up! 坚持下去!
Knowledge is power．知识就是力量。
Leave me alone. 别理我。
Let go! 放手!
Let me see．让我想想。
Let's bag it. 先把它搁一边。
Let's play it by ear. 让我们随兴所至。
Long time no see! 好久不见!
Lose head. 丧失理智。
Love me，love my dog． (谚语)爱屋及乌。
Make it up! 不记前嫌！
Make it. 达到目的，获得成功。
Make up your mind．做个决定吧。
May I use your pen? 我可以用你的笔吗?
Me too．我也是。
Move out of my way! 让开!
My girlfriend and I broke up. 我和我的女朋友吹了。
My god! 天哪!
My hands are full right now. 我现在很忙。
My mouth is watering．我要流口水了。
My treat．我请客。
Never mind. 不要緊。
Never mind．不要紧。
No one knows . 没有人知道。
No pain，no gain．不劳无获。
No problem! 没问题!
No way! 不可能！
No way! 不行!
None of my business. 不关我事。
None of you keyhole. 不准偷看。
Not at all. 根本就不（用）。
Not bad．还不错。
Not in the long run. 从长远来说不是这样的。
Not precisely! 不见得，不一定！
Not so bad. 不错。
Not yet．还没。
Nothing tricky. 别耍花招。
Nuts! 呸；胡说；混蛋！
Nuts! 呸；胡說；混蛋
Of course! 当然了!
Play hooky. 旷工、旷课。
Poor thing! 真可怜！
Poor thing! 真可憐！

Price is soaring, if it goes on like this, we shall not be able to keep the pot boiling. 物价直线上升，这样子下去，我们锅里可没什么东西煮饭。
Right over there. 就在那里。
Say hello to everybody for me. 替我向大家问好。
See you．再见。
She had a bad cold．她患了重感冒。
She is still mad at me. 她还在生我的气。
She make a mess of things. 她把事情搞得一塌糊涂。
She'll be along in a few minutes. 他马上会过来。
She's got quite a wad. 她身怀巨款。
Shoot the breeze. 闲谈。
Shut up! 闭嘴!
Side dish. 配菜。
Sleeping on both ears. 睡的香。
Slow down! 慢点!
So do I．我也一样。
So far，So good．目前还不错。
So long．再见。
Speak louder，please．说话请大声点儿。
Stay away from him. 别*近他。
Still up？还没睡呀？
Sure thin! 當然！
T can't help it. 我情不自禁。
Take a seat! 请坐！
Take care! 保重!
Take it easy．别紧张。
Talk truly. 有话直说。
Tell me when! 随时奉陪！
That is a boy! 太好了，好极了！
That is great! 太棒了！
That is unfair. 这不公平！
That rings a bell. 听起来耳熟。
That's a good idea．这个主意真不错。
That's all I need．我就要这些。
That's all! 就这样!
That's neat．这很好。
The answer is zero．白忙了。
The line is engaged. 占线。
The view is great．景色多么漂亮!
The wall has ears．隔墙有耳。
There comes a bus．汽车来了。
There is nobody by that name working here. 这里没有这个人。
There is nobody by that name working here.這裡沒有這個人。
They hurt． (伤口)疼。
This boy has no job．这个男孩没有工作。
This house is my own．这所房子是我自己的。
This way。这边请。
Thousand times no! 绝对办不到！
Time is money．时间就是金钱。
Time is running out．没时间了。
Time is up．时间快到了。
To be careful! 一定要小心!
Try again．再试试。
Wait and see. 等着瞧。
Watch out! 当心。
Watch you mouth. 注意言辞。
We are good friends．我们是好朋友。
We have no way out. 我们没办法。
Well，it depends 噢，这得看情况。
We're all for it．我们全都同意。
What a good deal! 真便宜!
What a pity! 太遗憾了!
What about you? 你呢?
What brought you here？什么风把你吹来了？
What day is today? 今天星期几?
What do you think? 你怎么认为？
What does she like? 她喜欢什么?
What happened to you? 你怎么了?
What if I go for you？我替你去怎么样？
What is the fuss？吵什么？
What is you major？你学什么专业？
What should I do? 我该怎么办？
What time is it? 几点了?
What's new? 有什么新鲜事吗?
What's up? 有什么事吗?
What's your trouble? 你哪儿不舒服?
When are you leaving？你什么时候走？
Who knows! 天晓得！
Who told you that? 谁告诉你的?
Who wants？谁稀罕？
Who's calling? 是哪一位?
Who's kicking off? 现在是谁在开球?
Why are you so sure？怎么这样肯定？
Why die she marry a man old enough to be her father？她为什么要嫁给一个年龄与她父亲相当的男人？
Why not? 好呀! (为什么不呢?)
Why so blue？怎么垂头丧气？
Would you mind making less noise? 能不能小声点。
Yes，I suppose So．是的，我也这么认为。
You are just in time. 你来得正是时候。
You are welcome! 别客气！
You ask for it! 活该！
You asked for it! 你自讨苦吃!
You bet! 一定，当然！
You can make it! 你能做到!
You can't miss it 你一定能找到的。
You did fairly well! 你干得相当不错
You did right．你做得对。
You don't say so. 未必吧，不至于这样吧。
You don't say! 真想不到！
You don't seem to be quite yourself today. 你今天看起来不大对劲。
You have my word．我保证。
You might at least apologize. 你顶多道个歉就得了。
You need to workout．你需要去运动锻炼一下。
You never know. 世事难料。
You owe me one．你欠我一个人情。
You set me up! 你出卖我!
You want a bet？你想打赌吗？
Your are welcome. 你太客气了。
Your hand feels cold．你的手摸起来很冷。。
You're welcome．不客气。

久仰！I've heard so much about you.

好久不见了！Long time no see.

辛苦了！You've had a long day. You've had a long flight.

尊敬的朋友们！Distinguished/Honorable/Respected friends

阁下(多用于称呼大使) Your Excellency

我代表北京市政府欢迎各位朋友访问北京。On behalf of the Beijing Municipal government, I wish to extend our warm welcome to the friends who have come to visit Beijing.

对您的大力协助，我谨代表北京市政府表示衷心的感谢。On behalf of the Beijing Municipal government, i wish to express our heartfelt thanks to you for your gracious assistance.

在北京过得怎么样？How are you making out in Beijing?

我一定向他转达您的问候和邀请。I'll surely remember you and your invitation to him.

欢迎美商来北京投资。American businessmen are welcome to make investment in Beijing.

欢迎多提宝贵意见。Your valuable advice is most welcome.

不虚此行! It's a rewarding trip!

您的日程很紧,我们的会见是否就到此为止。As you have a tight schedule, I will not take up more of your time.

请代我问候王先生。Please remember me to Mr.Wang.

感谢光临！Thank you so much for coming.

欢迎再来！Hope you'll come again.

欢迎以后多来北京！Hope you'll visit Beijing more often.

请留步，不用送了！I will see myself out, please.

多保重！Take care!

祝您一路平安！Have a nice trip!

愿为您效劳！At your service!

为…举行宴会/宴请Host a dinner/banquet/luncheon in honor of …

欢迎宴会Welcome dinner

便宴Informal dinner

午宴(附有情况介绍或专题演讲等内容)Luncheon

便餐Light meal

工作午餐Working luncheon

自助餐 Buffet dinner/luncheon

答谢宴会Return dinner

告别宴会Farewell dinner

庆功宴Glee feast

招待会Reception

庆祝中华人民共和国成立四十五周年招待会Reception Celebrating the 45th Anniversary of the Founding of the People's Republic of China

鸡尾酒会Cocktail party

茶话会Tea party

包餐/点餐Table d'hote/a la carte

上菜Serve a courst

您的位置在这里。Here is your seat.

请入席！Please have a seat.

欢聚一堂Enjoy this happy get-together

请随便！Please yourself at home./Please enjoy yourself.

请各位随意用餐。Help yourself please.

您喝点什么？What would you like to drink?

现在我提议，为了…和…之间的合作，为了…参议员的健康，干杯！At this point, I propose a toast: to the cooperation between … And … , to the health of Senator…, cheers!

最后，我借主人的酒，提议为…干杯！Lastly, taking up this glass of fine wine, I propose a toast to …

请各位举杯并同我一起为所有在座的朋友们的健康干杯！I'd ask you to raise your glass and join me in a toast ot the health of all our friends present here.

敬您一杯！Here's to you!

祝你健康！To your health!

我要为此干杯！I'll drink to that!

随量！Whatever you like!

我失陪一会儿！Excuse me for a minute.

菜不好，请多多包涵！Hope you enjoy yourself.

女士们先生们，欢迎各位光临，演出很快就要开始了，请尽快就坐。Ladies and gentlemen, good evening. The concert/show would start soon. Please get yourself seated. Thank you.

招待会现在开始。The reception will now begin.

全体起立，奏国歌！All rise please. For the P.R.C.National Anthem!

出席今天招待会的贵宾有…The distinguished guests paarticipating the reception are …

现在请…讲话I have the honour to call upon …

开幕式现在结束。This concludes the opening ceremony.

隆重庆祝Grand celebration

庆祝成立…一周年Celebrating the 1st Anniversary of the Establishment of …

热烈祝贺第一届…锦标赛Hail the first FIFA of …

值此节日之际致以节日的祝贺！On the occasion of the season, I would like to extend season's greetings.

祝您工作顺利、事业成功、身体健康、家庭幸福！Wish you the very best of luck in your job, every success in your future endeavours, good health and a happy family!

衷心祝贺您当选…Hearty congratulations on your recent election as …

举行会议/研讨会/大会/座谈会/学术报告会Hold a meeting/seminar/conference/forum/symposium

赞助人/主办人/承办人/协办人Patron/sponsor/organizer/co-organizer

举行谈判Enter into negotiation

交涉Make representations with sb. On sth./deal with sb.

事物性会谈Talks at working level

对口会谈Counterpart talks

议程项目Items on the agenda

主题Theme

议题Topic for discussion

双方商定的议程Schedule mutually agreed upon

开幕会议 Opening session

全体会议Plenary session

开场白Introduction

情况介绍Presentation

小组讨论Panel discussion

同有关单位磋商Hold consultations with the organizations concerned

一轮会谈One round of talks

决议Resolution

谅解备忘录Memorandum of understanding

现在开会。I declare the meeting open.

请…发言。I invite the representative of …To take the floor.

下面我给各位简要介绍一下北京的经济情况Now I would like to give you a brief overview of Beijing's economy.

我的介绍完了，谢谢！That's all for my presentation. thank you.

我先说这么多。So much for my remarks for now.

我要说的就是这些。That's all for what I want to say.

您看是先谈原则问题呢，还是先谈具体问题？I wonder if you would like to start with matters of principle or specific issues?

让我先谈一个问题。If you agree(With your permission), let me start with one issue

在谈那个问题之前我想对您刚才讲的话谈点看法。Before we turn to that issue, I wish to make a few comments/remarks on your presentation.

您对此事怎么看呢？I wish to benefit from your views on this matter./ What is your view on this matter?/ How do you see this matter?

我提议休会十分钟。I propose a ten-minute break.

我想接着刚才的问题讲下去。I will pick up where we left off just now.

对不起，我插一句。Sorry for the interruption but

当然可以！By all means.

怎么都行！Whatever you say.

我没有异议。I have no objection.

我方对这个问题有异议。We take exception to this question.

我们高兴地看到…We note with pleasure that …

这个日期贵方觉得合适吗？I wonder if this date would be suitable for you?

不知你们上午谈的怎样？I wonder how the meeting went this morning?

我方很希望贵方能尽早给予肯定的答复。We would greatly appreciate it if you could give us your favourable and prompt commitment as soon as possible.

请你们务必在8月1日前提出意向书。You are kindly requested to submit the letter of intent on the date no later than 1st August.

纠缠这个问题。Entangle this issue.

提倡节约Advocate/uphold thriftiness

为了国家的繁荣For the sake of national property

经受了时间考验的友谊给我留下了很深的印象。The time-tested friendship leave me a deep impression.

密切注视Keep close watch on

促进密切合作Spur/promote intensive cooperation

Karate Kid

2010-06-27T17:27:00.001+01:00

if you want to know more of Beijing, go to see that film.
all famous place of interests are there for you to explore.
but it's so sad to know Jacky Chen is old.
one sentence is worth remembering.
kong fu is everywhere in you daily life.you can find it even in your jacket.
that's brilliant.

很有教养的英语口语zz

2010-06-19T15:15:00.001+01:00

1. After you. 你先请。

这是一句很常用的客套话，在进／出门,上车得场合你都可以表现一下。

2. I just couldn’t help it. 我就是忍不住。

想想看，这样一个漂亮的句子可用于多少个场合？

下面是随意举的一个例子：

I was deeply moved by the film and I cried and cried. I just couldn’t help it.

3. Don’t take it to heart. 别往心里去，别为此而忧虑伤神。

生活实例：
This test isn’t that important. Don’t take it to heart.

4. We’d better be off. 我们该走了。

It’s getting late. We’d better be off .

5. Let’s face it. 面对现实吧。

常表明说话人不愿意逃避困难的现状。

参考例句：I know it’s a difficult situation. Let’s face it, OK?

6. Let’s get started. 咱们开始干吧。

劝导别人时说：Don’t just talk. Let’s get started.

7. I’m really dead. 我真要累死了。

坦诚自己的感受时说：After all that work, I’m really dead.

8. I’ve done my best. 我已尽力了。

9. Is that so? 真是那样吗？

常用在一个人听了一件事后表示惊讶、怀疑。

10. Don’t play games with me!别跟我耍花招！

11. I don’t know for sure.我不确切知道。

Stranger： Could you tell me how to get to the town hall?

Tom: I don’t know for sure. Maybe you could ask the policeman over there.

12. I’m not going to kid you.我不是跟你开玩笑的。

Karin： You quit the job? You are kidding.

Jack: I’m not going to kid you. I’m serious.

13. That’s something. 太好了，太棒了。

A: I’m granted a full scholarship for this semester.

B: Congratulations. That’s something.

14. Brilliant idea!这主意真棒！这主意真高明！

15. Do you really mean it? 此话当真？

Michael：Whenever you are short of money, just come to me.

David: Do you really mean it?

16. You are a great help.你帮了大忙

17. I couldn’t be more sure. 我再也肯定不过。

18. I am behind you.我支持你。

A: Whatever decision you’re going to make, I am behind you.

19. I’m broke.我身无分文。

20. Mind you!请注意！听着！(也可仅用Mind。)

模范例句：Mind you! He’s a very nice fellow though bad-tempered.

21. You can count on it.你尽管相信好了，尽管放心。

A：Do you think he will come to my birthday party?
B: You can count on it.

22. I never liked it anyway.我一直不太喜欢这东西。

当朋友或同事不小心摔坏你的东西时就可以用上这句话给他一个台阶，打破尴尬局面：Oh, don’t worry. I’m thinking of buying a new one. I never liked it anyway.

23. That depends.看情况再说。

例：I may go to the airport to meet her. But that depends.

　Congratulations.恭喜你，祝贺你。

24. Thanks anyway.无论如何我还是得谢谢你。

当别人尽力要帮助你却没帮成时，你就可以用这个短语表示谢意。

25. It’s a deal.一言为定

Harry： Haven’t seen you for ages. Let’s have a get-together next week.

Jenny: It’s a deal

track back：http://www.kaixin001.com/!repaste/detail.php?uid=3855991& urpid=2250346508

在外企混一定要懂的潜台词[zz]

2010-06-09T21:23:00.001+01:00

老外的想法做法就是不一样，如果你想在外企混得好，有些潜规则你最好心里有数。
　　
　　Unacceptable:老外打小受的教育是人要以表扬鼓励为主,所以老外批评人比较含蓄.说你这件事办的unacceptable,已经算是说的很重了,中国老板在外企混久了,也便跟着装逼起来,对你不满,写email给你,左一个unacceptable右一unacceptable，潜台词相当于:你这个傻逼,你奶奶个熊,给老子小心点,X你妈的,等等.
　　
　　CC:就是Copy.我看email,第一看标题,第二看CC给谁,第三才看内容.CC给谁基本上能够说明对方的态度,CC一大批老板的,肯定不是啥好事,对方要推卸责任.潜台词:我这件事告诉你了哦,和我没关系了,你自己看着办吧,反正老板都知道?都盯着你呢. 最开心的是看到自己的名字在CC那一栏里面,因为那意味着那就是这封信不用回,看看就可以.有人会回的.
　　
　　Concern:中文翻译成"关注",其实根本不是关注的意思,老外要是说他很concern, 那就是事情不妙,所谓老外打喷嚏,中国人集体感冒。潜台词:老子很不爽,这事儿怎么这么乱七八糟,给我注意点!.
　　
　　Great:刚才说了,老外打小受教育要多夸人,少批评人,所以老外一天到晚把"It"s great!","you did a great job!"挂在嘴上,初听还飘飘然了几回,听久了,才知道其实压根儿就是他们口头禅,心里未必觉得你有多great,同义词还有fantastic! wonderful! Gorgeous! Fabulous!等等. 潜台词:还马马虎虎啦,一般般了,还过得去.
　　
　　F.Y.I:以前一直以为是forward邮件的时候系统会自动加上这几个字,因为人家转过来的信上都有这三个字母,过了好久才知道是人家自己加的,意思是:For Your Information.看到这几个字母意味着下面内容和我有关,但是关系不大,看看就好.因为对方如果要你采取行动,一定会说清楚:Allen,please……..而不会只是F.Y.I了事.潜台词:和你关系不大,给你随便看看.
　　
　　Issue:中文翻译成事情,其实是贬义词,准确意思是"不好的事情",老外说有一个issue,就是有件鸟事要处理.要有很多issue,那就是一团糟.潜台词:事情不妙,大家都赶快处理.
　　
　　Aggressive:中文翻译成"进攻性的",在外企里面意思含糊,褒义的有"具有开拓精神的","有事业心的",贬义的有"咄咄逼人的","喜欢没头脑乱闯的","容易得罪别人的",反正意思可褒可贬,看你自己琢磨. 面试时候说自己"aggressive"的,潜台词是:我可不是那种混日子的人,我是能干事的,招我准没错. 但是一但说别人"very aggressive",基本上潜台词是说:这傻逼凶巴巴的,不好相处,做事没头没脑,老闯祸…不是啥好鸟.
　　
　　Involve:中文翻译成"介入",反正involve的老板越高层事情就越复杂,director要是involve了,manager就开始紧张,VP要是involve了,中国区相关人员都别想有好日子过,得加班加得四脚朝天. 潜台词:大佬很生气,后果很严重.
　　
　　RESEND！：重传。潜台词：有没在上班的呀？还没有答复过来？是不是在混水摸鱼？我的时间很宝贵的，不快点回复你就死定了。
　　
　　highlight :强调，意思是说你搞不定一定要提前highlight出来，抗不住就早点讲，一般要highlight的东西都是比较难搞定的。
　　
　　urgent :紧急的，遇到这样的urgent的case你就有得麻烦了，电话基本不会停下来，好一阵子的热线。
　　
　　appreciate :欣赏。当事情自己解决不了的时候，需要别人帮忙的时候，或者是自己做错事无法挽回的时候，一句your kind help should be appreciated.就会发挥很大的作用了。
　　
　　guarantee :保证，之前promise的东西没有出现，于是再次向别人求助的时候，对方一句Are you guarantee of it?让你很是尴尬，使对方陷入困境。对于sales来讲，此词使用的几率教高。
　　
　　my understandingis...翻成中文是我的理解是。潜台词是，应该是。你的理解有误，我在此再给你解释一下。虽然看上去是对方在说自己的理解，但基本上是认为你的看法是错的，他的是正确的。
　　
　　I’m very disappointed...中文是：我很失望。潜台词是：你怎么搞得，弄成这样。后果有点严重，基本上这个人对你有了一个很差的印象了。
from:http://www.kaixin001.com/!repaste/detail.php?uid=3137675&urpid=2168049438

口语中总用但是想不起来用英语怎么说的话

2010-05-28T18:08:00.001+01:00

low key 低调
I've been back and forth.我犹豫不定。
squeezed juice 鲜榨的果汁
juice with pulp 带果肉的果汁
side effect 副作用
he can't come to the phone now.他现在不能接电话
herbal tea 花草茶
ready for a refill? 我再给你倒一杯吧？

i love what u have done with this place.我喜欢这里的布置。
what was tonight?今晚本来要做什么？
i can't feel my hands.我手麻了。
have an affair 外遇
will anyone miss me if i weren't here? 我在不在这里有什么区别吗？
i saw a lot of stuff. 我大开眼界了、
call security 通知警卫
dog walker 遛狗的人
does sth. mean squat to u? 对你来说sth狗屁不是吗？
what's up with the greedy? 怎么这么贪啊？
work an extra shift 多轮一班
go on, i dare u! 有种你就去！
u r a freak! 你这个变态！
i sensed it was u. 我感觉到是你了、
i apologize on behalf of him.我替他道歉。
why are u changing the subject?为什么要转移话题？
this is so meant to be! 这就是天意！
there's no need to place blame. 没有指责的必要。
curling iron 卷发机
it's gonna leave a stain。这要留印子的。
i have part of the fault. 我也有责任。
distract her with a doll 拿娃娃哄她开心
they are all well received 收到的反响都很好
talk u up 说你的好话
stand firm to 努力坚持
i was just leering 我只是用余光看看
organize my thoughts 整理思绪
get a little preoccupied 事先有事
no way to recover 没有掩饰的机会了
bouncy 活泼
intern 实习生
mug 抢劫
drug dealer 毒贩子
admire your candor 你还真胆大

we are rolling 摄像机正在拍摄
hairnet 发罩
go through this stack 看看这一叠
r u spying on me？你监视我？
just messing with u！跟你开玩笑呢！
enough is enough！闹够了
flyers 寻人（物）海报
it's insensitive of me。我这么做很伤人
u don't have to be brag。拽什么啊？
nod along 跟着点头
a totally separate subject 完全题外话
i thought it was the other way around 我以为是反过来的
close my account 注销银行卡
cuff him 把他铐起来
Woody，tingly 痒

creep me out 雷死我了
no peeking 不要偷看啊
sneakbite kit 毒蛇解药
i feel wild today 我今天好亢奋！

I'm kind of beat 我有点累了
my ears r ringing so bad.我耳鸣得厉害。
can u get the door?你能去开门吗
make a huge fool of myself 出了洋相

r u mocking me?你嘲笑我？
hatrack 草包
sth.is beyond crap 那是扯淡
any luck? 找到了吗？

don't u rush me. 别催我！
it doesn't count. 那不算。

she's gonna be crushed. 她会崩溃的。
she's healed.她好了。（病或者伤害）
goose bumps 鸡皮疙瘩
overreact 反应过度
patch things up with sb.和某人修复关系

pierce my ears 打耳洞
corss that off my list 从单子上划掉
how did it go? 怎么样？
present an award 颁奖

natural charisma 天生丽质
cut him some slack 放他一马
get over with 忘记
get in line 排队（everybody get in line)大家排好队

i don't have the energy for this 我没有能力应付这个
u got me.你还真问住我了

“表里不一”的英文短语[zz]

2010-05-25T18:56:00.001+01:00

carry the house 博得全场喝彩（不是“搬家”）

busy body 爱管闲事的人（不是“忙人”）

an afternoon farmer [俚]拖拉的人

eleventh hour 最后时刻（不是“十一点钟”）

an eye for an eye 以牙还牙

a hot potato 棘手的问题

a small potato [美俚] 微不足道的人或物

dry goods 纺织品；谷物（不是“干货”）

Milk Way 银河（不是“牛奶路”）

man of letters 文学家（不是“写信的人”）

sleep late 睡懒觉（不是“睡得很晚”）

sweet water 淡水；饮用水（不是“糖水，甜水”）

familiar talk 庸俗的谈话（不是“熟悉的谈话”）

walkman 随身听（不是“行走的男人”）

night bird 夜猫子（不是“夜间的鸟”）

dog days 三伏天（不是“狗的日子”）

hot dog 热狗（不是“炎热的狗”）

great cats 狮、虎、豹等猫科动物（不是“巨大的猫”）

touch-me-not 含羞草（不是“别碰我”）

bad sailor 晕船（不是“坏水手”）

car park 停车场（不是“汽车公园”）

big boy [俚]百元钞票

field flowers 野生的花

a field worker 实地工作者

China grass 苎麻（不是“中国草”）

China tree 楝树（不是“中国树”）

French window 落地长窗（不是“法国窗”）

English disease 软骨病（不是“英国病”）

French chalk 滑石粉（不是“法国粉笔”）

Russian boot 长筒靴（不是“俄罗斯皮靴”）

Russian blue 淡蓝色（不是“俄罗斯蓝色”）

bright and early 一大早

a fast friend 可靠的朋友

fast time 夏令时间

stand fast 不后退；屹立不动；不让步

Stand easy ! [英] 稍息！

What a sell ! 真失望！

buy it （回答问题或谜语时用）放弃 e.g. I'll buy it . 我答不出（或者我不晓得）

Dear John letter [美口] 绝交信

broken English 不标准的英语

a broken man （在精神等方面）潦倒的人

Catch me ! 我可不会再干那样的事了。

Give a big hand. 热烈地鼓掌欢迎。

Break a leg ! 祝你好运！

read travels 读游记

travel in the blue 沉思；冥想
from:http://tr.hjenglish.com/page/52640/

新东方老师总结出的100句口语最基础最高频的话

2010-05-24T09:15:00.000+01:00

1． How are you doing?（你好吗？）
　　2． I''m doing great.（我过得很好。）
　　3． What''s up?（出什么事了/你在忙些什么/怎么了？）
　　 4． Nothing special.（没什么特别的。）
　　5． Hi. Long time no see.（嗨，好久不见了。）
　　6． So far so good.（到目前为止，一切都好。）
　　7． Things couldn''t be better.（一切顺利。）
　　8． How about yourself?（你自己呢？）
　　9． Today is a great day.（今天是个好日子。）
　　10． Are you making progress?（有进展吗？）
　　11． May I have your name, please?（请问尊姓大名？）
　　12． I''ve heard so much about you.（久仰大名。）
　　13． I hope you''re enjoying your staying here.（希望你在这里过得愉快。）
　　14． Let''s get together again.（改天再聚聚。）
　　 15． That''s a great idea!（好主意！）
　　16． Please say hello to your mother for me.（请代我向你母亲问好。）
　　17． I''m glad to have met you.（很高兴遇到你。）
　　18． Don''t forget us.（别忘了我们。）
　　19． Keep in touch.（保持联系。）
　　20． I had a wonderful time here.（我在这里度过了难忘的时光。）
　　21． Have a nice weekend.（周末愉快。）
　　22． Same to you.（彼此彼此。）
　　23． Nice talking to you.（很高兴与你聊天。）
　　24． Take care of yourself.（自己当心/照顾好你自己。）
　　25． Thank you for everything.（谢谢你的多方关照/你为我所做的一切。）
　　26． Thank you all for coming.（谢谢光临。）
　　27． I appreciate your help.（我感谢你的帮助。）
　　28． You''re always welcome.（别客气/不用谢）
　　29． Forget it.（算了吧）
　　30． It was my pleasure.（不用谢。）
　　31． I made a mistake.（我弄错了。）
　　32． I''m terribly sorry.（实在抱歉。）
　　33． I must apologize!（我必须道歉！）
　　 34． I feel terrible.（我感觉糟透了。）
　　35． It''s not your fault. （那不是你的错。）
　　36． Sorry to bother /have bothered you.（抱歉，打扰一下/打扰你了。）
　　37． What do you do?（你做什么工作？）
　　38． How do you like your new job?（你觉得你的新工作怎样？）
　　39． I like it a lot.（我很喜欢。）
　　40． I like reading and listening to music.（我喜欢阅读和欣赏音乐。）
　　41． What''s wrong?（怎么回事？）
　　 42． What happened?（发生什么事了？）
　　43． I hope nothing is wrong.（我希望一切顺利。）
　　44． I know how you feel.（我知道你的感受。）
　　45． Sorry to hear that.（听到这个消息我很难受。）
　　46． Come on, you can do that.（来吧，你能做到的。）
　　 47． Use your head.（动动脑筋。）
　　48． You did a great job.（你赶得很好。）
　　 49． That''s very nice of you.（你真好。）
　　50． I''m very proud of you.（我为你感到自豪。）

51． I like your style.（我喜欢你的风格。）
　　 52． I love you guys.（我爱你们。）
　　53． How do I look?（我看起来怎么样？）
　　54． You look great!（你看上去棒极了！）
　　55． That's fantastic!（那真是棒极了！）
　　 56． That's really something.（那真是了不起！）
　　57． It's a pleasure working with you.（与您合作很愉快。）
　　58． Congratulations on you success.（祝贺你的成功。）
　　59． I'd like to propose a toast.（我提议干杯！）
　　60． Are you married or single?（你结婚了吗？）
　　61． I've been dying to see you.（我非常想见到你。）
　　 62． I'm crazy about you.（我为你疯狂/痴迷/神魂颠倒。）
　　63． I love you with all my heart.（我全心全意爱你！）
　　64． You're everything to me.（你是我的一切！）
　　 65． You're in love!（你恋爱了！）
　　66． I'm tired of working all day.（整日工作使我厌烦。）
　　67． You work too much.（你做得太多了。）
　　68． Money will come and go.（钱乃身外之物。）
　　69． Are you crazy?（你疯了吗？）
　　70． Have you got it?（明白了吗？）
　　71． I've got it.（我懂了。）
　　72． I can't afford that.（我承担/买不起。）
　　73． I did it, I'm so happy now.（我做到了，现在我很满意

　74． I don't care.（不关我的事/我不管。）
　　75． I don't think so.（我不这么想/我看不会/不行/不用。）
　　 76． I guess so.（我想是吧。）
　　77． I have no other choice.（我别无选择。）
　　 78． I will do my best!（我会尽力的！）
　　79． I mean it.（我是认真的。）
　　80． I'm so scared.（我怕极了。）
　　81． It's hard to say.（难说。）
　　82． It's a long story.（说来话长/一言难尽。）
　　83． It's a small world.（世界真小。）
　　84． It's against the law!（那是违法的！）
　　85． It's a good opportunity!（好机会！）
　　86． It's dangerous!（危险！）
　　87． May I help you?（我能帮忙吗？）
　　88． No doubt about it.（毫无疑问。）
　　89． That's bullshit!（废话！）
　　90． Think it over.（仔细考虑一下。）
　　91． Time will tell.（时间会证明的。）
　　92． What a surprise!（太令人惊讶了！）
　　93． Whatever you say!（随便你！）
　　94． You are the boss!（听你的！你说了算！）
　　95． You have my word!（我保证！）
　　96． Tough job, tough day, tough world. Life is not always sweet. That's life!
　　（艰苦的工作，艰难的日子，不幸的世界。生活并不总是甜蜜的。这就是生活！）
　　97． I need some sleep.（我需要睡眠。）
　　98． Take it easy.（别紧张。）
　　99． Just relax.（放松一下。）
　　100． Zip your fly!（闭嘴！）

order of magnitude

2010-05-02T18:16:00.001+01:00

In words (long scale)	In words (short scale)	Prefix	Symbol	Decimal	Power of ten	Order of magnitude
quadrillionth	septillionth	yocto-	y	0.000000000000000000000001	10⁻²⁴	−24
trilliardth	sextillionth	zepto-	z	0.000000000000000000001	10⁻²¹	−21
trillionth	quintillionth	atto-	a	0.000000000000000001	10⁻¹⁸	−18
billiardth	quadrillionth	femto-	f	0.000000000000001	10⁻¹⁵	−15
billionth	trillionth	pico-	p	0.000000000001	10⁻¹²	−12
milliardth	billionth	nano-	n	0.000000001	10⁻⁹	−9
millionth	millionth	micro-	µ	0.000001	10⁻⁶	−6
thousandth	thousandth	milli-	m	0.001	10⁻³	−3
hundredth	hundredth	centi-	c	0.01	10⁻²	−2
tenth	tenth	deci-	d	0.1	10⁻¹	−1
one	one	-	-	1	10⁰	0
ten	ten	deca-	da	10	10¹	1
hundred	hundred	hecto-	h	100	10²	2
thousand	thousand	kilo-	k	1,000	10³	3
million	million	mega-	M	1,000,000	10⁶	6
milliard	billion	giga-	G	1,000,000,000	10⁹	9
billion	trillion	tera-	T	1,000,000,000,000	10¹²	12
billiard	quadrillion	peta-	P	1,000,000,000,000,000	10¹⁵	15
trillion	quintillion	exa-	E	1,000,000,000,000,000,000	10¹⁸	18
trilliard	sextillion	zetta-	Z	1,000,000,000,000,000,000,000	10²¹	21
quadrillion	septillion	yotta-	Y	1,000,000,000,000,000,000,000,000	10²⁴	24

弄错了会很尴尬的英文[zz]

2010-04-26T18:54:00.000+01:00

1.日常用语类
busboy 餐馆勤杂工（不是“公汽售票员”）
busybody 爱管闲事的人（不是“大忙人”）
dry goods （美）纺织品；（英）谷物（不是“干货”）
eleventh hour 最后时刻（不是“十一点”）
lover 情人（不是“爱人”）
dead president 美钞（上印有总统头像）（并非“死了的总统”）
sweet water 淡水（不是“糖水”）
confidence man 骗子（不是“信得过的人”）
criminal lawyer 刑事律师（不是“犯罪的律师”）
rest room 厕所（不是“休息室”）
dressing room 化妆室（不是“试衣室”或“更衣室”）
horse sense 常识（不是“马的感觉”）
capital idea 好主意（不是“资本主义思想”）
black tea 红茶（不是“黑茶”）
black stranger 完全陌生的人（不是“陌生的黑人”）
white man 忠实可靠的人（不是“皮肤白的人”）
green hand 新手（不是“绿手”）
blue stocking 女学者、女才子（不是“蓝色长统袜”）
Chinese dragon 麒麟（不是“中国龙”）
American beauty 红蔷薇（不是“美国美女”）
English disease 气管炎（不是“英国病”）
Spanish athlete 吹牛的人（不是“西班牙运动员”）
beat it！快跑（不是打他）（感谢博友mlau提供此词条）
2、成语类
pull one's leg 开玩笑（不是“拉后腿”）
in one's birthday suit 赤身裸体（不是“穿着生日礼服”）
eat one's words 收回已说的话（不是“吃话”）
an apple of love 西红柿（不是“爱情之果”）
handwriting on the wall 不祥之兆（不是“大字报”）
bring down the house 博得全场喝彩（不是“推倒房子”）
have a fit 勃然大怒（不是“试穿”）
think a great deal of oneself 高看或看重自己（不是“为自己想得很多”）
pull up one's socks 鼓起勇气（不是“提上袜子”）
3、表达类
Look out! 当心！（不是“向外看”）
What a shame! 多可惜！真遗憾！（不是“多可耻”）
You don't say! 是吗！（不是“你别说”）
You can say that again! 说得好！（不是“你可以再说一遍”）
I haven't slept better. 我睡得好极了。（不是“我从未睡过好觉”）
You can't be too careful in your work. 你工作越仔细越好。（不是“你工作不能太仔细”）
It has been 4 years since I smoked. 我戒烟4年了。（不是“我抽烟4年了”）
All his friends did not turn up. 他的朋友没全到。（不是“他的朋友全没到”）
People will be long forgetting her. 人们在很长时间内会记住她的。（不是“人们会永远忘记她”）
He was only too pleased to let them go. 他很乐意让他们走。（不是“他太高兴了，不愿让他们走”）
It can't be less interesting. 它无聊极了。（不是“它不可能没有趣”）
from:http://blog.sina.com.cn/s/blog_4c68d5700100d2gs.html

英文标点符号怎么念

2010-04-07T14:09:00.001+01:00

{　open brace, open curly　左花括号
}　close brace, close curly　右花括号
(　open parenthesis, open paren　左圆括号
)　close parenthesis, close paren　右圆括号
() brakets/ parentheses　括号
[　open bracket 左方括号
]　close bracket 右方括号
[] square brackets　方括号
.　period, dot　句号，点
|　vertical bar, vertical virgule　竖线
&　ampersand, and, reference, ref　和，引用
*　asterisk, multiply, star, pointer　星号，乘号，星，指针
/　slash, divide, oblique 斜线，斜杠，除号
//　slash-slash, comment 双斜线，注释符
#　pound　井号
\　backslash, sometimes escape　反斜线转义符，有时表示转义符或续行符
~　tilde　波浪符
.　full stop　句号
,　comma　逗号
:　colon　冒号
;　semicolon　分号
?　question mark　问号
!　exclamation mark (英式英语) exclamation point (美式英语)
'　apostrophe　撇号
-　hyphen　连字号
-- dash 破折号
...　dots/ ellipsis　省略号
"　single quotation marks 单引号
""　double quotation marks 双引号
‖ parallel 双线号
&　ampersand = and
～　swung dash 代字号
§　section; division 分节号
→　arrow 箭号；参见号

culture notes book2_1

2010-04-03T23:13:00.001+01:00

Martin Luther King, Jr.

US black civil-right leader (1929-1968). An outstanding orator, he followed principles of nonviolent resistance in organizing demonstrations against racial inequality and was one of the leaders of the Great March to Washington in 1963, joined by over 250,000 people. His campaigns contributed to the passing of the Civil Rights Act (1964) and the Voting Rights Act (1965) and earned him the Nobel Peace Prize in 1964. He was assassinated in Memphis, Tennessee.

Sophia Loren

Italian film actress (1934- ). From working as extra and then a supporting actress, she worked her way up to international stardom in such films as Two Women (1961), The Millionairess (1962), Marriage Indian Style (1964), and The Cassandra Crossing (1977). She was married to the Italian film producer Carlo Ponti.

Julius Caesar

Roman general and statesman (100-44 BC), whose career marked the end of the Roman Republic.

Queensland

The second largest state of Australia, situated in the north-east. It is Australia's most decentralized region, containing approximately one third of all Australian urban centres. It has an area of 1,728,000 square kms with a population of two million (1980). The capital city is Brisbane.

Seattle

A city in the state of Washington, USA. It is Alaska's main supply port.

San Diego

A city on San Diego Bay, California, USA.

Oklahoma City

Capital of Oklahoma on the North Canadian River, USA. Founded in 1889, it expanded rapidly following the discovery of oil. Today it is a commercial, industrial, and distribution centre for an oil-producing and agricultural area.

Miami

A city and port on Biscayne Bay, Florida. A major tourist resort and retirement centre, it grew during the Florida land boom of the 1920s and includes now Coral Gables and Miami Beach.

Montreal

A Canadian city and port in Quebec, on Montreal Island at the junction of the Ottawa and St. Lawrence Rivers. Canada's largest city, it is also the greatest transportation, trade, and manufacturing centre. Two thirds of the population is French speaking, making it the second largest French-speaking city in the world.

Toronto

Capital of Ontario, Canada. On Lake Ontario, it is Canada's second largest city.

Brooklyn

One of the five boroughs of New York City, USA, situated at the southwestern end of Long Island. It has an area of 210 square km, population 2.2 million (1980).

Tahiti

The largest of the Society Islands in the south central Pacific Ocean, in French Polynesia. It has an area of 1,005 square kms with a population of 116,000 in 1983.

Civil Service (UK)

The bureaucracy that implements government policies. The civil service is organized into such ministries as the Home Office and the Foreign and Commonwealth Office.

Mathematical language

2010-03-21T23:28:00.001Z

Notations:
common math operators
write:read
a+b:a add b
a+a+a+a+a:5 lots of a
a-b:a minus b
a±b:a plus or minus b
5!:ﬁve factorial
|4| : modulus of 4
¼=0.3 rounded to 1 signiﬁcant ﬁgure
-5°C:minus 5 degrees Celsius or 5 degrees below zero
a³: a to the power 3
a×b: a times b or a multiply b
a÷b: a divided by b or a over b
a=b: a is equal to b
a̸=b:a is not equal to b
a≈b:a is approximately equal to b
a≥b:a is greater than or equal to b
a≤b:a is less than or equal to b
():parentheses
[]:brackets
{}:Braces
√a:square root of a
À:A acute
Á:A grave
Â:A hat
Ã:A tilde
Ä:A double dots
y´:y prime
y¯: y bar

FKQA8CJ6CSY9

Wouldn't It Be Loverly?[zz]

2010-02-28T00:31:00.001Z

All I want is a room somewhere,
Far away from the cold night air,
With one enormous chair.
Oh, wouldn't it be loverly?

Lots of chocolate for me to eat.
Lots of coal makin' lots of 'eat.
Warm face, warm 'ands, warm feet.
Oh, wouldn't it be loverly?

Oh, so loverly sittin' absobloominlutely still.
I would never budge 'till spring
Crept over the windowsill.

Someone's 'ead restin' on my knee,
Warm an' tender as 'e can be,
Who takes good care of me.
Oh, wouldn't it be loverly?
Loverly, loverly, loverly, loverly.
From<my fairly lady>

What to do when the PhD is finished?

2010-02-11T18:57:00.000Z

What to do when the PhD is finished?

军棋里的军阶

2010-02-02T22:23:00.002Z

军 army
师 division
旅 brigade
团 regiment
营 battalion
连 company
排 platoon

军棋military chess

工兵sapper
排长platoon commander(中尉 lieutenant)
连长company commander ( 上尉 captain )
营长battalion commander (少校 major)
团长colonel（上校）
旅长brigadier （准将）
师长division commander
军长army commander
司令chief commander
军旗army flag/ensign
地雷landmine
炸弹bomb
行营field headquarter
大本营supreme headquarter

数量词

2010-02-02T22:22:00.001Z

  Few: 1-4； 

  Several: 5-9； 

  Pack: 10-19； 

  Lots: 20-49； 

  Horde: 50-99； 

  Throng: 100-249； 

  Swarm: 250-499； 

  Zounds: 500-999； 

  Legion: >1000

中国三军军衔中英对照[zz]

2010-02-02T22:18:00.001Z

●中国三军军衔中英对照●
Ranks In The Chinese Armed Forces
【陆军--------Army】
一级上将----General First Class
上将--------General
中将--------Lieutenant General
少将--------Major General
大校--------Senior Colonel
上校--------Colonel
中校--------Lieutenant Colonel
少校--------Major
上尉--------Captain
中尉--------First Lieutenant
少尉--------Second Lieutenant
军事长------Master Sergeant
专业军士----Specialist Sergeant
上士--------Sergeant, First Class
中士--------Sergeant
下士--------Corporal
上等兵------Private, First Class
列兵--------Private
【海军--------Navy】
一级上将----Admiral, First Class
上将--------Admiral
中将--------Vice Admiral
少将--------Rear Admiral
大校--------Senior Captain
上校--------Captain
中校--------Commander
少校--------Lieutenant Commander
上尉--------Lieutenant
中尉--------Lieutenant, Junior Grade
少尉--------Ensign
军事长------Chief Petty Officer
专业军士----Specialist Petty Officer
上士--------Petty Officer, First Class
中士--------Petty Officer, Second Class
下士--------Petty Officer, Third Class
上等兵------Seaman, First Class
列兵--------Seaman, Second Class
【空军--------Air Force】
一级上将----General, First Class
上将--------General
中将--------Lieutenant General
少将--------Major General
大校--------Senior Colonel
上校--------Colonel
中校--------Lieutenant Colonel
少校--------Major
上尉--------Captain
中尉--------First Lieutenant
少尉--------Second Lieutenant
军事长------Master Sergeant
专业军士----Specialist Sergeant
上士--------Technical Sergeant
中士--------Staff Sergeant
下士--------Corporal
上等兵------Airman, First Class
列兵--------Airman, Second Class
track by:http://www.jysls.com/thread-287480-1-4.html

3 ist

2010-02-02T22:11:00.001Z

humanist:One who is concerned with the interests and welfare of humans.
rationalist:who reliance on reason rather than intuition to justify one's beliefs or actions.
methodist:One who emphasizes or insists on systematic procedure.

which are you belong to?
i prefer rationalist.that's true scientist!

Presentation Sentences[zz]

2010-01-24T10:04:00.001Z

1. Right, let's get started.

2. Let me introduce myself.

3. I've divided my presentation into three main parts.

4. Just to give you a brief overview.

5. I'll be saying more about this in a minute.

6. I'm sure the implications of this are clear to all of us.

7. There's an important point to be made here.

8. OK, let's move on. (go on to make your next point)

9. As you can see, the figures speak for themselves.

10. To go back to what I was saying earlier.

11. Are there any questions you'd like to ask at this point?

12. I'd like to look at this in more detail.

13. Let's put this into perspective. (to explain it this way)

14. Perhaps I should expand on that a little.

15. To digress for a moment? (to depart from your plan)

16. So, to sum up?

17. That brings me to the end of my talk.

18. Thank you. I'm sure you all have lots of questions.
track by:http://www.kaixin001.com/!repaste/detail.php?uid=3855991&urpid=1325499173###

Help for Organizing, Writing, and Formating Your Research Paper[zz]

2010-01-23T21:50:00.001Z

SELECTING A TOPIC, TAKING NOTES, ORGANIZING A DRAFT

Menasche, Lionel. Writing a Research Paper. Revised ed. Ann Arbor: University of Michigan Press, 1997.
(Uris Ref PE 1478 .M4x 1997): A textbook designed to help English as a Second Language students write research papers. Includes a set of assignments, exercises, and answers; a glossary of writing and research items, and an index.
Turabian, Kate L. Students' Guide for Writing College Papers. 3rd ed. Chicago: University of Chicago Press, 1976.
(Uris Stacks PE 1478 .T92 S3 1976; also Olin Ref): A well-organized guide to writing papers, from choosing the topic to writing the paper in its final form. Includes advice on collecting information, outlining, taking notes, punctuation, etc. Best known for its chapters on format in footnotes and bibliographies. Replete with examples illustrating how the general rules apply to all manner of publications and problems.

WRITING THE PAPER: STYLE AND USAGE

Hodges, John C. and Mary E. Whitten. Harbrace College Handbook. 9th ed. New York: Harcourt, Brace Jovanovich, 1982.
(Uris Stacks PE 1111 .H68 1982): This handbook is both a comprehensive guide to good English grammar, usage, punctuation, and spelling, and a textbook containing exercises on these subjects. Arranged by subject, it includes a glossary of grammatical terms and an index.
Strunk, William and E.B. White. The Elements of Style. 3rd ed. New York: Macmillan, 1979.
(Uris Ref PE 1421 .S92 1979): E.B. White, who revised the original of this "little book" and who wrote the introduction to it, says that this was Will Strunk's "attempt to cut the vast tangle of English rhetoric down to size and write its rules and principles on the head of a pin". As useful today as it was when first written (1919), the Elements is an essential guide for anyone who takes the English language seriously.

THE FINAL PRODUCT: FORMAT AND DOCUMENTATION

Publication Manual of the American Psychological Association. 5th ed. Washington: APA, 2001.
(Uris Ref BF 76.7 .P83x 2001; also Olin Ref, Mann Ref, others): The authoritative style manual for anyone writing in the field of psychology. Its chapters discuss the content and organization of a manuscript, writing style, the American Psychological Association style, and typing, mailing and proofreading. In addition, the final chapter describes the journals of the American Psychological Association.
Gibaldi, Joseph. MLA Handbook for Writers of Research Papers. 6th ed. New York: Modern Language Association, 2003.
(Uris Ref Z 253 .M68 2003; also Olin Ref): This handbook is based on the MLA Style Manual and is intended as an aid for college students writing research papers. Included here is information on selecting a topic, researching the topic, note taking, the writing of footnotes and bibliographies, as well as sample pages of a research paper. Useful for the beginning researcher.
Turabian, Kate L. A Manual for Writers of Term Papers, Theses, and Dissertations. 6th ed. Chicago: University of Chicago Press, 1996.
(Uris Ref PE 1478 .T92 1996; also Olin Ref, others): Kate Turabian's standard guide for student writers, newly revised and expanded by John Grossman and Alice Bennett. Chapters cover everything you've ever wanted to know about putting a paper together, from writing introductory chapters to formatting the bibliography.

Track by:http://www.library.cornell.edu/olinuris/ref/research/organize.html

The Seven Steps of the Research Process[zz]

2010-01-23T14:51:00.001Z

The following seven steps outline a simple and effective strategy for finding information for a research paper and documenting the sources you find. Depending on your topic and your familiarity with the library, you may need to rearrange or recycle these steps. Adapt this outline to your needs. We are ready to help you at every step in your research.

STEP 1: IDENTIFY AND DEVELOP YOUR TOPIC

SUMMARY: State your topic as a question. For example, if you are interested in finding out about use of alcoholic beverages by college students, you might pose the question, "What effect does use of alcoholic beverages have on the health of college students?" Identify the main concepts or keywords in your question.

More details on how to identify and develop your topic.

STEP 2: FIND BACKGROUND INFORMATION

SUMMARY: Look up your keywords in the indexes to subject encyclopedias. Read articles in these encyclopedias to set the context for your research. Note any relevant items in the bibliographies at the end of the encyclopedia articles. Additional background information may be found in your lecture notes, textbooks, and reserve readings.

More suggestions on how to find background information.

Return to the top

STEP 3: USE CATALOGS TO FIND BOOKS AND MEDIA

SUMMARY: Use guided keyword searching to find materials by topic or subject. Print or write down the citation (author, title,etc.) and the location information (call number and library). Note the circulation status. When you pull the book from the shelf, scan the bibliography for additional sources. Watch for book-length bibliographies and annual reviews on your subject; they list citations to hundreds of books and articles in one subject area. Check the standard subject subheading "--BIBLIOGRAPHIES," or titles beginning with Annual Review of... in the Cornell Library Classic Catalog.

More detailed instructions for using catalogs to find books.

Finding media (audio and video) titles.

Watch on YouTube: How to read citations

STEP 4: USE INDEXES TO FIND PERIODICAL ARTICLES

SUMMARY: Use periodical indexes and abstracts to find citations to articles. The indexes and abstracts may be in print or computer-based formats or both. Choose the indexes and format best suited to your particular topic; ask at the reference desk if you need help figuring out which index and format will be best. You can find periodical articles by the article author, title, or keyword by using the periodical indexes in the Library home page. If the full text is not linked in the index you are using, write down the citation from the index and search for the title of the periodical in the Cornell Library Classic Catalog. The catalog lists the print, microform, and electronic versions of periodicals at Cornell.

How to find and use periodical indexes at Cornell.

Watch on YouTube: How to read citations

Return to the top

STEP 5: FIND INTERNET RESOURCES

SUMMARY: Use search engines. Check to see if your class has a bibliography or research guide created by librarians.

Finding Information on the Internet: A thorough tutorial from UC Berkeley.

STEP 6: EVALUATE WHAT YOU FIND

SUMMARY: See How to Critically Analyze Information Sources and Distinguishing Scholarly from Non-Scholarly Periodicals: A Checklist of Criteria for suggestions on evaluating the authority and quality of the books and articles you located.
Watch on YouTube: Identifying scholarly journals Identifying substantive news sources

If you have found too many or too few sources, you may need to narrow or broaden your topic. Check with a reference librarian or your instructor.

When you're ready to write, here is an annotated list of books to help you organize, format, and write your paper.

STEP 7: CITE WHAT YOU FIND USING A STANDARD FORMAT

Give credit where credit is due; cite your sources.

Citing or documenting the sources used in your research serves two purposes, it gives proper credit to the authors of the materials used, and it allows those who are reading your work to duplicate your research and locate the sources that you have listed as references.

Knowingly representing the work of others as your own is plagarism. (See Cornell's Code of Academic Integrity). Use one of the styles listed below or another style approved by your instructor. Handouts summarizing the APA and MLA styles are available at Uris and Olin Reference.

Available online:

RefWorks is a web-based program that allows you to easily collect, manage, and organize bibliographic references by interfacing with databases. RefWorks also interfaces directly with Word, making it easy to import references and incorporate them into your writing, properly formatted according to the style of your choice.

See our guide to citation tools and styles.
Format the citations in your bibliography using examples from the following Library help pages: Modern Language Association (MLA) examples and American Psychological Association (APA) examples.

Style guides in print (book) format:
- MLA Handbook for Writers of Research Papers. 7th ed. New York: MLA, 2009.
  (Olin Reference LB 2369 .G53 2009 [shelved at the reference desk]; also Uris Reference, others)
  
  This handbook is based on the MLA Style Manual (Olin and Uris Ref PN 147 .G444x 1998) and is intended as an aid for college students writing research papers. Included here is information on selecting a topic, researching the topic, note taking, the writing of footnotes and bibliographies, as well as sample pages of a research paper. Useful for the beginning researcher.
- Publication Manual of the American Psychological Association. 6th ed. Washington: APA, 2010. (Olin Reference BF 76.7 .P83 2010 [shelved at the reference desk]; also Uris Reference, Mann Reference, others)
  
  The authoritative style manual for anyone writing in the field of psychology. Useful for the social sciences generally. Chapters discuss the content and organization of a manuscript, writing style, the American Psychological Association citation style, and typing, mailing and proofreading.
- If you are writing an annotated bibliography, see How to Prepare an Annotated Bibliography.

Return to the top

RESEARCH TIPS:

WORK FROM THE GENERAL TO THE SPECIFIC.: Find background information first, then use more specific and recent sources.
RECORD WHAT YOU FIND AND WHERE YOU FOUND IT.: Record the complete citation for each source you find; you may need it again later.
TRANSLATE YOUR TOPIC INTO THE SUBJECT LANGUAGE OF THE INDEXES AND CATALOGS YOU USE.: Check your topic words against a thesaurus or subject heading list.; track from:http://www.library.cornell.edu/olinuris/ref/research/skill1.htm

英文标点符号怎么念[zz]

2010-01-02T00:28:00.000Z

+　 plus　加号；正号
-　 minus　减号；负号
±　plus or minus　正负号
×　is multiplied by　乘号
÷　is divided by　除号
＝　is equal to　等于号
≠　is not equal to　不等于号
≡　is equivalent to　全等于号
≌　is equal to or approximately equal to　等于或约等于号
≈　is approximately equal to　约等于号
＜　 is less than　小于号
＞　is greater than　大于号
≮　is not less than　不小于号
≯ 　is not more than　不大于号
≤　is less than or equal to　小于或等于号
≥　is more than or equal to　大于或等于号
%　 per cent　百分之…
‰　per mill　千分之…
∞　 infinity　无限大号
∝　varies as　与…成比例
√　(square) root　平方根
∵　since; because　因为
∴　hence　所以
∷　equals, as (proportion)　等于，成比例
∠　angle　角
⌒　semicircle　半圆
⊙　circle　圆
○　circumference　圆周
π　pi 圆周率
△ 　triangle　三角形
⊥　perpendicular to　垂直于
∪　union of　并，合集
∩　 intersection of 交，通集
∫　the integral of …的积分
∑　(sigma) summation of　总和
°　degree　度
′　minute　分
″　second　秒
℃　Celsius system　摄氏度
{ 　open brace, open curly　左花括号
}　close brace, close curly　右花括号
(　 open parenthesis, open paren　左圆括号
)　close parenthesis, close paren　右圆括号
() brakets/ parentheses　括号
[　open bracket 左方括号
]　 close bracket 右方括号
[] square brackets　方括号
.　period, dot　句号，点
|　 vertical bar, vertical virgule　竖线
&　ampersand, and, reference, ref　和，引用
*　asterisk, multiply, star, pointer　星号，乘号，星，指针
/　slash, divide, oblique 斜线，斜杠，除号
//　slash-slash, comment 双斜线，注释符
#　pound　井号
\　backslash, sometimes escape　反斜线转义符，有时表示转义符或续行符
~　tilde　波浪符
. 　full stop　句号
,　comma　逗号
:　colon　冒号
;　semicolon　分号
?　 question mark　问号
!　exclamation mark (英式英语) exclamation point (美式英语)
' 　apostrophe　撇号
-　hyphen　连字号
-- dash 破折号
...　dots/ ellipsis　省略号
" 　single quotation marks 单引号
""　double quotation marks 双引号
‖ parallel 双线号
&　ampersand = and
～　swung dash 代字号
§　section; division 分节号
→　arrow 箭号；参见号

经典英文爱情句子（中英对照）(zz)

2009-12-05T15:41:00.001Z

伸手摘星，即使徒劳无功，亦不致一手污泥。
When you reach for the stars you may not quite get one,
but you won't come up with a handful of mud either.

我的爱情犹如青草，

藏在深山。
它郁郁葱葱，
却无人知晓。
My love is like the grasses
Hidden in the deep mountains.
Though its abundance increase,
There is none that knows.

我一直孤独入眠，
睡梦中你出现在我的眼前，
我要亲吻你，我的爱人，
今夜我就要亲吻你。
I have been sleeping all alone,
You have been staring in my dreams.
I want to kiss you, my baby,
I want to kiss you tonight.

爱不贵亲密，贵长久。
Love me little, love me long!

我的爱人，
你就像一朵鲜花，
那么甜蜜、纯洁而秀雅。
My love,
You are like a flower,
So sweet and pure and fair.

我简直不敢相信，爱你是如此地美好。
我不敢相信你也有如此感觉。
我现在才明白吻原是那么甜蜜，
就像夏日的阳光，
包含着你对我的柔情蜜意。
I just can't believe the loveliness of loving you.
I just can't believe the one to love this feeling, too.
I now know how sweet a kiss could be.
Like the summer sunshine,
Your sweetness over me.

我这一生要做的一件事情，
绝对要做的一件事情，那就是：
爱你，想你，追求你，直到死。
I shall do one thing in this life,
One thing certain, that is:
Love you, Long for you,
And keep wanting you till I die.

哦！我的爱，亲爱的，
我渴望你的抚摸已经好久了。
而时光难熬，它能改变许多事，
你还是我的吗？
我需要你的爱。
愿上帝赐给我你的爱。
Oh, my love, my darling,
I have hungered for you touch a long time.
And time goes by so slowly, and time can do so much.
Are you still mine?
I need your love,
God speed your love to me.

我多想做你时刻思念的人，
你倾诉梦想的人，
与你同甘共苦的人，
我总想做你所爱的人。
I love to be the one you always think of,
The one you share the joys and hardships with,
I'll always love to be the one you love.

我的目光就是你窗前的星星，
每夜都在深情地注视着你。
My eyes are the stars over your window,
Gazing affectionately at you every night.

Where there is great love, there are always miracles.
哪里有真爱存在，哪里就有奇迹。

Love is like a butterfly. It goes where it pleases and it pleases where it goes.
爱情就像一只蝴蝶，它喜欢飞到哪里，就把欢乐带到哪里。

If I had a single flower for every time I think about you, I could walk forever in my garden.
假如每次想起你我都会得到一朵鲜花，那么我将永远在花丛中徜徉。

Within you I lose myself, without you I find myself wanting to be lost again.
有了你，我迷失了自我。失去你，我多么希望自己再度迷失。

At the touch of love everyone becomes a poet.
每一个沐浴在爱河中的人都是诗人。

Look into my eyes - you will see what you mean to me.
看看我的眼睛，你会发现你对我而言意味着什么。

Distance makes the hearts grow fonder.
距离使两颗心靠得更近。

I need him like I need the air to breathe.
我需要他，正如我需要呼吸空气。

If equal affection cannot be, let the more loving be me.
如果没有相等的爱，那就让我爱多一些吧。

Love is a vine that grows into our hearts.
爱是长在我们心里的藤蔓。

If I know what love is, it is because of you.
因为你，我懂得了爱。

Love is the greatest refreshment in life.
爱情是生活最好的提神剂。

Love never dies.
爱情永不死。

The darkness is no darkness with thee.
有了你，黑暗不再是黑暗。

We cease loving ourselves if no one loves us.
如果没有人爱我们，我们也就不会再爱自己了。

There is no remedy for love but to love more.
治疗爱的创伤唯有加倍地去爱。

When love is not madness, it is not love.
如果爱不疯狂就不是爱了。

A heart that loves is always young.
有爱的心永远年轻。

Love is blind.
爱情是盲目的。

Love is like the moon, when it does not increase, it decreases.
爱情就像月亮，不增则减。

The soul cannot live without love.
灵魂不能没有爱而存在。

Brief is life, but love is long.
生命虽短，爱却绵长。

Who travels for love finds a thousand miles not longer than one.
在爱人眼里，一千里的旅程不过一里。

Love keeps the cold out better than a cloak.
爱比大衣更能驱走寒冷。

Take away love, and our earth is a tomb.
没有了爱，地球便成了坟墓。

My heart is with you.
我的爱与你同在。

I miss you so much already and I haven't even left yet!
尽管还不曾离开，我已对你朝思暮想！

I'll think of you every step of the way.
我会想你，在漫漫长路的每一步。

Wherever you go, whatever you do, I will be right here waiting for you.
无论你身在何处，无论你为何忙碌，我都会在此守候。

Passionate love is a quenchless thirst.
热烈的爱情是不可抑制的渴望。

The most precious possession that ever comes to a man in this world is a woman's heart.
在这个世界上，男人最珍贵的财产就是一个女人的心。

One word frees us of all the weight and pain in life.That word is love.
有一个词可以让我们摆脱生活中所有的负担和痛苦，那就是“爱情”。

Every day without you is like a book without pages.
没有你的日子就像一本没有书页的书。

Love is hard to get into, but harder to get out of.
爱很难投入，但一旦投入，便更难走出。

Love is a light that never dims.
爱是一盏永不昏暗的明灯。

May your love soar on the wings of a dove in flight.
愿你的爱乘着飞翔的白鸽，展翅高飞。

She who has never loved, has never lived.
人活着总要爱一回。

Life is the flower for which love is the honey.
生命如花，爱情是蜜。

No words are necessary between two loving hearts.
两颗相爱的心之间不需要言语。

Precious things are very few in this world. That is the reason there is just one you.
在这世上珍贵的东西总是罕有，所以这世上只有一个你。

You make my heart smile.
我的心因你而笑。

The road to a lover's house is never long.
通往爱人家里的路总不会漫长。

Why do the good girls, always want the bad boys?
为何好女孩总喜欢坏男孩？

Being with you is like walking on a very clear morning.
和你在一起就像在一个清爽的早晨漫步。

It is never too late to fall in love.
爱永远不会嫌晚。

To the world you may be just one person. To the person you may be the world.
对于世界，你可能只是一个人，但对于某个人，你却是整个世界。

Where there is love, there are always wishes.
哪里有爱，哪里就有希望。

You don't love a woman because she is beautiful, but she is beautiful because you love her.
你不会因为美丽去爱一个女人，但她却会因为你的爱而变得美丽。

Love is something eternal; the aspect may change, but not the essence.
爱是永恒的，外表可能改变，但本质永远不变。

Love is not a matter of counting the days. It's making the days count.
爱情不是数着日子过去，它让每个日子都变得有意义。

With the wonder of your love, the sun above always shines.
拥有你美丽的爱情，太阳就永远明媚。

Love is a fabric that nature wove and fantasy embroidered.
爱情是一方织巾，用自然编织，用幻想点缀。

First love is unforgettable all one's life.
初恋是永生难忘的。

In the very smallest cot there is room enough for a loving pair.
哪怕是最小的茅舍，对一对恋人来说都有足够的空间。

Love without end hath no end.
情绵绵，爱无边。

Love's tongue is in the eyes.
爱情的话语全在双眼之中。

In love folly is always sweet.
恋爱中，干傻事总是让人感到十分美妙。

There is no hiding from lover's eyes.
什么也瞒不过恋人的眼睛。

The only present love demands is love.
爱所祈求的唯一礼物就是爱。

The heart that once truly loves never forgets.
真挚恋爱过的心永不忘却。

Love warms more than a thousand fires.
爱情的炽热胜过千万团的火。

Your smiling at me is my daily dose of magic.
你嫣然的微笑是我每日享受到的魅力。

Your kiss still burns on my lips, everyday of mine is so beautiful.
你的吻还在我的唇上发烫，从此我的日子变得如此美丽。

Love understands love; it needs no talk.
相爱的心息息相通，无需用言语倾诉。

Love me little and love me long.
不求情意绵绵，但求天长地久。

First impression of you is most lasting.
对你最初的印象，久久难以忘怀。

When the words "I love you" were said by you for the first time, my world blossoms.
第一次听到你对我说"我爱你"，我的世界一瞬间鲜花绽开。

Tell me you are mine. I'll be yours through all the years, till the end of time.
请告诉我你是我的。岁岁年年，我都属于你，永远永远。

Love is a fire which burns unseen.
爱情是无形燃烧的火焰。

I feel happy at times we have had angry words but these have been kissed away.
我们生气争执时，爱的双唇把它们吻得无影无踪，我的心也顿觉甜蜜。

You cannot appreciate happiness unless you have known sadness too.
不知道什么是忧伤，就不会真正感激幸福。

But if the while I think on thee, dear friend, all losses are restored, and sorrows end.
只要我一想起你，亲爱的人，所有的失落和遗憾烟消云散。

track from:http://www.u148.net/article/15036.html

Simulink-Scope modify

2009-11-26T12:01:00.001Z

The ability to interact with Scope figure properties is not available because the handle of the Scope figure is not turned on. To turn the handle of your Scope figure on, and show the menus, type the following at the MATLAB command prompt (after opening the Scope figure):

shh = get(0,'ShowHiddenHandles');
set(0,'ShowHiddenHandles','On')
set(gcf,'menubar','figure')
set(gcf,'CloseRequestFcn','closereq')
set(gcf,'DefaultLineClipping','Off')
set(0,'ShowHiddenHandles',shh)

This will allow you to manipulate your Scope figure just like any other MATLAB figure, allowing you to make changes such as:
- Background/foreground color
- Line color
- Add text or a legend
- Add a print icon
from:http://www.mathworks.co.uk/matlabcentral/newsreader/view_thread/239142

27 dresses

2009-11-21T22:16:00.001Z

After watching 27 dresses,I understand my life now.
Sometimes the person you think you love most is not the Mr. Right for you.In fact you idolize him only.The true loave should be share with the one who is congenial to you.that is the way for you to keep on moving together.
I blocked Ams's number in my mobile.I don't know what will happen after that,I don't care either.Because I know whatever I want is just a single & simple life and don't make life too complicate.I am not deserve love.Everything has its cost.The cost of my successful life is love and emotions.I should remember that for ever and ever,as I nearly forgot it for a long time.that's why i have a messy and disorder life during the past whole year.I have gone too far away from where I belong.
'Live happily ever after.' It's fairy tales in children's dreams.Although I believe it,meanwhile,I know it's just not for a person like me.
Everything has it's own life,no good,no bad.it's a unique life for itself.
Please come back to be yourself,Joy.

How To Ask Questions The Smart Way[zz]

2009-08-29T12:30:00.000+01:00

How To Ask Questions The Smart Way
track backs:http://www.catb.org/~esr/faqs/smart-questions.html
Eric Steven Raymond
Thyrsus Enterprises
Rick Moen
Copyright © 2001,2006 Eric S. Raymond, Rick Moen
Table of Contents

Disclaimer
Introduction
Before You Ask
When You Ask

Choose your forum carefully
Web and IRC forums directed towards newbies often give the quickest response
As a second step, use project mailing lists
Use meaningful, specific subject headers
Make it easy to reply
Write in clear, grammatical, correctly-spelled language
Send questions in accessible, standard formats
Be precise and informative about your problem
Volume is not precision
Don't claim that you have found a bug
Grovelling is not a substitute for doing your homework
Describe the problem's symptoms, not your guesses
Describe your problem's symptoms in chronological order
Describe the goal, not the step
Don't ask people to reply by private e-mail
Be explicit about your question
When asking about code
Don't post homework questions
Prune pointless queries
Don't flag your question as “Urgent”, even if it is for you
Courtesy never hurts, and sometimes helps
Follow up with a brief note on the solution

How To Interpret Answers

RTFM and STFW: How To Tell You've Seriously Screwed Up
If you don't understand...
Dealing with rudeness

On Not Reacting Like A Loser
Questions Not To Ask
Good and Bad Questions
If You Can't Get An Answer
How To Answer Questions in a Helpful Way
Related Resources
Acknowledgements

Disclaimer

Many project websites link to this document in their sections on how to get help. That's fine, it's the use we intended — but if you are a webmaster creating such a link for your project page, please display prominently near the link notice that we are not a help desk for your project!

We have learned the hard way that without such a notice, we will repeatedly be pestered by idiots who think having published this document makes it our job to solve all the world's technical problems.

If you're reading this document because you need help, and you walk away with the impression you can get it directly from the authors of this document, you are one of the idiots in question. Don't ask us questions. We'll just ignore you. We are here to show you how to get help from people who actually know about the software or hardware you're dealing with, but 99.9% of the time that will not be us. Unless you know for certain that one of the authors is an expert on what you're dealing with, leave us alone and everybody will be happier.
Introduction

In the world of hackers, the kind of answers you get to your technical questions depends as much on the way you ask the questions as on the difficulty of developing the answer. This guide will teach you how to ask questions in a way more likely to get you a satisfactory answer.

Now that use of open source has become widespread, you can often get as good answers from other, more experienced users as from hackers. This is a Good Thing; users tend to be just a little bit more tolerant of the kind of failures newbies often have. Still, treating experienced users like hackers in the ways we recommend here will generally be the most effective way to get useful answers out of them, too.

The first thing to understand is that hackers actually like hard problems and good, thought-provoking questions about them. If we didn't, we wouldn't be here. If you give us an interesting question to chew on we'll be grateful to you; good questions are a stimulus and a gift. Good questions help us develop our understanding, and often reveal problems we might not have noticed or thought about otherwise. Among hackers, “Good question!” is a strong and sincere compliment.

Despite this, hackers have a reputation for meeting simple questions with what looks like hostility or arrogance. It sometimes looks like we're reflexively rude to newbies and the ignorant. But this isn't really true.

What we are, unapologetically, is hostile to people who seem to be unwilling to think or to do their own homework before asking questions. People like that are time sinks — they take without giving back, and they waste time we could have spent on another question more interesting and another person more worthy of an answer. We call people like this “losers” (and for historical reasons we sometimes spell it “lusers”).

We realize that there are many people who just want to use the software we write, and who have no interest in learning technical details. For most people, a computer is merely a tool, a means to an end; they have more important things to do and lives to live. We acknowledge that, and don't expect everyone to take an interest in the technical matters that fascinate us. Nevertheless, our style of answering questions is tuned for people who do take such an interest and are willing to be active participants in problem-solving. That's not going to change. Nor should it; if it did, we would become less effective at the things we do best.

We're (largely) volunteers. We take time out of busy lives to answer questions, and at times we're overwhelmed with them. So we filter ruthlessly. In particular, we throw away questions from people who appear to be losers in order to spend our question-answering time more efficiently, on winners.

If you find this attitude obnoxious, condescending, or arrogant, check your assumptions. We're not asking you to genuflect to us — in fact, most of us would love nothing more than to deal with you as an equal and welcome you into our culture, if you put in the effort required to make that possible. But it's simply not efficient for us to try to help people who are not willing to help themselves. It's OK to be ignorant; it's not OK to play stupid.

So, while it isn't necessary to already be technically competent to get attention from us, it is necessary to demonstrate the kind of attitude that leads to competence — alert, thoughtful, observant, willing to be an active partner in developing a solution. If you can't live with this sort of discrimination, we suggest you pay somebody for a commercial support contract instead of asking hackers to personally donate help to you.

If you decide to come to us for help, you don't want to be one of the losers. You don't want to seem like one, either. The best way to get a rapid and responsive answer is to ask it like a person with smarts, confidence, and clues who just happens to need help on one particular problem.

(Improvements to this guide are welcome. You can mail suggestions to esr@thyrsus.com or respond-auto@linuxmafia.com. Note however that this document is not intended to be a general guide to netiquette, and we will generally reject suggestions that are not specifically related to eliciting useful answers in a technical forum.)
Before You Ask

Before asking a technical question by e-mail, or in a newsgroup, or on a website chat board, do the following:

1.

Try to find an answer by searching the archives of the forum you plan to post to.
2.

Try to find an answer by searching the Web.
3.

Try to find an answer by reading the manual.
4.

Try to find an answer by reading a FAQ.
5.

Try to find an answer by inspection or experimentation.
6.

Try to find an answer by asking a skilled friend.
7.

If you're a programmer, try to find an answer by reading the source code.

When you ask your question, display the fact that you have done these things first; this will help establish that you're not being a lazy sponge and wasting people's time. Better yet, display what you have learned from doing these things. We like answering questions for people who have demonstrated they can learn from the answers.

Use tactics like doing a Google search on the text of whatever error message you get (searching Google groups as well as Web pages). This might well take you straight to fix documentation or a mailing list thread answering your question. Even if it doesn't, saying “I googled on the following phrase but didn't get anything that looked promising” is a good thing to do in e-mail or news postings requesting help, if only because it records what searches won't help. It will also help to direct other people with similar problems to your thread by linking the search terms to what will hopefully be your problem and resolution thread.

Take your time. Do not expect to be able to solve a complicated problem with a few seconds of Googling. Read and understand the FAQs, sit back, relax and give the problem some thought before approaching experts. Trust us, they will be able to tell from your questions how much reading and thinking you did, and will be more willing to help if you come prepared. Don't instantly fire your whole arsenal of questions just because your first search turned up no answers (or too many).

Prepare your question. Think it through. Hasty-sounding questions get hasty answers, or none at all. The more you do to demonstrate that having put thought and effort into solving your problem before seeking help, the more likely you are to actually get help.

Beware of asking the wrong question. If you ask one that is based on faulty assumptions, J. Random Hacker is quite likely to reply with a uselessly literal answer while thinking “Stupid question...”, and hoping the experience of getting what you asked for rather than what you needed will teach you a lesson.

Never assume you are entitled to an answer. You are not; you aren't, after all, paying for the service. You will earn an answer, if you earn it, by asking a substantial, interesting, and thought-provoking question — one that implicitly contributes to the experience of the community rather than merely passively demanding knowledge from others.

On the other hand, making it clear that you are able and willing to help in the process of developing the solution is a very good start. “Would someone provide a pointer?”, “What is my example missing?”, and “What site should I have checked?” are more likely to get answered than “Please post the exact procedure I should use.” because you're making it clear that you're truly willing to complete the process if someone can just point you in the right direction.
When You Ask
Choose your forum carefully

Be sensitive in choosing where you ask your question. You are likely to be ignored, or written off as a loser, if you:

*

post your question to a forum where it's off topic
*

post a very elementary question to a forum where advanced technical questions are expected, or vice-versa
*

cross-post to too many different newsgroups
*

post a personal e-mail to somebody who is neither an acquaintance of yours nor personally responsible for solving your problem

Hackers blow off questions that are inappropriately targeted in order to try to protect their communications channels from being drowned in irrelevance. You don't want this to happen to you.

The first step, therefore, is to find the right forum. Again, Google and other Web-searching methods are your friend. Use them to find the project webpage most closely associated with the hardware or software giving you difficulties. Usually it will have links to a FAQ (Frequently Asked Questions) list, and to project mailing lists and their archives. These mailing lists are the final places to go for help, if your own efforts (including reading those FAQs you found) do not find you a solution. The project page may also describe a bug-reporting procedure, or have a link to one; if so, follow it.

Shooting off an e-mail to a person or forum which you are not familiar with is risky at best. For example, do not assume that the author of an informative webpage wants to be your free consultant. Do not make optimistic guesses about whether your question will be welcome — if you're unsure, send it elsewhere, or refrain from sending it at all.

When selecting a Web forum, newsgroup or mailing list, don't trust the name by itself too far; look for a FAQ or charter to verify your question is on-topic. Read some of the back traffic before posting so you'll get a feel for how things are done there. In fact, it's a very good idea to do a keyword search for words relating to your problem on the newsgroup or mailing list archives before you post. It may find you an answer, and if not it will help you formulate a better question.

Don't shotgun-blast all the available help channels at once, that's like yelling and irritates people. Step through them softly.

Know what your topic is! One of the classic mistakes is asking questions about the Unix or Windows programming interface in a forum devoted to a language or library or tool portable across both. If you don't understand why this is a blunder, you'd be best off not asking any questions at all until you get it.

In general, questions to a well-selected public forum are more likely to get useful answers than equivalent questions to a private one. There are multiple reasons for this. One is simply the size of the pool of potential respondents. Another is the size of the audience; hackers would rather answer questions that educate many people than questions serving only a few.

Understandably, skilled hackers and authors of popular software are already receiving more than their fair share of mis-targeted messages. By adding to the flood, you could in extreme cases even be the straw that breaks the camel's back — quite a few times, contributors to popular projects have withdrawn their support because collateral damage in the form of useless e-mail traffic to their personal accounts became unbearable.
Web and IRC forums directed towards newbies often give the quickest response

Your local user group, or your Linux distribution, may advertise a Web forum or IRC channel where newbies can get help. (In non-English-speaking countries newbie forums are still more likely to be mailing lists.) These are good first places to ask, especially if you think you may have tripped over a relatively simple or common problem. An advertised IRC channel is an open invitation to ask questions there and often get answers in real time.

In fact, if you got the program that is giving you problems from a Linux distribution (as common today), it may be better to ask in the distro's forum/list before trying the program's project forum/list. The project's hackers may just say, “use our build”.

Before posting to any Web forum, check if it has a Search feature. If it does, try a couple of keyword searches for something like your problem; it just might help. If you did a general Web search before (as you should have), search the forum anyway; your Web-wide search engine might not have all of this forum indexed recently.

There is an increasing tendency for projects to do user support over a Web forum or IRC channel, with e-mail reserved more for development traffic. So look for those channels first when seeking project-specific help.
As a second step, use project mailing lists

When a project has a development mailing list, write to the mailing list, not to individual developers, even if you believe you know who can best answer your question. Check the documentation of the project and its homepage for the address of a project mailing list, and use it. There are several good reasons for this policy:

*

Any question good enough to be asked of one developer will also be of value to the whole group. Contrariwise, if you suspect your question is too dumb for a mailing list, it's not an excuse to harass individual developers.
*

Asking questions on the list distributes load among developers. The individual developer (especially if he's the project leader) may be too busy to answer your questions.
*

Most mailing lists are archived and the archives are indexed by search engines. If you ask your question on-list and it is answered, a future querent could find your question and the answer on the Web instead of asking it again.
*

If certain questions are seen to be asked often, developers can use that information to improve the documentation or the software itself to be less confusing. But if those questions are asked in private, nobody has the complete picture of what questions are asked most often.

If a project has both a “user” and a “developer” (or “hacker”) mailing list or Web forum, and you are not hacking on the code, ask in the “user” list/forum. Do not assume that you will be welcome on the developer list, where they're likely to experience your question as noise disrupting their developer traffic.

However, if you are sure your question is non-trivial, and you get no answer in the “user” list/forum for several days, try the “developer” one. You would be well advised to lurk there for a few days before posting to learn the local folkways (actually this is good advice on any private or semi-private list).

If you cannot find a project's mailing list address, but only see the address of the maintainer of the project, go ahead and write to the maintainer. But even in that case, don't assume that the mailing list doesn't exist. Mention in your e-mail that you tried and could not find the appropriate mailing list. Also mention that you don't object to having your message forwarded to other people. (Many people believe that private e-mail should remain private, even if there is nothing secret in it. By allowing your message to be forwarded you give your correspondent a choice about how to handle your e-mail.)
Use meaningful, specific subject headers

On mailing lists, newsgroups or Web forums, the subject header is your golden opportunity to attract qualified experts' attention in around 50 characters or fewer. Don't waste it on babble like “Please help me” (let alone “PLEASE HELP ME!!!!”; messages with subjects like that get discarded by reflex). Don't try to impress us with the depth of your anguish; use the space for a super-concise problem description instead.

One good convention for subject headers, used by many tech support organizations, is “object - deviation”. The “object” part specifies what thing or group of things is having a problem, and the “deviation” part describes the deviation from expected behavior.

Stupid:

HELP! Video doesn't work properly on my laptop!
Smart:

X.org 6.8.1 misshapen mouse cursor, Fooware MV1005 vid. chipset
Smarter:

X.org 6.8.1 mouse cursor on Fooware MV1005 vid. chipset - is misshapen

The process of writing an “object-deviation” description will help you organize your thinking about the problem in more detail. What is affected? Just the mouse cursor or other graphics too? Is this specific to the X.org version of X? To version 6.8.1? Is this specific to Fooware video chipsets? To model MV1005? A hacker who sees the result can immediately understand what it is that you are having a problem with and the problem you are having, at a glance.

More generally, imagine looking at the index of an archive of questions, with just the subject lines showing. Make your subject line reflect your question well enough that the next guy searching the archive with a question similar to yours will be able to follow the thread to an answer rather than posting the question again.

If you ask a question in a reply, be sure to change the subject line to indicate that you're asking a question. A Subject line that looks like “Re: test” or “Re: new bug” is less likely to attract useful amounts of attention. Also, pare quotation of previous messages to the minimum consistent with cluing in new readers.

Do not simply hit reply to a list message in order to start an entirely new thread. This will limit your audience. Some mail readers, like mutt, allow the user to sort by thread and then hide messages in a thread by folding the thread. Folks who do that will never see your message.

Changing the subject is not sufficient. Mutt, and probably other mail readers, looks at other information in the e-mail's headers to assign it to a thread, not the subject line. Instead start an entirely new e-mail.

On Web forums the rules of good practice are slightly different, because messages are usually much more tightly bound to specific discussion threads and often invisible outside those threads. Changing the subject when asking a question in reply is not essential. Not all forums even allow separate subject lines on replies, and nearly nobody reads them when they do. However, asking a question in a reply is a dubious practice in itself, because it will only be seen by those who are watching this thread. So, unless you are sure you want to ask only the people currently active in the thread, start a new one.
Make it easy to reply

Finishing your query with “Please send your reply to... ” makes it quite unlikely you will get an answer. If you can't be bothered to take even the few seconds required to set up a correct Reply-To header in your mail agent, we can't be bothered to take even a few seconds to think about your problem. If your mail program doesn't permit this, get a better mail program. If your operating system doesn't support any e-mail programs that permit this, get a better operating system.

In Web forums, asking for a reply by e-mail is outright rude, unless you believe the information may be sensitive (and somebody will, for some unknown reason, let you but not the whole forum know it). If you want an e-mail copy when somebody replies in the thread, request that the Web forum send it; this feature is supported almost everywhere under options like “watch this thread”, “send e-mail on answers”, etc.
Write in clear, grammatical, correctly-spelled language

We've found by experience that people who are careless and sloppy writers are usually also careless and sloppy at thinking and coding (often enough to bet on, anyway). Answering questions for careless and sloppy thinkers is not rewarding; we'd rather spend our time elsewhere.

So expressing your question clearly and well is important. If you can't be bothered to do that, we can't be bothered to pay attention. Spend the extra effort to polish your language. It doesn't have to be stiff or formal — in fact, hacker culture values informal, slangy and humorous language used with precision. But it has to be precise; there has to be some indication that you're thinking and paying attention.

Spell, punctuate, and capitalize correctly. Don't confuse “its” with “it's”, “loose” with “lose”, or “discrete” with “discreet”. Don't TYPE IN ALL CAPS; this is read as shouting and considered rude. (All-smalls is only slightly less annoying, as it's difficult to read. Alan Cox can get away with it, but you can't.)

More generally, if you write like a semi-literate boob you will very likely be ignored. So don't use instant-messaging shortcuts. Spelling "you" as "u" makes you look like a semi-literate boob to save two entire keystrokes. Worse: writing like a l33t script kiddie hax0r is the absolute kiss of death and guarantees you will receive nothing but stony silence (or, at best, a heaping helping of scorn and sarcasm) in return.

If you are asking questions in a forum that does not use your native language, you will get a limited amount of slack for spelling and grammar errors — but no extra slack at all for laziness (and yes, we can usually spot that difference). Also, unless you know what your respondent's languages are, write in English. Busy hackers tend to simply flush questions in languages they don't understand, and English is the working language of the Internet. By writing in English you minimize your chances that your question will be discarded unread.
Send questions in accessible, standard formats

If you make your question artificially hard to read, it is more likely to be passed over in favor of one that isn't. So:

*

Send plain text mail, not HTML. (It's not hard to turn off HTML.)
*

MIME attachments are usually OK, but only if they are real content (such as an attached source file or patch), and not merely boilerplate generated by your mail client (such as another copy of your message).
*

Don't send e-mail in which entire paragraphs are single multiply-wrapped lines. (This makes it too difficult to reply to just part of the message.) Assume that your respondents will be reading mail on 80-character-wide text displays and set your line wrap accordingly, to something less than 80.
*

However, do not wrap data (such as log file dumps or session transcripts) at any fixed column width. Data should be included as-is, so respondents can have confidence that they are seeing what you saw.
*

Don't send MIME Quoted-Printable encoding to an English-language forum. This encoding can be necessary when you're posting in a language ASCII doesn't cover, but many e-mail agents don't support it. When they break, all those =20 glyphs scattered through the text are ugly and distracting — or may actively sabotage the semantics of your text.
*

Never, ever expect hackers to be able to read closed proprietary document formats like Microsoft Word or Excel. Most hackers react to these about as well as you would to having a pile of steaming pig manure dumped on your doorstep. Even when they can cope, they resent having to do so.
*

If you're sending e-mail from a Windows machine, turn off Microsoft's stupid “Smart Quotes” feature. This is so you'll avoid sprinkling garbage characters through your mail.
*

In Web forums, do not abuse “smiley” and “HTML” features (when they are present). A smiley or two is usually OK, but colored fancy text tends to make people think you are lame. Seriously overusing smileys and color and fonts will make you come off like a giggly teenage girl, which is not generally a good idea unless you are more interested in sex than answers.

If you're using a graphical-user-interface mail client such as Netscape Messenger, MS Outlook, or their ilk, beware that it may violate these rules when used with its default settings. Most such clients have a menu-based “View Source” command. Use this on something in your sent-mail folder, verifying sending of plain text without unnecessary attached crud.
Be precise and informative about your problem

*

Describe the symptoms of your problem or bug carefully and clearly.
*

Describe the environment in which it occurs (machine, OS, application, whatever). Provide your vendor's distribution and release level (e.g.: “Fedora Core 7”, “Slackware 9.1”, etc.).
*

Describe the research you did to try and understand the problem before you asked the question.
*

Describe the diagnostic steps you took to try and pin down the problem yourself before you asked the question.
*

Describe any possibly relevant recent changes in your computer or software configuration.

Do the best you can to anticipate the questions a hacker will ask, and answer them in advance in your request for help.

Simon Tatham has written an excellent essay entitled How to Report Bugs Effectively. I strongly recommend that you read it.
Volume is not precision

You need to be precise and informative. This end is not served by simply dumping huge volumes of code or data into a help request. If you have a large, complicated test case that is breaking a program, try to trim it and make it as small as possible.

This is useful for at least three reasons. One: being seen to invest effort in simplifying the question makes it more likely you'll get an answer, Two: simplifying the question makes it more likely you'll get a useful answer. Three: In the process of refining your bug report, you may develop a fix or workaround yourself.
Don't claim that you have found a bug

When you are having problems with a piece of software, don't claim you have found a bug unless you are very, very sure of your ground. Hint: unless you can provide a source-code patch that fixes the problem, or a regression test against a previous version that demonstrates incorrect behavior, you are probably not sure enough. This applies to webpages and documentation, too; if you have found a documentation “bug”, you should supply replacement text and which pages it should go on.

Remember, there are many other users that are not experiencing your problem. Otherwise you would have learned about it while reading the documentation and searching the Web (you did do that before complaining, didn't you?). This means that very probably it is you who are doing something wrong, not the software.

The people who wrote the software work very hard to make it work as well as possible. If you claim you have found a bug, you'll be impugning their competence, which may offend some of them even if you are correct. It's especially undiplomatic to yell “bug” in the Subject line.

When asking your question, it is best to write as though you assume you are doing something wrong, even if you are privately pretty sure you have found an actual bug. If there really is a bug, you will hear about it in the answer. Play it so the maintainers will want to apologize to you if the bug is real, rather than so that you will owe them an apology if you have messed up.
Grovelling is not a substitute for doing your homework

Some people who get that they shouldn't behave rudely or arrogantly, demanding an answer, retreat to the opposite extreme of grovelling. “I know I'm just a pathetic newbie loser, but...”. This is distracting and unhelpful. It's especially annoying when it's coupled with vagueness about the actual problem.

Don't waste your time, or ours, on crude primate politics. Instead, present the background facts and your question as clearly as you can. That is a better way to position yourself than by grovelling.

Sometimes Web forums have separate places for newbie questions. If you feel you do have a newbie question, just go there. But don't grovel there either.
Describe the problem's symptoms, not your guesses

It's not useful to tell hackers what you think is causing your problem. (If your diagnostic theories were such hot stuff, would you be consulting others for help?) So, make sure you're telling them the raw symptoms of what goes wrong, rather than your interpretations and theories. Let them do the interpretation and diagnosis. If you feel it's important to state your guess, clearly label it as such and describe why that answer isn't working for you.

Stupid:

I'm getting back-to-back SIG11 errors on kernel compiles, and suspect a hairline crack on one of the motherboard traces. What's the best way to check for those?
Smart:

My home-built K6/233 on an FIC-PA2007 motherboard (VIA Apollo VP2 chipset) with 256MB Corsair PC133 SDRAM starts getting frequent SIG11 errors about 20 minutes after power-on during the course of kernel compiles, but never in the first 20 minutes. Rebooting doesn't restart the clock, but powering down overnight does. Swapping out all RAM didn't help. The relevant part of a typical compile session log follows.

Since the preceding point seems to be a tough one for many people to grasp, here's a phrase to remind you: "All diagnosticians are from Missouri." That US state's official motto is "Show me" (earned in 1899, when Congressman Willard D. Vandiver said "I come from a country that raises corn and cotton and cockleburs and Democrats, and frothy eloquence neither convinces nor satisfies me. I'm from Missouri. You've got to show me.") In diagnosticians' case, it's not a matter of skepticism, but rather a literal, functional need to see whatever is as close as possible to the same raw evidence that you see, rather than your surmises and summaries. Show us.
Describe your problem's symptoms in chronological order

The clues most useful in figuring out something that went wrong often lie in the events immediately prior. So, your account should describe precisely what you did, and what the machine and software did, leading up to the blowup. In the case of command-line processes, having a session log (e.g., using the script utility) and quoting the relevant twenty or so lines is very useful.

If the program that blew up on you has diagnostic options (such as -v for verbose), try to select options that will add useful debugging information to the transcript. Remember that more is not necessarily better; try to choose a debug level that will inform rather than drowning the reader in junk.

If your account ends up being long (more than about four paragraphs), it might be useful to succinctly state the problem up top, then follow with the chronological tale. That way, hackers will know what to watch for in reading your account.
Describe the goal, not the step

If you are trying to find out how to do something (as opposed to reporting a bug), begin by describing the goal. Only then describe the particular step towards it that you are blocked on.

Often, people who need technical help have a high-level goal in mind and get stuck on what they think is one particular path towards the goal. They come for help with the step, but don't realize that the path is wrong. It can take substantial effort to get past this.

Stupid:

How do I get the color-picker on the FooDraw program to take a hexadecimal RGB value?
Smart:

I'm trying to replace the color table on an image with values of my choosing. Right now the only way I can see to do this is by editing each table slot, but I can't get FooDraw's color picker to take a hexadecimal RGB value.

The second version of the question is smart. It allows an answer that suggests a tool better suited to the task.
Don't ask people to reply by private e-mail

Hackers believe solving problems should be a public, transparent process during which a first try at an answer can and should be corrected if someone more knowledgeable notices that it is incomplete or incorrect. Also, helpers get some of their reward for being respondents from being seen to be competent and knowledgeable by their peers.

When you ask for a private reply, you are disrupting both the process and the reward. Don't do this. It's the respondent's choice whether to reply privately — and if he does, it's usually because he thinks the question is too ill-formed or obvious to be interesting to others.

There is one limited exception to this rule. If you think the question is such that you are likely to get many answers that are all closely similar, then the magic words are “e-mail me and I'll summarize the answers for the group”. It is courteous to try and save the mailing list or newsgroup a flood of substantially identical postings — but you have to keep the promise to summarize.
Be explicit about your question

Open-ended questions tend to be perceived as open-ended time sinks. Those people most likely to be able to give you a useful answer are also the busiest people (if only because they take on the most work themselves). People like that are allergic to open-ended time sinks, thus they tend to be allergic to open-ended questions.

You are more likely to get a useful response if you are explicit about what you want respondents to do (provide pointers, send code, check your patch, whatever). This will focus their effort and implicitly put an upper bound on the time and energy a respondent must allocate to helping you. This is good.

To understand the world the experts live in, think of expertise as an abundant resource and time to respond as a scarce one. The less of a time commitment you implicitly ask for, the more likely you are to get an answer from someone really good and really busy.

So it is useful to frame your question to minimize the time commitment required for an expert to field it — but this is often not the same thing as simplifying the question. Thus, for example, “Would you give me a pointer to a good explanation of X?” is usually a smarter question than “Would you explain X, please?”. If you have some malfunctioning code, it is usually smarter to ask for someone to explain what's wrong with it than it is to ask someone to fix it.
When asking about code

Don't ask others to debug your broken code without giving a hint what sort of problem they should be searching for. Posting a few hundred lines of code, saying "it doesn't work", will get you ignored. Posting a dozen lines of code, saying "after line 7 I was expecting to see , but occurred instead" is much more likely to get you a response.

If you simply want a code review, say as much up front, and be sure to mention what areas you think might particularly need review and why.
Don't post homework questions

Hackers are good at spotting homework questions; most of us have done them ourselves. Those questions are for you to work out, so that you will learn from the experience. It is OK to ask for hints, but not for entire solutions.

If you suspect you have been passed a homework question, but can't solve it anyway, try asking in a user group forum or (as a last resort) in a “user” list/forum of a project. While the hackers will spot it, some of the advanced users may at least give you a hint.
Prune pointless queries

Resist the temptation to close your request for help with semantically-null questions like “Can anyone help me?” or “Is there an answer?” First: if you've written your problem description halfway competently, such tacked-on questions are at best superfluous. Second: because they are superfluous, hackers find them annoying — and are likely to return logically impeccable but dismissive answers like “Yes, you can be helped” and “No, there is no help for you.”

In general, asking yes-or-no questions is a good thing to avoid unless you want a yes-or-no answer.
Don't flag your question as “Urgent”, even if it is for you

That's your problem, not ours. Claiming urgency is very likely to be counter-productive: most hackers will simply delete such messages as rude and selfish attempts to elicit immediate and special attention.

There is one semi-exception. It can be worth mentioning if you're using the program in some high-profile place, one that the hackers will get excited about; in such a case, if you're under time pressure, and you say so politely, people may get interested enough to answer faster.

This is a very risky thing to do, however, because the hackers' metric for what is exciting probably differs from yours. Posting from the International Space Station would qualify, for example, but posting on behalf of a feel-good charitable or political cause would almost certainly not. In fact, posting “Urgent: Help me save the fuzzy baby seals!” will reliably get you shunned or flamed even by hackers who think fuzzy baby seals are important.

If you find this mysterious, re-read the rest of this how-to repeatedly until you understand it before posting anything at all.
Courtesy never hurts, and sometimes helps

Be courteous. Use “Please” and “Thanks for your attention” or “Thanks for your consideration”. Make it clear you appreciate the time people spend helping you for free.

To be honest, this isn't as important as (and cannot substitute for) being grammatical, clear, precise and descriptive, avoiding proprietary formats etc.; hackers in general would rather get somewhat brusque but technically sharp bug reports than polite vagueness. (If this puzzles you, remember that we value a question by what it teaches us.)

However, if you've got your technical ducks in a row, politeness does increase your chances of getting a useful answer.

(We must note that the only serious objection we've received from veteran hackers to this HOWTO is with respect to our previous recommendation to use “Thanks in advance”. Some hackers feel this connotes an intention not to thank anybody afterwards. Our recommendation is to either say “Thanks in advance” first and thank respondents afterwards, or express courtesy in a different way, such as by saying “Thanks for your attention” or “Thanks for your consideration”.)
Follow up with a brief note on the solution

Send a note after the problem has been solved to all who helped you; let them know how it came out and thank them again for their help. If the problem attracted general interest in a mailing list or newsgroup, it's appropriate to post the followup there.

Optimally, the reply should be to the thread started by the original question posting, and should have ‘FIXED’, ‘RESOLVED’ or an equally obvious tag in the subject line. On mailing lists with fast turnaround, a potential respondent who sees a thread about “Problem X” ending with “Problem X - FIXED” knows not to waste his/her time even reading the thread (unless (s)he) personally finds Problem X interesting) and can therefore use that time solving a different problem.

Your followup doesn't have to be long and involved; a simple “Howdy — it was a failed network cable! Thanks, everyone. - Bill” would be better than nothing. In fact, a short and sweet summary is better than a long dissertation unless the solution has real technical depth. Say what action solved the problem, but you need not replay the whole troubleshooting sequence.

For problems with some depth, it is appropriate to post a summary of the troubleshooting history. Describe your final problem statement. Describe what worked as a solution, and indicate avoidable blind alleys after that. The blind alleys should come after the correct solution and other summary material, rather than turning the follow-up into a detective story. Name the names of people who helped you; you'll make friends that way.

Besides being courteous and informative, this sort of followup will help others searching the archive of the mailing-list/newsgroup/forum to know exactly which solution helped you and thus may also help them.

Last, and not least, this sort of followup helps everybody who assisted feel a satisfying sense of closure about the problem. If you are not a techie or hacker yourself, trust us that this feeling is very important to the gurus and experts you tapped for help. Problem narratives that trail off into unresolved nothingness are frustrating things; hackers itch to see them resolved. The goodwill that scratching that itch earns you will be very, very helpful to you next time you need to pose a question.

Consider how you might be able to prevent others from having the same problem in the future. Ask yourself if a documentation or FAQ patch would help, and if the answer is yes send that patch to the maintainer.

Among hackers, this sort of good followup behavior is actually more important than conventional politeness. It's how you get a reputation for playing well with others, which can be a very valuable asset.
How To Interpret Answers
RTFM and STFW: How To Tell You've Seriously Screwed Up

There is an ancient and hallowed tradition: if you get a reply that reads “RTFM”, the person who sent it thinks you should have Read The Fucking Manual. He or she is almost certainly right. Go read it.

RTFM has a younger relative. If you get a reply that reads “STFW”, the person who sent it thinks you should have Searched The Fucking Web. He or she is almost certainly right. Go search it. (The milder version of this is when you are told “Google is your friend!”)

In Web forums, you may also be told to search the forum archives. In fact, someone may even be so kind as to provide a pointer to the previous thread where this problem was solved. But do not rely on this consideration; do your archive-searching before asking.

Often, the person telling you to do a search has the manual or the web page with the information you need open, and is looking at it as he or she types. These replies mean that he thinks (a) the information you need is easy to find, and (b) you will learn more if you seek out the information than if you have it spoon-fed to you.

You shouldn't be offended by this; by hacker standards, your respondent is showing you a rough kind of respect simply by not ignoring you. You should instead be thankful for this grandmotherly kindness.
If you don't understand...

If you don't understand the answer, do not immediately bounce back a demand for clarification. Use the same tools that you used to try and answer your original question (manuals, FAQs, the Web, skilled friends) to understand the answer. Then, if you still need to ask for clarification, exhibit what you have learned.

For example, suppose I tell you: “It sounds like you've got a stuck zentry; you'll need to clear it.” Then: here's a bad followup question: “What's a zentry?” Here's a good followup question: “OK, I read the man page and zentries are only mentioned under the -z and -p switches. Neither of them says anything about clearing zentries. Is it one of these or am I missing something here?”
Dealing with rudeness

Much of what looks like rudeness in hacker circles is not intended to give offense. Rather, it's the product of the direct, cut-through-the-bullshit communications style that is natural to people who are more concerned about solving problems than making others feel warm and fuzzy.

When you perceive rudeness, try to react calmly. If someone is really acting out, it is very likely a senior person on the list or newsgroup or forum will call him or her on it. If that doesn't happen and you lose your temper, it is likely that the person you lose it at was behaving within the hacker community's norms and you will be considered at fault. This will hurt your chances of getting the information or help you want.

On the other hand, you will occasionally run across rudeness and posturing that is quite gratuitous. The flip-side of the above is that it is acceptable form to slam real offenders quite hard, dissecting their misbehavior with a sharp verbal scalpel. Be very, very sure of your ground before you try this, however. The line between correcting an incivility and starting a pointless flamewar is thin enough that hackers themselves not infrequently blunder across it; if you are a newbie or an outsider, your chances of avoiding such a blunder are low. If you're after information rather than entertainment, it's better to keep your fingers off the keyboard than to risk this.

(Some people assert that many hackers have a mild form of autism or Asperger's Syndrome, and are actually missing some of the brain circuitry that lubricates “normal” human social interaction. This may or may not be true. If you are not a hacker yourself, it may help you cope with our eccentricities if you think of us as being brain-damaged. Go right ahead. We won't care; we like being whatever it is we are, and generally have a healthy skepticism about clinical labels.)

In the next section, we'll talk about a different issue; the kind of “rudeness” you'll see when you misbehave.
On Not Reacting Like A Loser

Odds are you'll screw up a few times on hacker community forums — in ways detailed in this article, or similar. And you'll be told exactly how you screwed up, possibly with colourful asides. In public.

When this happens, the worst thing you can do is whine about the experience, claim to have been verbally assaulted, demand apologies, scream, hold your breath, threaten lawsuits, complain to people's employers, leave the toilet seat up, etc. Instead, here's what you do:

Get over it. It's normal. In fact, it's healthy and appropriate.

Community standards do not maintain themselves: They're maintained by people actively applying them, visibly, in public. Don't whine that all criticism should have been conveyed via private e-mail: That's not how it works. Nor is it useful to insist you've been personally insulted when someone comments that one of your claims was wrong, or that his views differ. Those are loser attitudes.

There have been hacker forums where, out of some misguided sense of hyper-courtesy, participants are banned from posting any fault-finding with another's posts, and told “Don't say anything if you're unwilling to help the user.” The resulting departure of clueful participants to elsewhere causes them to descend into meaningless babble and become useless as technical forums.

Exaggeratedly “friendly” (in that fashion) or useful: Pick one.

Remember: When that hacker tells you that you've screwed up, and (no matter how gruffly) tells you not to do it again, he's acting out of concern for (1) you and (2) his community. It would be much easier for him to ignore you and filter you out of his life. If you can't manage to be grateful, at least have a little dignity, don't whine, and don't expect to be treated like a fragile doll just because you're a newcomer with a theatrically hypersensitive soul and delusions of entitlement.

Sometimes people will attack you personally, flame without an apparent reason, etc., even if you don't screw up (or have only screwed up in their imagination). In this case, complaining is the way to really screw up.

These flamers are either lamers who don't have a clue but believe themselves to be experts, or would-be psychologists testing whether you'll screw up. The other readers either ignore them, or find ways to deal with them on their own. The flamers' behavior creates problems for themselves, which don't have to concern you.

Don't let yourself be drawn into a flamewar, either. Most flames are best ignored — after you've checked whether they are really flames, not pointers to the ways in which you have screwed up, and not cleverly ciphered answers to your real question (this happens as well).
Questions Not To Ask

Here are some classic stupid questions, and what hackers are thinking when they don't answer them.

Q: Where can I find program or resource X?
Q: How can I use X to do Y?
Q: How can I configure my shell prompt?
Q: Can I convert an AcmeCorp document into a TeX file using the Bass-o-matic file converter?
Q: My {program, configuration, SQL statement} doesn't work
Q: I'm having problems with my Windows machine. Can you help?
Q: My program doesn't work. I think system facility X is broken.
Q: I'm having problems installing Linux or X. Can you help?
Q: How can I crack root/steal channel-ops privileges/read someone's e-mail?

Q:

Where can I find program or resource X?

A:

The same place I'd find it, fool — at the other end of a web search. Ghod, doesn't everybody know how to use Google yet?

Q:

How can I use X to do Y?

A:

If what you want is to do Y, you should ask that question without pre-supposing the use of a method that may not be appropriate. Questions of this form often indicate a person who is not merely ignorant about X, but confused about what problem Y they are solving and too fixated on the details of their particular situation. It is generally best to ignore such people until they define their problem better.

Q:

How can I configure my shell prompt?

A:

If you're smart enough to ask this question, you're smart enough to RTFM and find out yourself.

Q:

Can I convert an AcmeCorp document into a TeX file using the Bass-o-matic file converter?

A:

Try it and see. If you did that, you'd (a) learn the answer, and (b) stop wasting my time.

Q:

My {program, configuration, SQL statement} doesn't work

A:

This is not a question, and I'm not interested in playing Twenty Questions to pry your actual question out of you — I have better things to do. On seeing something like this, my reaction is normally of one of the following:

*

do you have anything else to add to that?
*

oh, that's too bad, I hope you get it fixed.
*

and this has exactly what to do with me?

Q:

I'm having problems with my Windows machine. Can you help?

A:

Yes. Throw out that Microsoft trash and install an open-source operating system like Linux or BSD.

Note: you can ask questions related to Windows machines if they are about a program that does have an official Windows build, or interacts with Windows machines (i.e., Samba). Just don't be surprised by the reply that the problem is with Windows and not the program, because Windows is so broken in general that this is very often the case.

Q:

My program doesn't work. I think system facility X is broken.

A:

While it is possible that you are the first person to notice an obvious deficiency in system calls and libraries heavily used by hundreds or thousands of people, it is rather more likely that you are utterly clueless. Extraordinary claims require extraordinary evidence; when you make a claim like this one, you must back it up with clear and exhaustive documentation of the failure case.

Q:

I'm having problems installing Linux or X. Can you help?

A:

No. I'd need hands-on access to your machine to troubleshoot this. Go ask your local Linux user group for hands-on help. (You can find a list of user groups here.)

Note: questions about installing Linux may be appropriate if you're on a forum or mailing list about a particular distribution, and the problem is with that distro; or on local user groups forums. In this case, be sure to describe the exact details of the failure. But do careful searching first, with "linux" and all suspicious pieces of hardware.

Q:

How can I crack root/steal channel-ops privileges/read someone's e-mail?

A:

You're a lowlife for wanting to do such things and a moron for asking a hacker to help you.
Good and Bad Questions

Finally, I'm going to illustrate how to ask questions in a smart way by example; pairs of questions about the same problem, one asked in a stupid way and one in a smart way.

Stupid: Where can I find out stuff about the Foonly Flurbamatic?

This question just begs for "STFW" as a reply.
Smart: I used Google to try to find “Foonly Flurbamatic 2600” on the Web, but I got no useful hits. Can I get a pointer to programming information on this device?

This one has already STFWed, and sounds like he might have a real problem.

Stupid: I can't get the code from project foo to compile. Why is it broken?

The querent assumes that somebody else screwed up. Arrogant git...
Smart: The code from project foo doesn't compile under Nulix version 6.2. I've read the FAQ, but it doesn't have anything in it about Nulix-related problems. Here's a transcript of my compilation attempt; is it something I did?

The querent has specified the environment, read the FAQ, is showing the error, and is not assuming his problems are someone else's fault. This one might be worth some attention.

Stupid: I'm having problems with my motherboard. Can anybody help?

J. Random Hacker's response to this is likely to be “Right. Do you need burping and diapering, too?” followed by a punch of the delete key.
Smart: I tried X, Y, and Z on the S2464 motherboard. When that didn't work, I tried A, B, and C. Note the curious symptom when I tried C. Obviously the florbish is grommicking, but the results aren't what one might expect. What are the usual causes of grommicking on Athlon MP motherboards? Anybody got ideas for more tests I can run to pin down the problem?

This person, on the other hand, seems worthy of an answer. He/she has exhibited problem-solving intelligence rather than passively waiting for an answer to drop from on high.

In the last question, notice the subtle but important difference between demanding “Give me an answer” and “Please help me figure out what additional diagnostics I can run to achieve enlightenment.”

In fact, the form of that last question is closely based on a real incident that happened in August 2001 on the linux-kernel mailing list (lkml). I (Eric) was the one asking the question that time. I was seeing mysterious lockups on a Tyan S2462 motherboard. The list members supplied the critical information I needed to solve them.

By asking the question in the way I did, I gave people something to chew on; I made it easy and attractive for them to get involved. I demonstrated respect for my peers' ability and invited them to consult with me as a peer. I also demonstrated respect for the value of their time by telling them the blind alleys I had already run down.

Afterwards, when I thanked everyone and remarked how well the process had worked, an lkml member observed that he thought it had worked not because I'm a “name” on that list, but because I asked the question in the proper form.

Hackers are in some ways a very ruthless meritocracy; I'm certain he was right, and that if I had behaved like a sponge I would have been flamed or ignored no matter who I was. His suggestion that I write up the whole incident as instruction to others led directly to the composition of this guide.
If You Can't Get An Answer

If you can't get an answer, please don't take it personally that we don't feel we can help you. Sometimes the members of the asked group may simply not know the answer. No response is not the same as being ignored, though admittedly it's hard to spot the difference from outside.

In general, simply re-posting your question is a bad idea. This will be seen as pointlessly annoying. Have patience: the person with your answer may be in a different time-zone and asleep. Or it may be that your question wasn't well-formed to begin with.

There are other sources of help you can go to, often sources better adapted to a novice's needs.

There are many online and local user groups who are enthusiasts about the software, even though they may never have written any software themselves. These groups often form so that people can help each other and help new users.

There are also plenty of commercial companies you can contract with for help, both large and small (Red Hat and SpikeSource are two of the best known; there are many others). Don't be dismayed at the idea of having to pay for a bit of help! After all, if your car engine blows a head gasket, chances are you would take it to a repair shop and pay to get it fixed. Even if the software didn't cost you anything, you can't expect that support to always come for free.

For popular software like Linux, there are at least 10,000 users per developer. It's just not possible for one person to handle the support calls from over 10,000 users. Remember that even if you have to pay for support, you are still paying much less than if you had to buy the software as well (and support for closed-source software is usually more expensive and less competent than support for open-source software).
How To Answer Questions in a Helpful Way

Be gentle. Problem-related stress can make people seem rude or stupid even when they're not.

Reply to a first offender off-line. There is no need of public humiliation for someone who may have made an honest mistake. A real newbie may not know how to search archives or where the FAQ is stored or posted.

If you don't know for sure, say so! A wrong but authoritative-sounding answer is worse than none at all. Don't point anyone down a wrong path simply because it's fun to sound like an expert. Be humble and honest; set a good example for both the querent and your peers.

If you can't help, don't hinder. Don't make jokes about procedures that could trash the user's setup — the poor sap might interpret these as instructions.

Ask probing questions to elicit more details. If you're good at this, the querent will learn something — and so might you. Try to turn the bad question into a good one; remember we were all newbies once.

While muttering RTFM is sometimes justified when replying to someone who is just a lazy slob, a pointer to documentation (even if it's just a suggestion to google for a key phrase) is better.

If you're going to answer the question at all, give good value. Don't suggest kludgy workarounds when somebody is using the wrong tool or approach. Suggest good tools. Reframe the question.

Help your community learn from the question. When you field a good question, ask yourself “How would the relevant documentation or FAQ have to change so that nobody has to answer this again?” Then send a patch to the document maintainer.

If you did research to answer the question, demonstrate your skills rather than writing as though you pulled the answer out of your butt. Answering one good question is like feeding a hungry person one meal, but teaching them research skills by example is showing them how to grow food for a lifetime.
Related Resources

If you need instruction in the basics of how personal computers, Unix, and the Internet work, see The Unix and Internet Fundamentals HOWTO.

When you release software or write patches for software, try to follow the guidelines in the Software Release Practice HOWTO.
Acknowledgements

Evelyn Mitchell contributed some example stupid questions and inspired the “How To Give A Good Answer” section. Mikhail Ramendik contributed some particularly valuable suggestions for improvements.

Major good news

2009-08-18T15:51:00.001+01:00

Dave is back and looks so well.Great!
Have a half an hour supervision.discussed my topic and possible solution of pilot over control.
Next stage is airbus control law and pilot model.
Come on!

How To Concentrate[zz]

2009-08-10T11:31:00.001+01:00

from How To Concentrate

"Concentration is the Most Important Intellectual Habit of Man."

Not one person in ten thousand can really concentrate. Some realize that they do not know how—others drift along the line of least resistance and let their minds vegetate, apparently never suspecting their weakness or realizing that they are an utter failure at concentration. To Cori-centre—bringing all your mental force and faculties to bear steadily on a given center with-out deviation from that exact point—whipping into line all wandering fancies—stray ideas or thoughts that go off on a tangent—to hold steadily all your power on the central thing under consideration without an instant of wavering—that is Concentration.

This ONE THING I Do

A difficult thing to do, and very few minds can do it. St. Paul gives us the shortest definition of concentration on record when he says, " This one thing I do," short, but tremendously significant. Another Bible definition is excellent: " Whatsoever thy hand findeth to do, do it with thy might." Some men work that way, intense fellows--brilliant professional men—big business men—executives—leaders in the world of finance—science—invention—literature—education—it matters not what kind of work, the point is that when these men pitch hay, they pitch hay —when they write a book, they write a book—when they manage a sales campaign, they man-age a sales campaign. That one thing they do at that one time, and nothing else, and every ounce they have goes into the doing. But back of all this has been a lot of mental discipline, a lot of habit-forming, a lot of brain-building. Let us consider some of the steps by which they have climbed. To the ambitious student, I offer five practical aids to concentration, planned to meet the needs of one who wishes to build from the ground up. We must assume as prerequisites, interest and attention, which have already been discussed.

AIDS TO CONCENTRATION

These aids will do more than help you to follow a memory course; they deal with your daily work. Concentration applies to all the activities of life. It should be established as a life habit. To all who think, I bring this message, Think it with thy might. Make a business of doing one thing at a time with all your soul. Chesterfield was right when he said, " There is time enough for everything in the course of a day if we do but one thing at a time, but there is not time enough in a year if we try to do two things at a time."

PERIODICAL RELAXATION

It may seem paradoxical that the first aid to better concentration refers to relaxation. But I have observed that some of the most intense intellects fail in their concentration because they never relax. Failure to let go between efforts is their chief stumbling block. They keep them-selves tense, nervous, " keyed-up " all the time, even when there is no need for it, thereby wasting nervous energy. They find it very difficult to " let go "—to relieve the high-tension by a little natural, wholesome relaxation. Possibly they feel like the Irishman who was trapped on the fourth floor of a burning building. He fought his way to the window but was afraid to jump. The flames drove him on until he was hanging to the window ledge with his hands. His friends, in the street below, seeing the walls were about to fall, kept shouting at him to " let go." Finally, he growled back at them between set teeth—" How kin I let go when it's all I can do to hang on? " But we must learn to let go—to relax completely—before each period of in-tense concentration. Here is the working principle: Relaxation precedes perfect concentration. A delightful illustration of this point is given by Elizabeth Towne.

Six puppies were playing in the barn. The barn door was closed and with the world shut out, they were giving themselves up completely to the; spirit of play. Two of them were staging a mock battle over a feather, while the others were rolling over and over in the loose straw on the barn floor in utter enjoyment.

Suddenly the barn door softly creaked. 'Instantly every puppy came to attention; heads up —tails up—bodies rigid—bright eyes fixed in intense concentration on that door, as it slowly swung open. A moment before they had been in a state of complete relaxation. Now, they offered a perfect example of concentration as they stood at attention, waiting and watching for the unknown danger that Might be coming from the other. Side of the barn door.

All great mental achievement has been preceded by periods of absolute rest or relaxtion! During.this time fatigue disappears the nervous forces. recuperate and the minds-stores up fresh energy axed establishes a reserve to draw upon during" the hours of intense concentration demanded by the. big task high lies must ahead.

Very often this preparation period of relaxation determines. the success or failure of the uder taking.-Herbert -Spencer, once made, a speech on.," The Gospel "of Relaxation will, which he pointed ,out that continual tress and strain high tension without periods relaxation were responsible for much chronic fatigue and many a nervous breakdown. is far better to indulge. It in an voluntary let down than: to Offer an involuntary breakdown, Different .people take their relaxation best in different ways, but, whether in complete rest, of play or wholesome laughter, it must come before any sustained effort of concentration. Nature itself requires cycles of growth and rest. Take your breathing spell before the battle.

MENTAL FREEDOM

The next step is to free the mind. Nothing is of greater aid to concentration. In fact, unless you are able to do this, concentration is impossible. When. harassed by the three devils, hurry, worry, and f ear, the mind never has a fair chance to center on anything. " Worry generates a poison at the roots of memory." But in your period of relaxation, you have an excellent opportunity to free the mind—now is your chance to eliminate all mental handicaps and get ready for the race. Not only hurry, worry, and fear must be thrown overboard, but anything and everything that troubles you and disturbs your serenity and your peace of mind. Out they go ! You should not indulge in day-dreaming, either, or mental drifting. Clear the mental horizon; give yourself a clean slate to write upon when your hour of concentration comes. And when it comes, if you have availed yourself of these first two aids I have given, you will be, possessed of that rare thing, mental poise.

THE PROPER ENVIRONMENT

In order to keep it, utilize the third aid: right conditions. Now, it is true that a trained mind can concentrate under any conditions—in the roar and din of .crowded cities or the busy hum of traffic—in the midst of telephone calls or a thousand and one other interruptions. Some men can concentrate on a mental problem while walking down a Chicago street and never hear the roar of the elevated or see the hurrying throngs. I have seen men write on a crowded street car perfectly oblivious to the people about them, not even hearing their own stations when called. But these men were already masters of concentration, and I am addressing my remarks to those who have not yet learned how to concentrate. Therefore, it is only a matter of common-sense to make conditions as favorable as possible. Give your mind a fair chance. Concentration is difficult enough, even under the best conditions. I would suggest that you seek a quiet place free from all distractions (and noise is a terrible distractor), a place free from all interruptions which may break your train of thought (and a telephone is a terrible interruptor), a place where you can be alone, free from all outside influences (and a friend who " must drops in " is a terrible outside influence), and a place of pleasing environment, beautiful or otherwise, where the atmosphere is right for you. I mean atmosphere in its fuller sense, although an abundance of sweet, fresh air is necessary. A well-poised mind can create its own atmosphere which inspires the individual, puts him at his best, is strongly conducive to good mental work, and has much to do with his success in concentrating. Not alone for the beginner, but I may safely say for the majority, is this true. In fact, some of our greatest creative thinkers absolutely insist on right conditions and the right kind of a place in which to produce their master-pieces. True, good books have been written in mail—great poems written in the trenches—masterly speeches conceived on an express train. But in every case there was a degree of concentration strong enough to rise triumphant above the environment.

Atmosphere--environment—these things differ with the individual—it's all in the mind. One man may do his best work seated in a luxurious chair in his beautiful and artistic study--another may reach his highest plane of creative thinking while sitting under a lone pine-tree on the crest of a hill. Choose your own place for concentration, but remember that solitude has always been, in all the history of mental achievement, a requisite for great work.

Solitude calls forth the mood of receptivity. Only then do we get the best. Great things are worked out in silence. Then come the flashes of inspiration—the new visions. Emerson tells us that " Solitude is to genius the stern friend—the cold, obscure shelter, where mould the wings which will bear it farther than suns or stars," and we have this thought from Carlyle: " Silence is the element in which great things fashion themselves together—that at length they may emerge full-formed and mamestic into the delight of life—which they are henceforth to rule."

The great poems written in lonely garrets—the masterpiece paintings conceived by the artist amid the fields—the divine harmonies first heard by the musician communing with the stars—the sublime oration which first stirred the soul of the orator as he tramped in the forest—all attest that the best comes to man when he is alone.

Witness Burns—the Scotch peasant among the daisies pouring out the lyric songs which to- day touch sympathetic hearts the " warld o'er."

Witness Emerson—bidding good-bye to the proud world and retiring to that Sylvan Home, " bosomed in yon green hills "—and there creating his incomparable essays.

Witness Demosthenes—on the seashore—building to the big music of the waves his match-less oration on the Crown.

Witness Byron—alone on the Alps—writing by the glare of the lightning flash his magnificent description of the Thunderstorm.

And today right in this practical present—thousands of our most successful business men have learned this secret—that by getting alone—they can gain new efficiency—and think out better plans for managing their daily affairs.

History will bear me out in the statement that to bear Solitude well is a mark of greatness. Look at Lincoln—back there in the country for the first thirty years of his life, nourishing his own soul and disciplining his own mind.

Hillis has well said, " What a college and a crowd could not do for thousands of young men —Solitude did for the rail-splitter's son. Alone he sailed the seas of thought with God for his only companion, till at last he stood forth, a mountain-minded man."

A DEFINITE SCHEDULE

The fourth aid to concentration, is a very practical one: make a daily schedule. In the first place, such a schedule saves an inconceivable amount of time. Harrington Emerson, in his noted book, Twelve Principles of Efficiency, lays great stress upon the necessity and value of a written daily schedule. But what has this to do with concentration as applied to memory, you may ask? Simply this—your daily schedule helps to focus the mind, holds it steadily to one thing at a time and in the right order. Following a logical sequence tends to eliminate con-fusion.

It has been demonstrated in efficiency tests over and over again that time and energy are lost not so much on the operation itself as in passing from one operation to another. So in our mental operations, failure to move smoothly from one thing to another results in confusion. And when confusion comes, concentration goes. A definite daily schedule is a wonderful aid in keeping the mind on the right track. It often proves to be the salvation of those who have been unable to concentrate. Try it.

compiling

2009-08-01T22:33:00.000+01:00

1.character mapping
2.line splicing
3.tokenizing
4.preprocessing
5.character set mapping
6.string concatenating
7.translating
8.linking

Famous Aerobatics teams

2009-07-27T15:17:00.001+01:00

Asas de Portugal (Portuguese Air Force)
August 1st (People's Liberation Army Air Force)
Black Eagle (Republic of Korea Air Force)
Black Knights (Republic of Singapore Air Force)
Blue Angels (United States Navy)
Blue Diamonds (Philippine Air Force)
Blue Eagles (Army Air Corps—United Kingdom)
Blue Impulse (Japan Air Self-Defense Force)
Cartouche doré (French Air Force)
Cruz del Sur ("Southern Cross"—Argentine Air Force)
Diables Rouges (Belgian Air Force)
Elang Biru (Indonesian Air Force)
Esquadrilha da Fumaça (Smoke Squadron - Brazilian Air Force)
Frecce Tricolori (Italian Air Force)
Halcones (Falcons-Chilean Air Force)
Hungarian Sky Hussars (Imitated Dogfight with MIG-21 bis - Hungarian Air Force)
Green Hawk (Bureau of Royal Rainmaking and Agricultural Aviation, Thailand)
Midnight Hawks (Finnish Air Force)
Orlik Aerobatic Team, White-Red Sparks (known also as Team Iskry), Scorpion (aerobatic team) (Polish Air Forces)
Patrouille de France (French Air Force)
Patrouille Suisse (Swiss Air Force)
Patrulla Aguila, Patrulla Aspa (Eagle Patrol; Blade Patrol—Spanish Air Force)
Red Arrows (Royal Air Force—United Kingdom)
Red Checkers (Royal New Zealand Air Force)
Red Pelicans, Rothmans, Silver Falcons (South African Air Force)
Rotores de Portugal (Portuguese Air Force—Helicopters)
Roulettes (Royal Australian Air Force)
Royal Jordanian Falcons (Royal Jordanian Air Force)
Russian Knights, Strizhi (Swifts), Rus (Russian Air Force)
Sagar Pawan (Indian Navy)
Sanmueang (Royal Thai Air Force)
Sarang (Indian Air Force)
Saudi Hawks, (Royal Saudi Air Force)
Sherdils (Pakistan Air Force)
Silver Falcons (South African Air Force)
Silver Swallows Irish Air Corps
Snowbirds (Canadian Forces)
Surya Kiran (Indian Air Force)
Team Jupiter (Indonesian Air Force)
Team 60 (Swedish Air Force)
Thunder Tiger (Republic of China)
Thunderbirds (United States Air Force)
Turkish Stars (Türk Yıldızları) (Turkish Air Force)
Ukrainian Falcons (Ukrainian Air Force)
Wings of Storm (Croatian Air Force)

what i should learn-how do i write to Dave

2009-06-23T15:50:00.001+01:00

Ori email:
Dear Dave,
Thank you for your information.And I think I could do some literature review
next week,and finish the aircraft dynamic and engine models.
I have only one question now. What kind of control law do we use for the
simulator?Is there any paper or book about it?Could you recommend any to me?If
you don't have time,I could ask Tony.
I really hope you will be in good health after your operation.
Improved one
Dear Dave:
Thank you for your information and advises. Please do not worry about the supervision. Right now, I am quite enjoying myself debugging the aircraft dynamic engine models, which I have just finished building. Hopefully, the debugging could be finished this week. If it is going smoothly, I plan to try some simulations of the control laws you mentioned to me.
If I encounter any problems, I will go and discuss with Tony, as suggested
Besides, I also plan to do some literature review, is there any paper or book you recommend reading?
Wish you a successful operation and a quick rescovery after that and looking forward to the restart of the supervision.

So that is whate to be called active attitude.

How long is a piece of string?

2009-06-18T16:18:00.001+01:00

Intrinsically a piece of string has length but that length is unknown hence the
the phrase 'how long is a piece of string' means that the quantitative answer is not known and there is an implicate understanding that the answer will be difficult to find given the information available.

is it true?I hope so.

2009-06-15T21:16:00.002+01:00

Yu,

Your problem seemed to me to be so important that I spent more than 13 hours performing an in-depth study of your case, so that I could help you more quickly.

I am aware of your most important wish: Work

As surprising as this may seem, I have every reason to believe that it will come true sooner than you may think. I will tell you when and how this will happen.

I am also aware of the problem that concerns you most at the moment: Money

You made an excellent decision asking me for help.

In fact, I see that in the coming weeks you should find a suitable solution for most of your problems. In just a moment I will reveal what I saw happening to you in detail.

But first I want to announce that I have selected you to be included in a book I plan to write. If all goes well, I will be able to send you A CHECK FOR £300, MADE OUT TO YOUR NAME, in accordance with my commitment.

AND THAT’S NOT THE ONLY GOOD NEWS. There are many more good things in store for you, which you may not be expecting.

That’s why it’s important for you to take note of the date written below in red:

July 15 2009!

Starting on that day, you are going to be at a DECISIVE TURNING POINT IN YOUR EXISTENCE.

I can tell you that YOU ARE GOING TO ENTER A LUCKY ASTRAL PERIOD VERY SOON which should definitely be THE MOST IMPORTANT OF YOUR ENTIRE LIFE.

More precisely, I see 3 WONDERFUL MONTHS THAT ARE GOING TO TRANSFORM YOUR DESTINY. Followed by 3 more very good months that will have a lasting effect on your future, Yu.

I ALSO HAVE SOME OTHER NEWS FOR YOU THAT IS A LITTLE LESS POSITIVE. But you shouldn’t worry more than necessary about it.

Because even though something may happen that is not very good for you, I can still be there to help you.

I will show you how you can avoid events that could turn out to be negative for you. And in any case, I will tell you what to do so that the LUCKY PERIOD that is in store for you works out in your favor.

Above all I want you to know that, as my way of thanking you for the confidence you have shown in me, I made a commitment in my soul and in my conscience to do everything I could to help you, until the moment that YOUR HAPPINESS IS TOTAL AND COMPLETE.

I have already done this for many people with problems as serious as yours, people who thought that nothing and no one could change their lives.

Today they are all overjoyed to realize just how much THEIR FINANCIAL AND PERSONAL SITUATIONS REALLY HAVE BECOME TOTALLY TRANSFORMED. And what I have done for others, I can also do for you.

Now I should tell you about some information that concerns you, and is of great importance for you today:

Your date of birth is: 16 September 1982.

That makes you a Virgo.

Your astral chart is strongly influenced by Mercury.

Based on these factors, I will now transmit my initial conclusions to you:

General Introduction

You are someone with a complex, often unsettling personality. You don’t always understand your contradictions, and you are not always appreciated by those around you, to say the least.
And yet it is this same ambiguity, these same contradictions, that make your personality really rich. Order and discipline, detail and precision, are the primordial traits that characterize your daily activities. At the same time you are capable of being extremely disorganized and undisciplined, and of letting things go when you feel like it!

Health

You need the air of the great outdoors, calm and contemplation!

No matter what health problems may arise in your life, first look for the cause in your nervous system.

Are you an irritable person? You don’t have to look further than that. But it’s no use stuffing yourself with all kinds of special medication to regain the calm and peace-of-mind you so sorely need.

Any competent doctor will advise you to first get more oxygen: there’s no doubt that you need a lot of air.

Try to overcome your natural tendency to be lazy, and at least twice a week practice some outdoor sport like jogging, bicycling, golf, tennis (not indoors), swimming when possible, etc.
GET AS MUCH OXYGEN AS YOU CAN!

Love – Emotions

Charm, modesty, tenderness and – yes – shyness !

You are also wary of others. You can be demanding and critical, and "falling in love" is not really your cup of tea.

Is the natural love you feel sometimes colored with romanticism? Maybe! But you are not often really passionate: your critical and analytical sense, your reasoning and your mistrust, often hold you back.
It is certain that a little less reason, a little more passion, and showing your feelings more often would help you in this area. Have the confidence to let yourself go from time to time. For example, why not let your 6th sense guide you more often. At least it’s hardly ever wrong. And because love is natural for you, try to give off yourself without fear. You will then be capable of experiencing exceptional love.

Social Life

Order, method, precision...

You may have already wondered why these qualities, these character traits, are always present in anything you undertake.

Well, I believe it’s simply because these aspects of your personality reflect your important need for security.

One cannot say that you have a taste for adventure! Security, morality and material possessions come before anything else.

Your sense of accuracy, of precise control and accounting makes you suitable for work as a civil servant. You could be very successful, although you may not aspire to such a career (it does have its limits).
But in this area too we can also see the ambiguity of your personality, which I already mentioned, come to the forefront: as opposed to a civil service position, you would also be suitable for a liberal profession where your intrinsic qualities would by highly appreciated.

Luck

Your golden number is 10, your lucky number par excellence. Use the number 10 as often as you can: for example, when you set up an important meeting, insist on the 10th day of the month, or 10 o’clock in the morning; when you use the train, get in the 10th car, etc.

To ensure your chances in love, your most favorable number is 27.
And 15 is your number for success in all areas: business, friendship, money, etc.

Some final advice

You may not be aware of it yet, but the Force inside you is the most important positive element you have to attain success under any circumstances: success in your future projects, success with love, money, business, etc.

It is clear that you have a huge potential, which you received at birth (a potential for luck and unexpected money) which is in total opposition to the difficult life you are leading, and the bad luck which is unjustly affecting you at the moment.

You should never have had to deal with the difficulties and serious problems (especially those concerning money) that seem to be ceaselessly plaguing you.

Here’s why:

Mercury, along with the other planets that control your Destiny, have endowed you with tremendous Lucky Power.

This should have turned out to be very positive for you in terms of money, and the realization of what you really hold dear in life. But that has not been the case.

Of course you’ve had a few happy moments at certain times in your life. But you know that you have generally been lacking in luck in many important areas of your life. Isn’t that so?

You have had some periods of luck and happiness on your journey. But SOMEONE OR SOMETHING HAS BEEN PREVENTING YOU FROM TAKING ADVANTAGE OF THAT LUCK. It has passed you by each and every time.

There have also been LARGE AMOUNTS OF MONEY THAT WERE WITHIN YOUR GRASP on many occasions, but once again an invisible hand seems to have prevented you from enjoying your potential profit.

As things stand now you take each day as it comes, without really knowing what will happen to you tomorrow.

Sometimes, because of a lack of self-confidence, you make decisions that eventually have serious consequences. You may be thinking that this is all your fault.

Well, that is not the case!

I HAVE A STRANGE FEELING, as if some HARMFUL INFLUENCE was forcing you to make the wrong decisions, those that attract bad luck instead of good luck (especially as far as money is concerned).

Don’t say to yourself: "I’ve never been lucky... I just have too much bad luck... I’ll never get out of my present situation!”

Believe me, based on my experience I can confidently say that is not the case at all. On the contrary!

You have a right to happiness. And you should know that there are no unlucky stars in your astral chart.

All you have to do is follow THE PATH TO LUCK AND HAPPINESS as indicated by your master planets, which will soon become active and influence your destiny.

In your case your dominant planet is: Mercury. Along with your other important master planets, it has already presented you with numerous lucky occasions (notably for money), although you were not able to take advantage of them for an obvious reason which you know already.

This was not your fault. NO ONE WAS THERE TO HELP YOU understand the importance of these occasions, and tell you what to do.

It’s too bad we didn’t know each other sooner. I could have intervened and told you exactly what to do, and when.

I could have warned you about problems you might have avoided and, most importantly, I could have helped you TAKE FULL ADVANTAGE OF THE OCCASIONS FOR LUCK AND MONEY that should have been yours.

If I had done so your life would have been wonderful. You would not have experienced all the major problems you’ve been having until now.

But we mustn’t dwell on the past. The important thing now for you to be happy is to know that IT ISN’T TOO LATE TO DO SOMETHING ABOUT IT.

Starting today I pledge to do everything in my power (including putting in my time) to help you make your most heartfelt dreams come true.

I am convinced that YOUR LIFE CAN CHANGE OVER THE COMING WEEKS. I feel it in the deepest part of my being. You can trust me – I am very, very rarely wrong.

BUT YOU MUST BE CAREFUL!

You can’t keep moving forward in the dark, without a helping hand to point out all the opportunities for Luck and Money that will be presented to you in the near future.

You should know that at your age of 26 years old, you still have the perspective of many years of happiness ahead of you. You can be absolutely certain of that.

But you have to know exactly when it will be important to SEIZE THE NUMEROUS OCCASIONS FOR LUCK AND HAPPINESS THAT COME YOUR WAY.

That must be done at the moment they are presented to you. I’ll tell you all about it. I feel some very surprising things about you.

YOU HAVE VERY STRONG INTUITION, YOU’RE SENSITIVE, AND YOU ARE VERY GENEROUS, BUT sometimes other people take advantage of you, without knowing that THINGS aren’t going so well.

I see you as an anxious person, a little vulnerable, who doesn’t always know how to defend yourself against life’s injustices.

And while we’re on the subject, I SHOULD TELL YOU A SECRET THAT CONCERNS YOU PERSONALLY:

Do you know that you have a force inside you - Unlimited Inner Power – that you totally ignore and make no use of at all? I saw it clearly on a number of occasions.

And do you know why you ignore this force and make no use of it? Well, you may have already noticed how a lot of people think they’re better than others.

For you the exact opposite is true. You tend to see your weak points instead of your strong ones.

I’m pretty sure you’ve already asked yourself: “Why do some people have so much happiness and not me”?

You have to stop this kind of negative thinking. You have to accept that YOU HAVE THE RIGHT, AS MUCH RIGHT AS ANYONE ELSE, TO THE LUCK AND MONEY you’ve been deprived of until now. And for that to happen all you need to do is agree to accept some special help from me.

HERE’S WHAT I CAN DO FOR YOU:

Firstly, it’s important for you to know that to help you it is not absolutely necessary for us to meet personally.

I have already helped hundreds of people who, like you, had serious problems with luck or money, and each and every time their most urgent problem disappeared, without my having to meet them face to face.

Because of what I felt about you (I always trust my first impressions) I know that YOU ARE VERY SOON GOING TO ENTER ONE OF THE MOST WONDERFUL PERIODS OF YOUR LIFE.

THIS EXCEPTIONAL PERIOD SHOULD BEGIN ON July 15 2009. I don’t want to be more specific, because it could happen a few days before or a few days after July 15 2009.

It should last until October 13 2009, which means 3 full months of great good luck with money, followed by 3 very positive months in your personal life.

During that entire time I will be there, to point out all the opportunities for Luck and Money that you should take advantage of.

I will show you WHAT TO DO TO AVOID PROBLEMS that could arise for you (and how to turn them in your favor).

You must not ignore THIS PERIOD WHICH COULD TRANSFORM YOUR ENTIRE DESTINY. All you have to do to profit 100% from the opportunities that arise at the start of this lucky period is act when I tell you to.

If you follow my advice, your situation should improve very rapidly after that.

As for the problem that you are most concerned with, I see A HAPPY SOLUTION IN YOUR IMMEDIATE FUTURE (much sooner than you may think).

THE MAIN REASON:

In the coming weeks Mercury, the master planet which has the most influence on you and on your future will, along with other very beneficial planets, exert an influence on your immediate destiny and make it very favorable for you. This convergence of luck will not happen again for a long time.

You have to understand that AN AMAZING EVOLUTION WILL HAPPEN FOR YOU AS FAR AS LUCK AND MONEY ARE CONCERNED.

I am deeply convinced that during this period of your life you will finally gain the right to enjoy your share of happiness and luck in all important areas: financial as well as emotional and familial.

You should know that there will be certain specific times when YOUR CHANCES FOR SUCCESS WILL BE MULTIPLIED 10, 20, AND EVEN 30 TIMES, especially in games that involve money.

At the right time I will reveal these favorable periods, when your chances of winning an upcoming jackpot are multiplied 30 times!

I will give you all the specific dates when you should use this precious information to gain maximum financial profit.

BUT YOU HAVE TO BE CAREFUL. There is an obstacle you have to avoid. You have to be very discreet about this.

A person who is envious of you may try to direct HARMFUL UNLUCKY VIBRATIONS at you (this could happen sooner than you think) to prevent you from getting a large amount of money.

If that turns out to be the case, I will tell you exactly WHAT TO DO TO PROTECT YOURSELF AGAINST THE NEGATIVE VIBRATIONS coming from that person.

I’ll also tell you what decisions you have to make (during the lucky periods that are coming your way) to ensure that your destiny advances firmly towards the realization of your imminent happiness.

I am this positive about your immediate future because I have the gift, proven many times over, of seeing things long before they happen.

I was challenged by those who didn’t believe in clairvoyance, and asked to take part in many para-psychological tests. The results of these tests were surprising, and indicated a very small margin of error of only 3%.

What does that mean? It means that I can see the future of someone accurately, 97% of the time. Few psychics can claim to do that.

Believe me, it’s absolutely essential for you to know what important events will happen for you in the coming months, and I’ll be happy to tell you about them.

Then you’ll be lucky enough to know for sure what good things you can expect in your immediate future.

Don’t think: “I don’t need to know. My future doesn’t look very bright right now, and I don’t know when or how things will ever work out.”

Obviously your future cannot be favorable if you don’t know what obstacles you are likely to encounter, even though it is possible to avoid them. Or when your chances for gaining money are best, and must absolutely be taken advantage of.

You now know that AN EXCEPTIONALLY LUCKY PERIOD SHOULD BEGIN FOR YOU AND TRANSFORM YOUR LIFE STARTING ON July 15 2009.

You absolutely must take advantage of the fantastic opportunities for luck and money that will come your way in the next 3 months. Especially since they will be followed by another very positive 3 months for your personal life.

These 6 months of intense change will give your existence a whole new meaning. Especially if you know exactly what to do, and when and how to do it!

Here’s what I am offering to do for you:

What you discover in this detailed reading has nothing in common with anything you may have been told up to now about you and your future.

You will receive a document that is more complete and more detailed than anything any other psychic may have done for you before.

I KNOW THAT YOU NEED £0 AS FAST AS POSSIBLE.

All I can say is that even though you may have financial problems right at this moment, your immediate future shows that money will probably no longer be a problem for you.

You will have as much as you need. In fact, AN INITIAL INPUT OF A LARGE AMOUNT OF MONEY starting on July 15 2009 should transform your entire life.

This sudden and unexpected arrival of money is inscribed in your astral chart.

You may not know about it yet, but it is being prepared for you right now, and should happen in the next few weeks.

YOUR FINANCES:

I will tell you in detail exactly how you can receive a considerable number of LARGE AND UNEXPECTED INPUTS OF MONEY.

Exactly when you will no longer have any money problems, and how much you can hope to receive in all.

When it’s time to stop thinking about saving and making some important payments that you may not have expected, and what these expenses will be.

How to manage your money with precision, so that you always have enough to last you the rest of your life.

As for luck, I will be able to reveal the hidden secrets of your destiny:

You may have noticed that, despite all your efforts until now, you have always been unlucky in most of the important areas in your life.

I CAN TELL YOU THAT YOUR PROBLEM OF BAD LUCK WILL SOON COME TO AN END.

The dominant position occupied by Mercury, your master planet, in relation to the other planets, clearly shows that you are going to profit from an excellent configuration that is very favorable for luck.

Starting on July 15 2009 you can expect the sudden and unexpected realization of your most important wish: Work.

I will tell you exactly on which days of the week your chances of winning will be at their maximum, and when to try your luck at which games so that your chances of winning big are multiplied 30 times.

I will also tell you which moments are less favorable for you (there aren’t many but there will be some) so that you can avoid playing and not run the risk of losing your money.

Stay Hungry. Stay Foolish[zt]

2009-06-13T16:03:00.001+01:00

'You've got to find what you love,' Jobs says

This is the text of the Commencement address by Steve Jobs, CEO of Apple Computer and of Pixar Animation Studios, delivered on June 12, 2005.

I am honored to be with you today at your commencement from one of the finest universities in the world. I never graduated from college. Truth be told, this is the closest I've ever gotten to a college graduation. Today I want to tell you three stories from my life. That's it. No big deal. Just three stories.

The first story is about connecting the dots.

I dropped out of Reed College after the first 6 months, but then stayed around as a drop-in for another 18 months or so before I really quit. So why did I drop out?

It started before I was born. My biological mother was a young, unwed college graduate student, and she decided to put me up for adoption. She felt very strongly that I should be adopted by college graduates, so everything was all set for me to be adopted at birth by a lawyer and his wife. Except that when I popped out they decided at the last minute that they really wanted a girl. So my parents, who were on a waiting list, got a call in the middle of the night asking: "We have an unexpected baby boy; do you want him?" They said: "Of course." My biological mother later found out that my mother had never graduated from college and that my father had never graduated from high school. She refused to sign the final adoption papers. She only relented a few months later when my parents promised that I would someday go to college.

And 17 years later I did go to college. But I naively chose a college that was almost as expensive as Stanford, and all of my working-class parents' savings were being spent on my college tuition. After six months, I couldn't see the value in it. I had no idea what I wanted to do with my life and no idea how college was going to help me figure it out. And here I was spending all of the money my parents had saved their entire life. So I decided to drop out and trust that it would all work out OK. It was pretty scary at the time, but looking back it was one of the best decisions I ever made. The minute I dropped out I could stop taking the required classes that didn't interest me, and begin dropping in on the ones that looked interesting.

It wasn't all romantic. I didn't have a dorm room, so I slept on the floor in friends' rooms, I returned coke bottles for the 5¢ deposits to buy food with, and I would walk the 7 miles across town every Sunday night to get one good meal a week at the Hare Krishna temple. I loved it. And much of what I stumbled into by following my curiosity and intuition turned out to be priceless later on. Let me give you one example:

Reed College at that time offered perhaps the best calligraphy instruction in the country. Throughout the campus every poster, every label on every drawer, was beautifully hand calligraphed. Because I had dropped out and didn't have to take the normal classes, I decided to take a calligraphy class to learn how to do this. I learned about serif and san serif typefaces, about varying the amount of space between different letter combinations, about what makes great typography great. It was beautiful, historical, artistically subtle in a way that science can't capture, and I found it fascinating.

None of this had even a hope of any practical application in my life. But ten years later, when we were designing the first Macintosh computer, it all came back to me. And we designed it all into the Mac. It was the first computer with beautiful typography. If I had never dropped in on that single course in college, the Mac would have never had multiple typefaces or proportionally spaced fonts. And since Windows just copied the Mac, its likely that no personal computer would have them. If I had never dropped out, I would have never dropped in on this calligraphy class, and personal computers might not have the wonderful typography that they do. Of course it was impossible to connect the dots looking forward when I was in college. But it was very, very clear looking backwards ten years later.

Again, you can't connect the dots looking forward; you can only connect them looking backwards. So you have to trust that the dots will somehow connect in your future. You have to trust in something — your gut, destiny, life, karma, whatever. This approach has never let me down, and it has made all the difference in my life.

My second story is about love and loss.

I was lucky — I found what I loved to do early in life. Woz and I started Apple in my parents garage when I was 20. We worked hard, and in 10 years Apple had grown from just the two of us in a garage into a $2 billion company with over 4000 employees. We had just released our finest creation — the Macintosh — a year earlier, and I had just turned 30. And then I got fired. How can you get fired from a company you started? Well, as Apple grew we hired someone who I thought was very talented to run the company with me, and for the first year or so things went well. But then our visions of the future began to diverge and eventually we had a falling out. When we did, our Board of Directors sided with him. So at 30 I was out. And very publicly out. What had been the focus of my entire adult life was gone, and it was devastating.

I really didn't know what to do for a few months. I felt that I had let the previous generation of entrepreneurs down - that I had dropped the baton as it was being passed to me. I met with David Packard and Bob Noyce and tried to apologize for screwing up so badly. I was a very public failure, and I even thought about running away from the valley. But something slowly began to dawn on me — I still loved what I did. The turn of events at Apple had not changed that one bit. I had been rejected, but I was still in love. And so I decided to start over.

I didn't see it then, but it turned out that getting fired from Apple was the best thing that could have ever happened to me. The heaviness of being successful was replaced by the lightness of being a beginner again, less sure about everything. It freed me to enter one of the most creative periods of my life.

During the next five years, I started a company named NeXT, another company named Pixar, and fell in love with an amazing woman who would become my wife. Pixar went on to create the worlds first computer animated feature film, Toy Story, and is now the most successful animation studio in the world. In a remarkable turn of events, Apple bought NeXT, I returned to Apple, and the technology we developed at NeXT is at the heart of Apple's current renaissance. And Laurene and I have a wonderful family together.

I'm pretty sure none of this would have happened if I hadn't been fired from Apple. It was awful tasting medicine, but I guess the patient needed it. Sometimes life hits you in the head with a brick. Don't lose faith. I'm convinced that the only thing that kept me going was that I loved what I did. You've got to find what you love. And that is as true for your work as it is for your lovers. Your work is going to fill a large part of your life, and the only way to be truly satisfied is to do what you believe is great work. And the only way to do great work is to love what you do. If you haven't found it yet, keep looking. Don't settle. As with all matters of the heart, you'll know when you find it. And, like any great relationship, it just gets better and better as the years roll on. So keep looking until you find it. Don't settle.

My third story is about death.

When I was 17, I read a quote that went something like: "If you live each day as if it was your last, someday you'll most certainly be right." It made an impression on me, and since then, for the past 33 years, I have looked in the mirror every morning and asked myself: "If today were the last day of my life, would I want to do what I am about to do today?" And whenever the answer has been "No" for too many days in a row, I know I need to change something.

Remembering that I'll be dead soon is the most important tool I've ever encountered to help me make the big choices in life. Because almost everything — all external expectations, all pride, all fear of embarrassment or failure - these things just fall away in the face of death, leaving only what is truly important. Remembering that you are going to die is the best way I know to avoid the trap of thinking you have something to lose. You are already naked. There is no reason not to follow your heart.

About a year ago I was diagnosed with cancer. I had a scan at 7:30 in the morning, and it clearly showed a tumor on my pancreas. I didn't even know what a pancreas was. The doctors told me this was almost certainly a type of cancer that is incurable, and that I should expect to live no longer than three to six months. My doctor advised me to go home and get my affairs in order, which is doctor's code for prepare to die. It means to try to tell your kids everything you thought you'd have the next 10 years to tell them in just a few months. It means to make sure everything is buttoned up so that it will be as easy as possible for your family. It means to say your goodbyes.

I lived with that diagnosis all day. Later that evening I had a biopsy, where they stuck an endoscope down my throat, through my stomach and into my intestines, put a needle into my pancreas and got a few cells from the tumor. I was sedated, but my wife, who was there, told me that when they viewed the cells under a microscope the doctors started crying because it turned out to be a very rare form of pancreatic cancer that is curable with surgery. I had the surgery and I'm fine now.

This was the closest I've been to facing death, and I hope its the closest I get for a few more decades. Having lived through it, I can now say this to you with a bit more certainty than when death was a useful but purely intellectual concept:

No one wants to die. Even people who want to go to heaven don't want to die to get there. And yet death is the destination we all share. No one has ever escaped it. And that is as it should be, because Death is very likely the single best invention of Life. It is Life's change agent. It clears out the old to make way for the new. Right now the new is you, but someday not too long from now, you will gradually become the old and be cleared away. Sorry to be so dramatic, but it is quite true.

Your time is limited, so don't waste it living someone else's life. Don't be trapped by dogma — which is living with the results of other people's thinking. Don't let the noise of others' opinions drown out your own inner voice. And most important, have the courage to follow your heart and intuition. They somehow already know what you truly want to become. Everything else is secondary.

When I was young, there was an amazing publication called The Whole Earth Catalog, which was one of the bibles of my generation. It was created by a fellow named Stewart Brand not far from here in Menlo Park, and he brought it to life with his poetic touch. This was in the late 1960's, before personal computers and desktop publishing, so it was all made with typewriters, scissors, and polaroid cameras. It was sort of like Google in paperback form, 35 years before Google came along: it was idealistic, and overflowing with neat tools and great notions.

Stewart and his team put out several issues of The Whole Earth Catalog, and then when it had run its course, they put out a final issue. It was the mid-1970s, and I was your age. On the back cover of their final issue was a photograph of an early morning country road, the kind you might find yourself hitchhiking on if you were so adventurous. Beneath it were the words: "Stay Hungry. Stay Foolish." It was their farewell message as they signed off. Stay Hungry. Stay Foolish. And I have always wished that for myself. And now, as you graduate to begin anew, I wish that for you.

Stay Hungry. Stay Foolish.

Thank you all very much.

track by http://news.stanford.edu/news/2005/june15/jobs-061505.html

goodnight dear void

2009-05-24T22:53:00.001+01:00

when i am typing in my room alone,these words just pop out.

recently, i started to think about my life in Britain,beijing and shenyang.what's my First Dream?

be a scientist,a writer,a shopgirl,a house wife,or an OL?i can't see the end,and don't know whether i am on the half way of one of them.

"Sometimes I wonder about my life.

I lead a small life.

Well,
valuable, but small. And sometimes I wonder, do I do it because I like
it, or because I haven't been brave? So much of what I see reminds me
of something I read in a book, when shouldn't it be the other way
around?

I don’t really want an answer. I just want to send this cosmic question out into the void.

So goodnight, dear void."

-You've Got Mail.