新闻，没授权。
本翻译作品采用知识共享署名-非商业性使用-相同方式共享 3.0 未本地化版本许可协议进行许可。
转载请注明作者和本帖地址。
ST. LOUIS, MO (KTVI) – A plane with landing gear problems was able to land safely at Lambert Airport Monday afternoon. CNN confirms the plane is from Wooster, OH.
CNN确认，周一下午一架飞机遭遇起落架故障，于兰伯特机场成功迫降。
The airport confirms eight people were on board and officials at the airport say they were prepared for a crash-landing scenario. Four ambulances were requested along with Arch Helicopter and other emergency equipment.
机场方面确认，机上当时有8人，机场方面做好了迫降准备，准备了4辆救护车，直升机和其他救援物资。
The Learjet planned to make an emergency landing at Parks Airport in Cahokia, Illinois but was diverted to Lambert.
该飞机本打算在伊利诺伊州卡霍基亚的Parks Airport 迫降，但最终选择兰伯特机场。
Just after noon Monday, the plane reported a problem with its front landing gear.
The plane flew by the tower for a visual inspection and determined the front landing gear was copped to the side. Officials in the tower said the plane will have to land without its gear.
周一下午，该飞机报告前起落架故障。通场目视检查后，地面报告前起落架偏向一边。塔台通知机组，可能要在没有起落架的状态下着陆。
The plane circled the airport to burn off fuel before landing safely at Lambert.
It appears Learjet passengers de-planed normally. All passengers are off the plane. Baggage from the plane was carried over to a shuttle bus.
迫降之前，飞机绕场飞行以消耗燃油。机上乘客全数正常离机。机上行李被卸到运输车辆中。
The Learjet was towed from the runway.
飞机被拖车拖离跑道。
原文：
Learjet Makes Emergency Landing At Lambert Airport @ fox2now
新闻，没授权。
本翻译作品采用知识共享署名-非商业性使用-相同方式共享 3.0 未本地化版本许可协议进行许可。
转载请注明作者和本帖地址。
WANT to own a piece of Manitoba history, albeit a very large piece of history?
想弄块曼省的“巨大历史残片”么？
If so, you're in luck: The infamous Air Canada Boeing 767 that made history as the Gimli Glider is up for auction in April.
机会来了：加航著名的“基米尼滑翔机”将在4月拍卖。
But you'll need to have a bit of money in your bank account.
但是这东西可不便宜。
Terry Lobzun, of Collector Car Productions, the company holding the auction via avideo presentation at the Toronto Classic Car Auction on April 14, said the aircraft's owners are expecting to get from $2.75 million to $3 million for it.
Collector Car Productions 的Terry Lobzun 称现拥有者的目标价格是275~300万加币。
（super注释：1800万RMB，不知是不是还得交HST？）
"It can be flyable and it can be delivered," Lobzun said on Thursday from the company's offices in Blenheim, Ont.
周四，Lobzun 在位于安省Blenheim 的办公室称该飞机仍可飞行，可以交付。
"To get it back into service, they'd have to jump through some hoops and it probably wouldn't be economically feasible, but it can be flyable to deliver it to be put on display. It would be nice to see it at the Western Canada Aviation Museum or Gimli.
“要让这架飞机重新服役，还需要跨过几道门槛，可能经济上并不划算，但是它还是可以飞到展览的地方的。如果这架飞机能在西加拿大飞行博物馆或基米尼 展出，就再好不过了。
（super注释：西加拿大飞行博物馆 位于温尼伯,同基米尼一样位于曼省 ）
"But if it went to Gimli, you'd just have to let the motorsport people know it's coming this time," he said laughing.
“但是，如果要在基米尼展出，你得提前打个招呼了。”
The plane is currently housed at a facility in California.
目前该飞机位于加州。
The aircraft gained fame when, because of a fuel conversion error between metric and imperial units, not enough fuel was taken on before it was bound for Edmontonon July 23, 1983.
该飞机因公制和英制差异导致的油料计算错误，于抵达埃德蒙顿前耗尽油料。
The plane's engines ran out of fuel at 41,000 feet and the powerless plane was glided to the former air force base in Gimli, forcing spectators at a drag strip to get out of the way. Nobody was injured.
飞机在41000英尺耗尽燃油，于位于基米尼的废弃空军基地迫降.无人受伤。
The aircraft flew regularly until it was retired from service in 2008.
飞机在此之后仍然服役，直到2008年。
If the plane returns to Manitoba, it probably won't be parked at the aviation museum.
如果飞机回到曼省，很可能不会停放在飞行博物馆。
Shirley Render, the museum's executive director, said while the plane landed in Gimli with empty fuel tanks almost 30 years ago, it is still too new for their collection.
Shirley Render ，博物馆的执行董事，表示虽然迫降时间发生在30年之前，作为展品来讲，这架飞机仍然太新。
"It's too much on what people fly today," Render said.
他说，“这架飞机是还在执飞的机型。”
"Our focus is on the old planes which people don't know too much about... it would be lovely but it wouldn't be on our dream list."
“我们的目标是人们不了解的老飞机。。。东西不错，但是我们不会要。”
（super吐槽：想要。。。）
原文：Original 'Gimli Glider' can be yours for a few million
来自Winnipeg Free Press，作者Kevin Rollason。
延伸阅读：
空中浩劫S05E02 “基米尼滑翔机”
@valencia7cn
http://tieba.baidu.com/p/1998696940
http://tieba.baidu.com/p/2037449456
（坟贴，勿顶）
那个767才200WRMB。。。
你是否遇到过如下几种状况：
- 博客更换域名，博客文章的内容也要跟着换
- 使用的图片地址更换了
- 写了很多文章，回过头来想切换作者
- 想删除某个可恶留言者的所有留言
- 想更改某个留言者所有留言的网站URL
- 想要禁用所有文章的pingback
- 想要禁用所有文章的评论功能
所有的这些，都涉及到一个关键词：批量修改。如果在WordPress后台，手动地去一个一个修改文章内容，相信会让你很抓狂，对一些拥有上千篇文章的博客来说，几乎是不可能完成任务。本文将教你如何使用SQL语句来操作你的数据库，实现数据的批量修改。
如果你没学过数据库的相关知识，肯定不知道SQL是什么，但是本文所涉及到的内容不需要你了解数据库的知识，也不需要你精通SQL语句的编写，你完全可以直接使用本文提到的SQL，下面我们将分条介绍各个SQL语句的功能，所有语句都使用默认的 wp_ 表前缀，如果你的不是，请自行更改。
开始之前，先介绍以下如何执行SQL语句，进行批量操作。现在一般的空间都是用phpmyadmin来管理数据库，这里将以phpmyadmin为例来介绍如何执行SQL语句：
进入你的phpmyadmin管理页面，然后进入你的博客对应的数据库
菜单栏有个 SQL 选项，点击进去
出现一个SQL语句的输入框，现在你就可以在里面输入SQL语句了
输入完毕，点击 执行 ，将执行你刚才输入的SQL语句
SQL语句执行完毕，你的文章也被批量修改了，现在去看看你的文章是否都被更改了
最后提个醒：以下介绍的SQL语句都在我的博客上做过测试，但是尽管如此，操作数据库之前都要先备份一下你的数据库；定期备份你的数据库是好习惯
1、批量修改文章内容：
如果你想替换之前写过的所有文章中的某些内容，如更换博客的名称，更换博客的网址，更换文章配图的链接等等，你可以使用以下SQL语句：
UPDATE wp_posts SET post_content = REPLACE( post_content, 以前的', '现在的' );
该语句的功能是将所有文章中的 以前的 字眼，全部替换成 现在的，你可以根据需要做一些更改。因为文章内容在数据库中是以HTML代码形式存储的，所以以上SQL语句同样可以替换HTML代码。
如果你只是想更改文章插图的链接，而不想影响其他的链接，可以使用以下SQL语句，所有src="oldurl.com被替换成了src="newurl.com
UPDATE wp_posts SET post_content = REPLACE (post_content, 'src="oldurl.com', 'src="newurl.com');
[important]super注释：我没成功。。。[/important]
如果你是以图片附件形式上传的话，需要更改图片附件的GUID
UPDATE wp_posts SET guid = REPLACE (guid, 'oldsiteurl.com', 'newsiteurl.com') WHERE post_type = 'attachment';
2、批量修改文章摘要：
文章摘要就是你在WordPress后台编辑文章时，"摘要"框中输入的内容，如果你想批量更改文章摘要，可以使用以下语句：
UPDATE wp_posts SET post_excerpt = REPLACE( post_excerpt, 'AA', 'BB' );
该语句的功能是将所有文章摘要中的 AA 字眼，全部替换成 BB。
3、批量修改文章的作者：
假设你的博客有两名注册用户，张三和李四，你想将张三的所有文章划归到李四名下，这时候该怎么办呢？你可以执行以下语句：
UPDATE wp_posts SET post_author = 李四用户id WHERE post_author = 张三用户id;
那如何获得 李四的用户id 和 张三的用户id 呢？你可以执行以下SQL语句：
SELECT ID, user_nicename, display_name FROM wp_users;
这时将列出你博客上所有的注册用户的ID，昵称和公开显示的名称，你现在就可以找到对应用户的ID了，如zhangsan的ID为2，lisi的ID为5
你的SQL就可以这样写了：
UPDATE wp_posts SET post_author = 5 WHERE post_author = 2;
4、批量修改文章评论者的网站URL：
假设，你的博客有个非常忠实的读者，给你的博客文章留下很多有用的评论，同时他的评论都填写了留言者的网站URL，但是有一天他的博客域名换了，并请求你更新他留言中的网站URL，那你怎么办？手动一个一个帮他改，这不太现实。你可以使用以下SQL语句：
UPDATE wp_comments SET comment_author_url = REPLACE( comment_author_url, 'oldurl.com', 'newurl.com' )
以上语句，将留言者所有旧的网站链接oldurl.com，更改为新的网址newurl.com
5、禁用所有文章的pingback功能：
开启pingback功能，可以在别人引用你的文章链接的情况下，给你发送通知，但是该功能似乎对我们的文章没多大帮助，那为何不把pingback给禁止了呢？在WordPress后台 – 设置 – 讨论，取消勾选"接收来自外部博客的引用通告(pingbacks 和 trackbacks)"，这样以后的文章都不开启pingback，但是该选项不会对之前的已发布的文章起作用，还是要用到SQL:
UPDATE wp_posts SET ping_status = 'closed';
6、删除所有文章的修订版：
在通常情况下，文章的修订版对大多数人来说没多大意义，而且修订版的数量会随着你修改文章的次数不断增长，这会增加数据库的查询速度，这并不是什么好事。互联网上有很多教你如何禁止修订版的文章，还有很多插件可以删除文章修订版，你可以自己搜索看看。这里教你如何使用SQL语句，删除所有已产生的文章修订版数据：
DELETE a,b,c FROM wp_posts a LEFT JOIN wp_term_relationships b ON (a.ID = b.object_id) LEFT JOIN wp_postmeta c ON (a.ID = c.post_id) WHERE a.post_type = 'revision';
7、删除某个评论者的所有评论：
如果你的博客想要封杀某人，并删除其在你博客的所有留言，可以使用以下SQL语句。
(1)根据留言者的博客URL进行删除，以下SQL语句将删除所有URL为 www.example.com 的评论
DELETE FROM wp_comments WHERE comment_author_url LIKE '%www.example.com%';
(2)根据留言者的昵称进行删除，以下语句将删除所有昵称为 example 的评论
DELETE FROM wp_comments WHERE comment_author = 'example';
(3)根据留言者的Email进行删除，以下语句将删除所有Email为 example@example.com 的评论
DELETE FROM wp_comments WHERE comment_author_email = 'example@example.com';
8、替换所有评论中的敏感词汇：
国内的互联网监控力度表现出了不断加强的趋势，如果你的博客评论中出现了大量的敏感词汇，很可能离被墙也不远了。最好的做法是，替换相关的敏感词汇，以保证你的博客安全，以下SQL语句将所有评论中的 fuck，替换成 **，替换内容根据你的需要来。
UPDATE wp_comments SET comment_content = REPLACE( comment_content, 'fuck', '**' );
9、关闭文章评论功能
有时候你的博客可能会因为某种原因，需要关闭文章的评论。在WordPress后台 – 设置 – 讨论，那里取消勾选"允许人们发表新文章的评论"，以后发表的文章默认是关闭评论的。但是之前已经发表的文章，若想关闭评论需要你一篇一篇地去修改评论设置，这是一件比较痛苦的事情。以下SQL语句可以帮助你轻松地批量关闭文章评论：
(1) 关闭所有旧文章的评论：
通常情况下，一篇旧文章就很少会有人发表评论了，一般访问旧文章的访客大都来自搜索引擎，这是好事，但是这部分访客还会提出一些新问题，尤其是技术问题，但是可能文章中提到的技术细节你已经淡忘，这时候会让你很难办。最好的做法还是还是禁用旧文章的评论，以下SQL将禁止2009-01-01之前发表的所有文章的评论，你可以根据需要修改日期：
UPDATE wp_posts SET comment_status = 'closed' WHERE post_date < '2009-01-01' AND post_status = 'publish';
(2) 关闭所有文章的评论：
有时候很不幸，在不可抗力的威胁下，你不得不关闭所有文章的评论，可以使用以下SQL语句：
UPDATE wp_posts SET comment_status = 'closed' WHERE post_status = 'publish';
原文：http://www.ludou.org/batch-modify-wordpress-posts.html
A fix of GFW'blocking WordPress under complex environment
一个复杂环境下WP的解决被墙的实践
Maybe it 's for I am outside the GFW, I do not really know that Openshift had been banned by GFW- or least partly.
To fix this, one of the easiest ways is to use a CDN to "boost" a alias binded to your gear, and change your setting of website.
But, this has a little problem for me.
Firstly, I just moved to this blog, and links of pictures and CSSes are big problems, for they are pointing to my real URL, which is blocked.
Secondly, to access this blog quickly, I made a little change to wp-config.php.(http://www.superwbd3.tk/2013/02/diary-wordpresss-multi-domains/) to add another alias, superwbd3.tk, in order to visit it directly.
My original idea is not to let CDN impair my visit, but if I enable this, I cannot change the website of WordPress.
Catch 22.
So, here 's my way so fix this:
This is based on Openshift, but should work everywhere.
1. Use CDN on your alias.
2.You can keep the change in wp-config.php. Won't hurt you.
3.Add phpmyadmin on your blog.
[important]4.Make a backup of your database. Operations next cannot been reverse, and may cause permanent amage.[/important]
4.Replace your old domain to a new CDN-accelerated one:
To replace post_content:
UPDATE wp_posts SET post_content = REPLACE (post_content, '@@@-###.rhcloud.com', 'www.superwbd3.tk');
If pictures are attachments, change GUID:
UPDATE wp_posts SET guid = REPLACE (guid,'@@@-###.rhcloud.com', 'www.superwbd3.tk') WHERE post_type = 'attachment';
And update all CSSes' URL:
UPDATE wp_options SET option_value = REPLACE (option_value,'@@@-###.rhcloud.com', 'www.superwbd3.tk')
Now have a try.
If failed, check:
Is your CDN 's IP address also banned?
Did you change everything? Are your CSSes' URL new ones?
Simple.
1.Save all your imformation with a XML file. Backup everything.
2.Install a new blog.
3. Throw the XML file in.
4.Change all the settings.
Reasons that the old one was soooo slow:
1.Old server.
2.Had down serveral times.
3.A lot of conflicts.
Hope this time will help.
P.S:
Openshift Bind alias:
rhc alias add (name) www.superwbd3.tk
Remove alias:
rhc alias add (name) www.superwbd3.tk
请各位组员注意：
经过与其他字幕组作品的对照，我在此提议，将英文字体从微软雅黑更换为方正综艺_GBK。
我认为，新字体的可读性比雅黑更强。
superwbd
ACI字幕组CDC
附：效果对比图
中：方正黑体_GBK 英：方正综艺_GBK（人人字幕组的方案）
中：方正黑体_GBK 英：微软雅黑（参照物）
中：方正黑体简体 英：微软雅黑（ACI字幕组目前的方案）
Cloudflare has serveral options.
CDN only;
CDN + Small
CDN + Full
The last one, which I used to use, have speed limit.
Just shut it down.
Sometimes you need to use more domains for your blog.
Like, www.superwbd3.tk & superwbd3.tk.
If you set one, even if you point your DNS to its ip address, it won't make any difference.
So........
Just add these to your blog's wp-config.php:
$wphome = 'http://'.$_SERVER['HTTP_HOST'];
$wpsiteurl = 'http://'.$_SERVER['HTTP_HOST'];
define('WP_HOME', $wphome);
define('WP_SITEURL', $wpsiteurl);
That 's it.
If you refer to my record, you will know that this blog is on Openshift 's Amazon US EC2.
So, in order to "boost" a little bit, I used a CDN- just like everyone does.
Why?
1. I do not want to push Openshift too hard- since AWS 's fee is calculated by traffic, I like to save a little bit to help Redhat to make it free.
2.Cloudflare is free- and no traffic or speed limit.
Well, what we think is that since CDN have servers all over the world, your user's traffic would be routed to the nearest server to make it quick.
BUT, I am wrong this time.
With any remote Ping tool on the Internet, you will find out that all your traffic are routed to the US West servers. Ah, forgot to mention, you have to set your DNS to Cloudflare's DNS.
So, it means that ALL your traffic would go through US West.
BUT, hell, AWS is in US East, and I am in Canada East! The speed is driving me crazy.
So you know what to do: Think twice before you "take advantage" of the free CDN.
Happy new year!
I changed the theme to make it looks better.
Twenty Eleven looks nice, but...is so common.
Let us make some change.
And, I reduced my Ad. Hope they will look good~