 |
当前位置：首页 >> 个人服务 >> 预览个人简历信息 提醒：任何一种简历保密设置，都不会影响您在线投递简历。 |
|
| 个人信息 |
| 姓 名： |
曾译员 [编号]:1447 |
性 别： |
女 |
|
| 擅长专业： |
英语 |
出生年月： |
1985/9/1 |
|
| 民 族： |
汉族 |
所在地区： |
上海 上海 |
|
| 文化程度： |
硕士 |
所学专业： |
英语 |
|
| 毕业时间： |
40339 |
毕业学校： |
上外 |
|
| 第一外语： |
英语 |
等级水平： |
专八 |
|
|
| 口译等级： |
高级 |
工作经历： |
2 年 |
|
|
| 翻译库信息 |
| 可翻译语种： |
英语 |
|
|
| 目前所在地： |
上海 上海 |
| 可提供服务类型： |
笔译、口译、家教 |
| 每周可提供服务时间： |
周末
工作日可任意排出一两天 |
| 证书信息 |
| 证书名称： |
专业八级证书 |
|
| 获证时间： |
2009/6/1 |
|
| 获得分数： |
78 |
|
|
| 工作经历 |
| 工作时期： |
2009/6/1--2009/9/1 |
|
| 公司名称： |
IBM |
|
| 公司性质： |
外商独资 |
| 所属行业： |
计算机/互联网/IT |
| 所在部门： |
用户体验部 |
|
| 职位： |
实习生 |
| 自我评价： |
认真，踏实 |
|
|
| 笔译案例信息 |
| 案例标题： |
Twitter |
|
| 原文： |
Twitter Postings: Iterative Design
Summary:
We made a timeline message more punchy, credible, and viral through 5 rounds of redesign.
A few days ago, I posted the announcement of our next usability conferences to Nielsen Norman Group's timeline on Twitter (@NNgroup).
I don't have all the guidelines for stream-based postings yet, because we're still conducting usability studies (particularly of B2B users, like my audience). But, based on the user sessions I've observed already, I put this posting through 5 rounds of iterative design.
1st Design
Announcing LAS VEGAS and BERLIN as the venues for our biggest usability conference of the year http://bit.ly/UsabilityWeek
Good: City names are highlighted, drawing the eye.
Bad: Starts with the non-information-carrying word "announcing." Of course it's an announcement — otherwise I wouldn't be posting it...
Remember that users tend to read only the first few characters as they scan down a list. Make them count.
2nd Design
LAS VEGAS and BERLIN are the venues for our biggest usability conference of the year http://bit.ly/UsabilityWeek
Good: Frontloading attractive keywords makes this version more scannable.
Bad: We lost the sense of news that "announcing" implied in the previous version.
Because many companies molest their poor followers with repeat postings about the same event, users have become somewhat hardened against event promotions.
3rd Design
LAS VEGAS (October) and BERLIN (November) are the venues for our biggest usability conference of the year http://bit.ly/UsabilityWeek
Good: Adding the months highlights that the conferences are coming up soon, regaining us some of that sense of news. Also, specificity is always a plus: it makes users feel like they're getting concrete and useful info, instead of the blather that characterizes so many B2B websites.
Bad: This draft Tweet is 133 characters, leaving only 7 characters for users who want to retweet. This isn't enough to add the customary 11-character attribution (RT @NNgroup), which is a must if we're going to benefit from the viral effect of our followers' followers being made aware of our feed.
(Keeping tweets below 130 characters won't be a long-term guideline because Twitter is redesigning to remove the source attributions from the main message content for repostings. Until this redesign goes live, however, it's best to leave slack in your original postings if you expect followers to share them.)
4th Design
LAS VEGAS (October) and BERLIN (November): venues for our biggest usability conference of the year http://bit.ly/UsabilityWeek
Good: Saved 6 characters by replacing "are the" with a colon. Full sentences aren't necessary for such short content, which users are scanning anyway. We're not trying to be the next Hemingway in a tweet.
Also: Fragments fine here. MS Word's squiggles frowning at you? Ignore them.
(Alternatively, I could have used a shorter URL shortcut, but there are benefits to giving people an idea of where the link will lead.)
5th Design
LAS VEGAS (October) and BERLIN (November): venues for our biggest usability conference ever http://bit.ly/UsabilityWeek
Good: Changed the awkward "biggest of the year" to the punchier "biggest ever." In addition to being shorter, "biggest ever" provides two additional benefits:
It's a more compelling argument for why readers should care and click through to see the full program
Growing during a bad recession is evidence of our strength and promises a positive experience, which is appealing to audiences who are tired of doom and gloom
This year, I'm producing 33 full-day seminars in Vegas compared with 31 in 2008, so I could have tried to squeeze in a reference to "6.5% growth since last year." But even though exact numbers have higher credibility than broader assertions, a tweet should be highly focused and not try to make multiple points.
Expanding by 6.5% during a recession is what evolutionary scientists call a "costly signal." That is, it's a way of communicating both the healthy status of usability in general and the high interest in our conference, which can't be faked: it costs real money to book more lecture rooms and fly in more speakers. Only a healthy peacock can grow a big tail.
Costly signals are more credible than unsupported boasts — whether you want to attract peahens or Web users. I was particularly interested in communicating a strong position last week, because we're currently recruiting new usability staff. The best people will consider leaving their current jobs only if they're confident of the new company's prospects.
When to Tweet
My last design decision was when to post the message to the Twitter timeline. My preferred tweeting time is 9:01 a.m. because it encompasses working hours from California to the U.K. and thus reaches a majority of our customers. (It's best to post a minute after the hour so you'll be listed on top of anybody who naively sets their software to release postings at exactly 9:00.)
In this case, however, German readers and others in continental Europe were particularly important, because we're going to Berlin for the first time. Thus, I pulled the posting time forward to 7:51 a.m. Pacific time, which is 4:51 p.m. in Germany and will still reach Californians who check Twitter during breakfast.
One of the big downsides of stream-based communication compared to email newsletters is the highly ephemeral nature of the postings: Once they scroll off the first screen, they're essentially 6 feet under.
A look at clickthrough statistics for links posted to Twitter vs. those circulated in email newsletters shows a drastically steeper decay function: lots of clicks the first few minutes, and then almost none. In contrast, email continues to generate clicks for days as people work their way through their inboxes.
Clickthrough decay: Twitter time passes 10 times faster than email time.
This makes it hard to reach an international customer base on Twitter, and makes it important to tweak the posting time relative to each topic's main target. (It's also one of the many reasons I continue to believe that email is a more powerful medium.)
Text is a UI
It's a common mistake to think that only full-fledged graphical user interfaces count as interaction design and deserve usability attention. As our earlier research has shown, URLs and email both contribute strongly to the Internet user experience and thus require close attention to usability to enhance the profitability of a company's Internet efforts.
In fact, the shorter it is, the more important it is to design text for usability.
Learn More
2-day course on Writing for the Web at the Usability Week 2009 conference in Las Vegas and Berlin.
The conference also has a full-day seminar on Integrating Social Features on Mainstream Websites: User-Generated Content, Social Media, Collaboration, and More.
> Other Alertbox columns (complete list)
> Sign up for newsletter that will notify you of new Alertboxes
Copyright © 2009 by Jakob Nielsen. ISSN 1548-5552 |
|
| 译文： |
总结:通过五轮重新设计，我们可以让时间轴上的信息更吸引人,更可信,传播得更广。
几天前，我通过Twitter在Nielsen Norman群的时间轴上发布了下次可用性会议的通知。
我们还在进行可用性研究（尤其是针对企业到企业的电子商务模式的用户，比如我的听众），尚未整理出串流发贴的指导。但是，根基于我在用户研讨会上的观察研究，在五轮交互设计后，我发布了这个帖子。
第一轮设计
宣布拉斯维加斯和柏林为本年度最大可用性会议的举办城市。
优点：强调了城市名字，能吸引注意力。
缺点：以“宣布”这一不含任何信息的词开头。这当然是一个通知——否则我就不会发上去了……
记住：用户游览列表时，通常只会看前几个字，所以要让每一个字都有作用。
第二轮设计
拉斯维加斯和柏林为本年度最大可用性会议的举办城市。
优点：将突出的关键词提前可以让这个版本更便于浏览。
缺点：前一个版本中“宣布”一词所包含的新闻意味在这一版中丢失了。
很多公司经常重复发布关于同一事件的帖子，这骚扰了他们的跟随者，所以用户已经对这些事件的宣传变得有些冷淡了。
第三轮设计
拉斯维加斯（十月）和柏林（十一月）为本年度最大可用性会议的举办城市。
优点：增加的日期强调会议即将举行，这给了我们新闻的感觉。同样，明确化总是好的:这让用户感觉到他们的收到的信息是具体有用的，而不是经常出现在很多企业对企业的电子商务网站上的废话。
缺点:这一个Tweet有133个字符，仅留给想重新tweet的用户7个字符。这不够用来增加有11个字符的属性(RT@NNgroup)。而如果我们想让我们追随者的追随者知道我们输入的内容，并从其广泛传播的影响中获益的话，这又是必需的。
(Tweet要求低于130个字符的限制不会是一个长期的准则，为了从新贴的主要信息内容中移除源属性，Twitter正在更新设计。但是，在这个设计投入使用之前，如果想要让跟随者共享它们，最好还是在原帖里留一些余地。)
第四轮设计
拉斯维加斯（十月）和柏林（十一月）：本年度最大可用性会议的举办城市。
优点：冒号代替了“为”，省略了六个字符。内容比较少的信息不一定要使用完整的句子，用户只会随便看一下。我们并不是想在Tweet里变成第二个海明威。
另外：片语的用法在这里是非常好的。Word中会出现波浪线？别管提示。
（或者，我应该使用一个更短的链接, 但是让别人知道这个链接会通向哪里是有好处的。）
第五轮设计
拉斯维加斯（十月）和柏林（十一月）：至今最大可用性会议的举办城市。
优点：将笨拙的“本年度最大”变成了更有力的“至今最大”。除了更简洁以外，“至今最大”至少还有两个好处：
能够更好地说服读者关心这个信息，并进一步阅读整个项目。
在经济萧条期还能保持增长说明了我们的能力，而且会是一个不错体验，这会吸引那些对这种灰暗生活产生厌烦情绪的群体。
相比2008年的31次，今年我们在拉斯维加斯举行了33个全天研讨会，所以我本可以在6.5%的增长率中再挤入一个会议的。但即使精确的数字比宽泛的妄断更可信， tweet也应该是有焦点的，而不该有多个关注点。
在经济萧条期还能以6.5%的速率增长，这被进化论科学家称为“昂贵的信号”。 这是表达可用性健康状态和我们会议的最高利益的方法。预订更多演讲教室，请更多演讲者会花更多的钱。只有一个健康的孔雀才能长出一个大的尾巴。
“昂贵的信号”比起那些没有得到支持的大话更加可信——无论你想吸引母孔雀还是网络用户。 上周我特别想表达一个很强烈的观点，因为目前我们正在招聘可用性员工。最优秀的人才只有对新公司的前景十分有信心才会离开现在的工作岗位。
什么时候Tweet
最后要下的设计决定就是什么时候在Twitter的时间轴上发布信息。我最喜欢的时间是上午九点零一分。因为这个时候从加利福利亚到英国这片区域都是上班时间，所以大部分客户都可以收到消息。（最好是在这个小时过去了一分钟再发布，很多人都会天真地将软件设定在九点整发布信息，这样你就会列在天他们前面了。）
但是，在这种情况下德国和其他欧洲大陆的读者特别重要，因为我们是第一次去柏林。因此，我会把发布信息的时间调到太平洋时间上午七点五十一分，这个时间正好是柏林下午四点五十一分。这样，在早餐时查看Twitter 的人就能看到通知了。
比起电子邮件简报来说，串流通信最大的不足就在于帖子存在的瞬时性：一旦它们卷起第一页，它们就在六英尺以下了。
看一看发布在Twitter上的和那些通过邮件简报传播开去的链接点击数据，就能看到一个非常陡峭的衰减函数:点击都集中在前几分钟，后面的时间几乎就没有了。相对的，随着人们打开邮箱，邮件还能在未来的好些天内继续获得点击。
点击衰减:Twitter时间比邮件时间快十倍。
这使得通过Twitter联系国际客户变得有些难度，而且调整与每个话题主要目标有关的发贴时间也很困难。（这就是我一直觉得邮件是一个更好媒介的众多原因之一。）
文本是界面
认为仅仅只有成熟的图片用户界面才能算得上是交互设计，才应得到可用性关注，这个想法是错的。正如之前的研究所示，网址和电子邮箱都能够为因特网用户体验做出很大的贡献，因此他们需要对可用性进行密切关注，从而增强公司在互联网上作出的努力应该实现的盈利。
实施上，内容越短，为可用性设计文本就越重要。
想知道更多内容，请看：
在拉斯维加斯和柏林举行的“可用性周2009年会议”上为一个为期两天的网页写稿课程。
会议还有一个全天研讨会，主题是：在主流网站上综合社会特征：用户生成内容，社会媒体，合作以及更多。
|
|
|
| 案例标题： |
IBM 用户体验 |
|
| 原文： |
Stop Password Masking
Summary:
Usability suffers when users type in passwords and the only feedback they get is a row of bullets. Typically, masking passwords doesn't even increase security, but it does cost you business due to login failures.
It's time to show most passwords in clear text as users type them. Providing feedback and visualizing the system's status have always been among the most basic usability principles. Showing undifferentiated bullets while users enter complex codes definitely fails to comply.
Most websites (and many other applications) mask passwords as users type them, and thereby theoretically prevent miscreants from looking over users' shoulders. Of course, a truly skilled criminal can simply look at the keyboard and note which keys are being pressed. So, password masking doesn't even protect fully against snoopers.
More importantly, there's usually nobody looking over your shoulder when you log in to a website. It's just you, sitting all alone in your office, suffering reduced usability to protect against a non-issue.
The Costs of Masking
Password masking has proven to be a particularly nasty usability problem in our testing of mobile devices, where typing is difficult and typos are common. But the problem exists for desktop users as well.
When you make it hard for users to enter passwords you create two problems — one of which actually lowers security:
Users make more errors when they can't see what they're typing while filling in a form. They therefore feel less confident. This double degradation of the user experience means that people are more likely to give up and never log in to your site at all, leading to lost business. (Or, in the case of intranets, increased support calls.)
The more uncertain users feel about typing passwords, the more likely they are to (a) employ overly simple passwords and/or (b) copy-paste passwords from a file on their computer. Both behaviors lead to a true loss of security.
Yes, users are sometimes truly at risk of having bystanders spy on their passwords, such as when they're using an Internet cafe. It's therefore worth offering them a checkbox to have their passwords masked; for high-risk applications, such as bank accounts, you might even check this box by default. In cases where there's a tension between security and usability, sometimes security should win.
In most cases, however, users will appreciate getting clear-text feedback as they enter passwords. Your business will increase, and security will even improve a tiny bit as well.
Abandon Legacy Design
Password masking has become common for no reasons other than (a) it's easy to do, and (b) it was the default in the Web's early days. In this respect, it's similar to another usability problem — having Reset buttons on forms, which is also something that should die.
Generally, I recommend adhering to conventions. Do what users expect, and they can concentrate their brainpower on understanding your products and offers instead of struggling with the user interface.
But password masking and Reset buttons are not something users actively seek out. Losing these features won't cause confusion, nor will their replacements: the new features will simply be clear text (in the first case) and a blank area where the destroy-my-work button used to be (in the second).
This is very different from removing something users look for or introducing something they don't understand.
Let's clean up the Web's cobwebs and remove stuff that's there only because it's always been there.
|
|
| 译文： |
因此，从现在开始，当用户输入密码时，大部分的密码应该显示出来。最基本的可用性原则是提供反馈及系统状态的可视化。用户输入复杂的密码而显示的却是无差别的星号，很明显这不符合可用性原则。
大多数网站（以及许多应用软件）在用户输入密码时都会屏蔽，这在理论上防止了歹徒窥视屏幕上的密码。然而，一名熟练的罪犯只需留意键盘就能记住密码。所以，屏蔽并不能完全防止密码窥探。
更重要的是，通常不会有人躲在你身后偷看你登录网站。而你自己却为了防止一个不是问题的问题发生，坐在办公室里忍受着被降低了的可用性。
屏蔽的成本
在测试移动设备时，输入困难及打错字是常见的问题，密码屏蔽在这时就成了一个尤为讨厌的可用性问题了。但是，同样的问题也存在于台式机用户身上。
在增加密码输入的难度时，你造成了2个问题——其中之一就是降低了安全性：
1. 当用户填写表格而看不到自己输入的文字时，他们会犯更多的错误，因而变得更不自信。这种双重的用户体验削弱所蕴含的意思是，人们更趋向于放弃输入，而且再也不会登录你的网站，从而导致你丢失业务。（如果是企业内部网，就会有更多人打电话向技术支持部门寻求帮助。）
2. 输入密码时，用户感觉越不确定，就越有可能使用极度简单的密码或从电脑的一个文件夹中复制粘贴密码。这两种行为都导致了真正的安全性的降低。
当然，有时候用户确实是冒着密码被窥视的风险，比如当他们在网吧使用电脑的时候。此时就应向用户提供一个复选框屏蔽该用户的密码；而在诸如银行账户之类的高风险应用中，甚至可以将这个密码屏蔽复选框设为系统默认。当安全性与可用性出现矛盾时，有时我们更应考虑安全性。
而大多数情况下，当用户输入密码时，他们更希望得到可视化的反馈。这样，你的业务会增加，甚至安全性也会有小小的改善。
丢弃老化的设计
密码屏蔽如此普及只是因为（1）这样做很容易，（2）早期网络上密码屏蔽是系统默认的。在这方面，它与另一个可用性问题相似，即在表格上的“重置”按钮，这也同样是应该消除的。
一般来说，我推崇传统。按照用户所希望的那样做，从而使他们能够集中精力理解你的产品和提议而不是在理解用户界面上犯难。
但是密码屏蔽和重置按钮并不是用户积极寻找的东西。没有这些特性并不会导致混乱，它们的代替物也不会造成混乱：新的特性只不过是可视化显示（在第一种情况下）和原来的重置按钮区域变成了一个空白区域（在第二种情况下）。
这与把用户寻找的东西移除或向他们介绍他们不理解的东西恰恰是不同的。
让我们一起清理盘根错节的网络，把那些一直存放在那里却没有用处的东西移除吧！ |
|
|
| 案例标题： |
华晖电子商务-旅游 |
|
| 原文： |
'摩洛哥艾特- 哈迪柏柏尔部族具有特色的新娘节，也叫穆塞姆节，在每年九月份举行，持续三天。
节日期间，待嫁少女身着白衣，外披绣有部族标志的花格羊毛披衣，在亲人的陪伴下，一排排地坐在集市的祠堂前面，等待意中人的到来。求婚的小伙子们则头缠整洁”的白毛巾，在知己朋友的陪同下，穿梭于待嫁姑娘群中，当找到了意中人时，便伸出右手求爱。姑娘如果拒不握手，即表示拒绝，如果同意，则说“你掳走了我的肝”（柏柏尔人认为健康的肝脏能给家庭带来幸福和美满），然后即商定婚期。年复一年，这个新娘节成全了许许多多的美满姻缘。
A
匈牙利最大的嘉年华会，狂欢者戴着柳木刻成的面具，面具上漆着鲜明的色彩，手持响板和摇铃在匈牙利南部莫哈其镇的大街上一路游行到广场，用声响赶走冬天。整个城镇用民族表演、民族艺术市场和民族舞蹈庆祝这个节日，并燃烧象征冬天的棺木以庆祝春天到来，然后跳舞狂欢直到黎明。
'尼日尔河下游的奥尼查是贝宁和伊博文化的汇合点。每年九月，最高头领奥比要在这里举行奥发拉节。一清早，人们被鼓声叫醒，酋长们列队到达，然后随音乐跳舞。中午，人们涌向奥比的宫殿去看奥比。奥比先后出现三次，他右手拿剑，左手拿马尾做成的护身符。据说，如果护身符碰着谁，谁就会得麻疯病。女人们唱起赞颂奥比的歌。奥发拉节结束后，新木薯节继之。
|
|
| 译文： |
ite- Hadibaibaier tribe of Morocco’s characteristic festival- Bride Festival, also known as Muse Mu Festival, is held in September and continues for three days.
During the holiday, marriage girls dressed in white all wear woolen gingham cloaks embroidered with tribal marks. They sit in rows in front of the ancestral hall on the market in the company of loved ones, waiting for the matches to come. The lads, who wrap their heads with white towels, then go to and fro through the rows of girls and hold out their right hands to propose when they find the girls they want to marry. If the girl refused to shake hands, that signifies the courtship is rejected. If she agrees, she will say "You kidnapped my liver" (Berber people think that a healthy liver can bring happiness to the family) and then the wedding day will be fixed. Year after year, this Bride Festival has helped achieved many happy marriage.
In the biggest carnival of Hungary, all the merrymakers ,wearing colored masks made from willows and having castanets and bells in their hands, march along a street throughout the whole night in the town of Moharri in the south part of Hungary, chasing the winter away with noises. The celebration goes on in the form of ethnic performance, ethnic arts displays and nationality dances. Furthermore, coffins, symbol of winter, are burned to celebrate the arrival of spring and people dance until dawn.
The lower reaches of Niger are the meeting place of Benin and Eta Cultures. Every September, Aofala Festival was held here by the highest leader. People are waked by the sound of drum at early morning and chieftains arrived in teams. After that, they start t o dance to the music. At noon, people flocked to the Aobi Palace to watch Obeah. Obeah appeared for three times, with a sword in the right hand and horsetail in the left hand as an amulet. It’s said that anyone who touches the amulet will bring himself leprosy. Women sing songs to celebrate Obeah. When Aofala Festival comes to an end, the Fresh Cassava Festival begins. |
|
|
|
|
