<authentication mode="Windows"/>
<authorization>
<deny users="?" />
</authorization>

Then all Windows users can access your pages but those without Windows login (from internet) will receive an ASP.NET "Access Denied 401" page. I have decided to replace this default message with some custom page. After couple of hours Googling, I found out that this is a very common problem and all the workarounds which seem to be reasonable does not work. Here are some of them:

1. Use a custom error page in Web.config:

   <customErrors defaultRedirect="ErrorPage.asp&shy;x" mode="On">
       <error statusCode="401" redirect="AccessDenied.aspx" />
       </customErrors>

   This works fine with statusCode="404" but not with 401.

2. Try to catch an unauthorized request in one of the application events in Global.asax.cs:

   protected void Application_AuthenticateRequest(Object sender,
       EventArgs e)
       {
       if (!Request.IsAuthenticated) Response.Redirect(
       "AccessDenied.aspx");
       }

   It is also useless, because even the browsers with valid credentials make two posts, one without credentials and having Request.IsAuthenticated=false and the other one with credentials and having Request.IsAuthenticated=true. Browsers without credentials make only one post. It means you are not able to determine if the first post having Request.IsAuthenticated=false comes from an unauthorized browser or not.

The problem

Then I found an answer from a Guru at microsoft.public.dotnet.framework.aspnet.security newsgroup.

That's correct. There's no way around that. The way wininet authentication works is that if the resource you are requesting does not allow anonymous access, a 401 is sent back to the browser. If the resource is using Windows Integrated authentication and the browser is configured to automatically send credentials, the token is sent back and the user is authenticated. In the case of Basic authentication, a login prompt is displayed and the user must log in.

If you intercept the 401 and redirect somewhere, you hijack the browser's ability to challenge. There is no way around that.

Jxx Cxxxxxx, MCSE, MCSD [MSFT], Developer Support, ASP.NET.

Resolution

That was also the result of my research. The whole thing works like this:

1. The browser sends request without credentials to the server.
2. Server rejects this request and answers with "401 Access Denied".
3. Browser recognizes 401 and if it has appropriate credentials does not show this message. The second request with credentials will be posted. The requested page will be sent to the browser.
4. If the browser has no credentials the second post will not take place. The received "401 Access Denied" will be shown.

The workaround is to manipulate the content of "401 Access Denied" response. The browser uses the header of this response to determine 401 case. It means we can manipulate the HTML content without influencing the whole challenge. For instance we can add the following code in the Application_EndRequest event of Global.asax.cs.

  protected void Application_EndRequest(Object sender,
EventArgs e)
{
HttpContext context = HttpContext.Current;
if (context.Response.Status.Substring(0,3).Equals("401"))
{
context.Response.ClearContent();
context.Response.Write("<script language="javascript">" +
"self.location='../login.aspx';</script>");
}
}

Now, the whole thing works like this:

1. The browser sends request without credentials to the server.
2. Server rejects this request and answers with "401 Access Denied" Header + our JavaScript.
3. Browser recognizes 401 and if it has appropriate credentials does not show this message. Our HTML will not be rendered and JavaScript will not be executed. The second request with credentials will be posted. The requested page will be sent to the browser.
4. If the browser has no credentials, the second post will not take place. The received "401 Access Denied" will be shown. Our HTML will be rendered and JavaScript will be executed. The client side redirection will take place. The browser will show a custom 401 page.

GhostDoc

   GhostDoc是Visual Studio的一个免费插件，可以帮助开发者生成比较完整规范的XML格式代码注释，如果你的代码遵循微软类库开发人员设计规范 ，由它自动产生的注释就已经完全可以很好地表达开发者创建的方法或者属性的意图，无需手工再进行修改。有了这些标准的XML注释，我们可以使用微软的文档工具Sandcastle生成专业级别的帮助文档。如我们有这样一段代码：

public bool Add(string item) 

{ 

//...... 

} 



public void AppendHtmlText(IHtmlProvider htmlProvider) 

{ 

//...... 

} 

   使用GhostDoc生成的注释如下：

/// <summary> 

/// Adds the specified item. 

/// </summary> 

/// <param name="item">The item.</param> 

/// <returns></returns> 

public bool Add(string item) 

{ 

//...... 

} 



/// <summary> 

/// Appends the HTML text. 

/// </summary> 

/// <param name="htmlProvider">The HTML provider.</param> 

public void AppendHtmlText(IHtmlProvider htmlProvider) 

{ 

//...... 

} 

   官方主页：http://www.roland-weigelt.de/ghostdoc/

Sandcastle

   Sandcastle是微软发布的一个帮助文档生成工具，它通过反射程序集中的源代码和添加代码到中的XML注释来创建专业级别的帮助文档。Sandcastle于2006年推出，它的面世也使得曾经列入.NET开发必备十大工具之一的文档生成工具NDoc的作者Kevin Downs在2006年7月宣告不再投入NDoc Open Source Project的开发。生成的文档效果如下图所示：



Nunit

   NUnit 是为 .NET 框架生成的开放源代码单元测试框架。NUnit 使你可以用你喜欢的语言编写测试，从而测试应用程序的特定功能。当你首次编写代码时，单元测试是一种测试代码功能的很好方法，它还提供了一种对应用程序进行回归测试的方法。NUnit 应用程序提供了一个用于编写单元测试的框架，以及一个运行这些测试和查看结果的图形界面。
官方主页：http://www.nunit.org/

MyGeneration

   作为.NET开发人员，手边有一款代码生成工具必不可少。旧版.NET开发必备十大工具中，作者曾经推荐了非常著名的CodeSmith，不幸的是现在CodeSmith已经商业化，需要花钱购买；幸运的是我们又有一款免费并开源的代码生成工具选择MyGeneration，它的功能丝毫不亚于CodeSmith，完全基于模板引擎进行代码的生成，如下图所示：



   官方主页：http://sourceforge.net/projects/mygeneration

Reflector for .NET

   相信大名鼎鼎的Reflector for .NET大家都已经用过了，几年前它已经位于.NET开发必备十大工具榜，现在自然也不能例外。它是一个类浏览器和反编译器，可以分析程序集并向你展示它的所有秘密。使用Reflector for .NET可以浏览程序集的类和方法，可以分析由这些类和方法生成的 Microsoft 中间语言 (MSIL)，并且可以反编译这些类和方法并查看 C# 或 Visual Basic.NET 中的等价类和方法。经过多年的发展，Reflector for .NET已经发展到了5.1版本，并且提供了相当丰富的插件，利用这些插件我们可以浏览Silverlight程序结构、浏览WPF资源文件、与TestDriven.net集成等。如下图所示：

The Regulator

   The Regulator能够使生成和测试正则表达式变得很容易，它允许你输入一个正则表达式以及一些针对其运行该表达式的输入。这样，在应用程序中实现该正则表达式之前，你便可以了解它将产生什么效果以及它将返回哪些种类的匹配项。另外它还提供了正则表达式库管理功能，在线更新正则表达式库，可以在RegexLib.com上搜索需要的正则表达式，如下图所示：



官方主页：http://sourceforge.net/projects/regulator/

LINQPad

    随着在.NET Framework 3.5中对于LINQ的支持，越来越多的开发者在开发中使用了LINQ to SQL，但是编写LINQ to SQL查询似乎又成了一件很麻烦的事情，好在我们还有LINQPad这个工具，用来编写LINQ查询，不仅仅是LINQ to SQL，同时它也支持LINQ to XML、LINQ to Objects，另外LINQPad是完全免费的且无需安装，只要下载它的可执行文件就可以了。官方主页：http://www.linqpad.net/

NAnt

   NAnt 是一个基于 .NET 的生成工具，与当前版本的 Visual Studio .NET 不同，它使得为你的项目创建生成过程变得非常容易。当你拥有大量从事单个项目的开发人员时，你不能依赖于从单个用户的座位进行生成。你也不希望必须定期手动生成该项目。你更愿意创建每天晚上运行的自动生成过程。NAnt 使你可以生成解决方案、复制文件、运行 NUnit 测试、发送电子邮件，等等。遗憾的是，NAnt 缺少漂亮的图形界面，但它的确具有可以指定应该在生成过程中完成哪些任务的控制台应用程序和 XML 文件。目前NAnt已经支持.NET Framework 3.5，它的最新版本是0.86 Beta 1。官方主页：http://nant.sourceforge.net/ 

总结

   以上工具笔者在原有的.NET开发必备十大工具基础之上，加以整理，添加了一些新的优秀的工具，也许有朋友会说，还有很多比这些工具更优秀的工具，没错，是有这样的工具，但是笔者要说的是，上述十个工具，不仅考虑它的实用性，有一点更为重要的是，它们都是免费的，而且有很多是开源的！

   为了便于大家对比，此处列出旧版.NET开发必备十大工具：
   代码段编译工具：Snippet Compiler
   正则表达式工具：Regulator
   代码生成工具：CodeSmith（已经商业化）
   编写单元测试工具：NUnit
   监视代码工具：FxCop
   程序集分析检查工具：Reflector
   创建代码文档工具：NDoc（已经停止开发）
   生成解决方案工具：NAnt
   ASPNET版本转换器
   VSNET项目转换器

1

Returning an IDENTITY From an INSERT

SELECT @@IDENTITY

INSERT INTO Products (ProductName) VALUES ('Chalk')
SELECT @@IDENTITY

Set oRs = oCn.Execute("SET NOCOUNT ON;INSERT INTO Products _
(ProductName) VALUES ('ChalkSELECT @@IDENTITY")
lProductID = oRs(0)

CREATE TRIGGER trProducts_Insert ON Products FOR INSERT AS
SELECT @@IDENTITY
GO

Inline Views Versus Temp Tables

CREATE TABLE #Temp1 (OrderID INT NOT NULL, _
OrderDate DATETIME NOT NULL)
INSERT INTO #Temp1 (OrderID, OrderDate)
SELECT     TOP 5 o.OrderID, o.OrderDate
FROM Orders o ORDER BY o.OrderDate DESC
SELECT     p.ProductName, SUM(od.Quantity) AS ProductQuantity
FROM     #Temp1 t
INNER JOIN [Order Details] od ON t.OrderID = od.OrderID
INNER JOIN Products p ON od.ProductID = p.ProductID
GROUP BY p.ProductName
ORDER BY p.ProductName
DROP TABLE #Temp1

SELECT p.ProductName,
SUM(od.Quantity) AS ProductQuantity
FROM     (
SELECT TOP 5 o.OrderID, o.OrderDate
FROM     Orders o
ORDER BY o.OrderDate DESC
) t
INNER JOIN [Order Details] od ON t.OrderID = od.OrderID
INNER JOIN Products p ON od.ProductID = p.ProductID
GROUP BY
p.ProductName
ORDER BY
p.ProductName

Avoid LEFT JOINs and NULLs

Use Cartesian Products Wisely

Odds and Ends

SELECT <non-pivoted column> ,

    [first pivoted column] AS <column name> ,

    [second pivoted column] AS <column name> ,

    ...

    [last pivoted column] AS <column name>

FROM

    ( <SELECT query that produces the data> )

    AS <alias for the source query>

PIVOT

(

    <aggregation function>( <column being aggregated> )

FOR

[<column that contains the values that will become column headers>]

    IN ( [first pivoted column] , [second pivoted column] ,

    ... [last pivoted column] )

) AS <alias for the pivot table>

<optional ORDER BY clause>

SELECT <non-pivoted column>,

    [first pivoted column] AS <column name>,

    [second pivoted column] AS <column name>,

    ...

    [last pivoted column] AS <column name>

FROM

    (<SELECT query that produces the data>)

    AS <alias for the source query>

PIVOT

(

    <aggregation function>(<column being aggregated>)

FOR

[<column that contains the values that will become column headers>]

    IN ( [first pivoted column], [second pivoted column],

    ... [last pivoted column])

) AS <alias for the pivot table>

<optional ORDER BY clause>

This could be applied to the .NET and Java APIs to reduce the amount of required try/catchs. For example, the File.IO.OpenRead method could be (shown here is the artist's representation):

 public static FileStream OpenRead (string file)

 {

         int fd = open (file);

         if (f == -1)

                 return null;

         return new FileStreamFromFD (f);

 }

Which makes null a valid return value. If you fail to check for the return value, you would get a nice NullReferenceException, but you would allow the expensive creation of an exception object, and the ugly try/catch block in the call site.

Obviously we can not change the existing APIs, but we could encourage developers to minimize their use of exceptions. In my limited personal experience with software design, when I have faced applications with tons of Exceptions it was extremely hard to keep up with them. A rewrite of the software to avoid exceptions and use the more sane API paid for.

Here is the rationale for exceptions rather than error codes for exceptional situations. (thanks to Jason Clark for writting these up for us)  

There are many benefits to exception handling as compared to return value based error reporting. In fact, the Framework exposes more of the benefits of exception handling then some other common exception models such as Win32 SEH or C++ exception handling. Good managed API design does not restrict the application developer from realizing the benefits of exceptions. The following are some of these benefits.

Exceptions Promote API Consistency

Consistency of API is important to developers.  Exceptions promote consistency, because they are designed to be used for failure reporting (and nothing else).  In contrast, return values have many uses of which failure reporting is only a subset.  For this reason, it is likely that APIs that report failure through return values will find a number of patterns, while exceptions can be constrained to specific patterns.  The Win32 API is a clear example of this inconsistency through BOOLs, HRESULTS, and GetLastError() among others.

Exceptions are Compatible with Object Oriented Features

Object-Oriented languages tend to impose constraints on method signatures that are not imposed by functions in functional programming.  For example, constructor methods, operator overloads, virtual methods, generic methods, interface methods and properties all resolve to functions, and yet the developer writing the method has no choice in the return value (if any) of the method.  For this reason, it is not possible to standardize on return value based error reporting for object oriented APIs. An error reporting method, such as exceptions, which is out of band of the method signature is the only option.

With Exceptions, Error Handling Code Need not be Near Failing Code

With return-value based error reporting error handling code is always very near to the code that could fail.  However, with exception handling the application developer has a choice.  Code can be written to catch exceptions near the failure point, or the handling code can be further up in the call stack.

With Exceptions, Error Handling Code is More Localized

Very robust code that reports failure through return values tends to have an if statement for every functional line of code.  The job of these if statements is to handle the failure case.  With exception oriented code, robust code can often be written such that a number of methods and operations can be performed with the error handling logic grouped at the end of the try block (or even higher in the call-stack). 

A common argument is that exception handling code is unsightly.  This argument is usually being made by someone comparing well written exception handling code with return value oriented code that is not sufficiently checking return values of functions. 

Exceptions Are Not Easily Ignored

Return values can be easily ignored, and often are. Exceptions, on the other hand, take an active role in the flow of your code.  This makes failures reported as exceptions difficult to ignore, and improves the robustness of code.
For example the Win32 API CloseHandle() fails very rarely, and so it is common (and appropriate) for many applications to ignore the return value of the API.  However, if any application has a bug which causes CloseHandle() to be called twice on the same handle, it would not be obvious unless the code was written to test the return value.  A managed equivalent to this API would throw an exception in this case and the unhandled exception handler would log the failure and the bug would be found.

Exceptions Allow for Unhandled Exception Handlers

Ideally, every application is written to intelligently handle all forms of failure.  However, this is not realistic as all forms of failure can’t be known.  With return value oriented code, failures that are unexpected are ignored by code and the application continues to run with undefined results.  With well written exception based code, unexpected failures eventually cause an unhandled exception handler to be called.  This handler can be designed to log the failure, and can also make the choice to shut down the application.  This is far preferable to running with indeterminate results, and also provides for logging that makes it possible to add more significant error handling for the previously unexpected case.  (Today, Microsoft Office uses an unhandled exception handler to gracefully recover and re-launch the application as well as send error information to Microsoft to improve the product.)

You should only have a custom unhandled exception handler, if you have a have specific, app-oriented work to do in the handler. If you just want error reporting to occur, the runtime will handle that automatically for you and you do not need to (and should not) use a UEF. An application should only register a UEF if it can provide functionality above and beyond the standard error reporting that comes with the system and runtime.

Exceptions Provide Robust Error Info for Logging

Exceptions provide for a consistent error handling mechanism, and as such make it possible to have consistent logging of error information.  The System.Exception type in the Framework encapsulates stack-frame information as well as other useful information such as a nested exception type.  This is great for error logging and discovery of unexpected error cases during the QA phase.  Exceptions are objects, so it is possible to extend exceptions to add additional information.

Handling Errors Consistently and Thoroughly are Essential for Creating a Good User Experience

The application developer needs to provide specific information about what error occurred, why it occurred, and what can be done to mitigate it. This requires detailed and specific error returns from API calls. The exception mechanism allows detailed error information to be created by the API developer. There is no need for the API developer to change global header files to add new error codes. The API developer can customize the exception subclass as much as necessary to transmit all of the details of the error to the caller.

Exceptions Promote Instrumentation

Exceptions are a well-defined method-failure model.  Because of this, it is possible for tools such as debuggers, profilers, performance counters, and others to be intimately aware of exceptions.  The PerfMon application, for example, keeps track of exception statistics.  In the future automatic instrumentation from profiling to auto-documentation will be more sophisticated related to exceptions.  Methods that return failure do not share in the benefits of instrumentation.

Exceptions Unify the Error Model (Hard and Logical Errors)

Exception handling or interrupts are the only option for hard errors such as null references and divisions by zero (certain operations have no return-value means of reporting failure).  Using exception handling for API and logical failure reporting is beneficial in that it unifies error handling for all failure types

    The expensive shops in a famous near Piccadilly were just opening. At this time of the morning, the arcade was almost empty. Mr. Taylor, the owner of a jewellery shop was admiring a new display. Two of his assistants had been working busily since eight o'clock and had only just finished. Diamond necklaces and rings had been beautifully arranged on a background of black velvet. After gazing at the display for several minutes, Mr. Taylor went back into his shop. 

    The silence was suddenly broken when a large car, with its headlights on and its horn blaring, roared down the arcade. It came to a stop outside the jeweller's. One man stayed at the wheel while two others with black stocking over their faces jumped out and smashed the window of the shop with iron bars. While this was going on, Mr. Taylor was upstairs. He and his staff began throwing furniture out of the window. Chairs and tables went flying into the arcade. One of the thieves was struck by a heavy statue, but he was too busy helping himself to diamonds to notice any pain. The raid was all over in three minutes, for the men scrambled back into the car and it moved off at a fantastic speed. Just as it was leaving, Mr. Taylor rushed out and ran after it throwing ashtrays and vases, but it was impossible to stop the thieves. They had got away with thousands of pounds worth of diamonds.

Language points:
Smash-and-grab

open
v. When do you open/close?
a. We are open/closed.
opening hours -- 营业时间

jewellery -- 珠宝总称
jewel -- 宝石
jeweller -- 珠宝商人

jeweller's -- 珠宝商店
grocer's -- 杂货店
Mary's -- Mary家
St. Paul's -- 圣保罗教堂

admire -- 欣赏
I admire your courage.
We stopped to admire the view.

display -- 展示，陈列
on display

arrange -- 安排，摆放，计划
He was arranging a surpirse party for his wife's birthday.
Who arranged these flowers so beautifully?

backgroud -- 背景
historical background
educational background

gaze at -- （出于惊讶、沉思或其他情绪）常时间的盯着看
start at -- 盯着看，带有不礼貌或者愤怒的情绪
If you stare at people like that, you might upset them.

break -- 打破
break silence
break the tension
break the deadlock -- 打破僵局
break the monotony -- 打破单调
break my train of thought

the wheel -- 方向盘
wheel -- 轮胎

go flying -- go + ing强调动作的方向

be busy doing something
She is busy preparing for the exams.

help onself to something
Please help yourselt!

raid -- n.袭击, 搜捕 v. 奇袭, 搜捕
a bombing raid -- 空袭
a police raid -- 警察临检
a bank raid -- 抢银行

fantastic
You lokk fantastic!
a fantastic tale about dragons
a fanstatic amount of money

worth
n. $4,000 of equipment
a. The had got away with diamonds worth thousands of pounds.

with + n. / prep. / adj. / pp.
One man stayed at the wheel while two others with balck stocking over their faces jumped out and smashed the window of the shop with iron bars.
The silence was suddenly broken when a large car, with its headlights on and its horn blaring, roared down the arcade.







 

    Editors of newspapers and magazines often go to extremes to provide their readers with unimportant facts and statistics. Last year a journalist had been instructed by a well-known magazine to write an article on the president's palace in a new African republic. When the article arrived, the editor read the first sentence and then refuse to publish it. The article began: 'Hundreds of steps lead to the high wall which surrounds the president's palace'. The editor at once sent the journalist a fax instructing him to find out the exact number of steps and the height of the wall. 

The journalist immediately set out to obtain these important facts, but he took a long time to send them .Meanwhile, the editor was getting impatient, for the magazine would soon go to press. He sent the journalist two more faxes, but received no reply. He sent yet another fax informing the journalist that if he did not reply soon he would be fired. When the journalist again failed to reply, the editor reluctantly published the article as it had originally been written. A week later, the editor at last received a fax from the journalist. Not only had the poor man been arrested, but he had been sent to prison as well. However, he had at last been allowed to send a fax in which he informed the editor that  he had been arrested while counting the 1,084 steps leading to the fifteen-foot wall which surrounded the president's palace.

    These days, people who do manual work often receive far more money than people who work in offices. People who work in offices are `frequently referred to as "white-collar workers' for the simple reason that they usually wear a collar and tie to go to work. Such is human nature, that a great many people are often willing to `sacrifice higher pay for the `privilege of becoming white-collar workers. This can give rise to curious situations, as it did in the case of Alfred Bloggs who worked as a dustman for the Ellesmere Corporation. 

    When he got married, Alf was too embarrassed to say anything to his wife about his job. He simply told her that he worked for the Corporation. Every morning, he left home dressed in a smart black suit. He then changed into overalls and spent the next eight hours as a dustman. Before returning home at night. He took a shower and changed back into his suit. Alf did this for over two years and his fellow dustmen kept his secret Alf's wife has never discovered that she married a dustman and she never will, for Alf has just found another job. He will soon be working in an office. He will be earning only half as much as he used to, but he feels that his rise in status is well worth the loss of money. From now on, he will wear a suit all day and others will call him 'Mr. Bloggs', not 'Alf'.

Language points:
double 
collar
441322
double bed/room
double standard 

manual -- by hand
a manual typewriter
manual work/labour//mental work/labour

refer to -- be descriped
He spoke without referring to the notes.

such that
Such is life.

sacrifiee -- 为了...牺牲，give up
Many women sacrifiee their careers for their family.

privilege -- 特权
aristocratic privilege

give rise to -- be the reason whay somehing happened
The recent accident is giving rise to national concern.

curious -- 奇怪的,好奇的
Bayies are curious about everything around them.
She was wearing a curious smile on her face.

embarrassed -- 为难的，困窘的
I was really embrassed when i spilt coffee on his shirt.
He was ashamed of having lied to hi family.
He was too shy to ask her to dance with him.
He feels awkward with women.

smart -- 漂亮的，聪明的，老练的，时尚的
a smart restaurant
a smart kid
a smart lawyer

well
well ahead of time

... far more money than ...

... half as much as ...

Some time ago, an interesting discovery was made by archaeologists on the Aegean island of Kea. An American team explored a temple which stands in an ancient city on the promontory of Ayia Irini. The city at one time must have been prosperous, for it enjoyed a high level of civilization. Houses -- often three storeys（story） high -- were built of stone. They had large rooms with beautifully ‘decorated walls. The city was equipped with a drainage system, for a great many clay pipes were found be`neath the narrow streets. 

    The temple which the archaeologists explored was used as a place of worship from the fifteenth century B.C. until Roman times. In the most sacred room of temple, clay fragments of fifteen statues were found. Each of these represented a goddess and had, at one time, been painted. The body of one statue was found among remains dating from the fifteenth century B.C. It's missing head happened to be among remains of the fifth century B.C. This head must have been found in Classical times and carefully preserved. It was very old and precious even then. When the archaeologists reconstructed the fragments, they were amazed to find that the goddess turned out to be a very modern-looking woman. She stood three feet high and her hands rested on her hips. She was wearing a full-length skirt which swept the ground. De`spite her great age, she was very graceful indeed, but, so far, the archaeologists have been unable to discover her identity.

Language points:
archaeologist
n. archaeology
a. archaeological

explore -- to search and discover考察,研究
explore space
explore the issue/topic/question

promontory -- 海角

enjoy -- 喜欢，享受，享有，拥有
I enjoy meeting people.
enjoy oneself
This arctress has always enjoyed a good reputation.

be built of 
This house is built of wood.

worship -- 崇拜
act of worship
hero worship

times
Classical times -- 特指古希腊罗马时期

scared -- 神圣的， holy, divine

statue
Statue of liberty
stature -- 升高,水平
an artist of great stature
status -- 地位，身份，状态
marital status
statue -- 法令，法规
college statue

paint
paint her room pink
paint her nails
paint a picture -- 画画

remains -- 遗迹，残骸，遗体
The remains of the day -- 去日留痕
the remains of lunch
the remains of an aircraft
His remains were returened to his homeland after his death.

date from -- have been existed from
Thanks for your letter date August 15, 2002.
Archaeologists were unable to date the fossils.
Are you still dating hime?

amaze -- 惊奇，困惑，惊异，强调wonder
surpirse,astonish, astound

turn out to be -- 含有出乎意料的意思
The guy I went to meet turned out to be my former classmate.

full-lenght
full-length dress/coat
full-lenght mirror/photograph

sweep
sweep the floor

great

so far -- 到现在为止
so far so good

identity
identity card(ID card)
a sense of identity -- 身份感，归属感

a temple which stands in an ancient city
she stood three feet high
The bicycle rested against the wall.

     Our vicar is always raising money for one cause or another, but he has never managed to get enough money to have the church clock repaired. The big clock which used to strike the hours day and night was damaged many years ago and has been silent ever since. One night, however, our vicar work up with a start: the clock was striking the hours! Looking at his watch, he saw that it was one o'clock, but the bell struck thirteen times before it stopped. Armed with a torch, the vicar went up into the clock tower to see what was going on. In the torchlight, he caught sight of a figure whom he immediately recognized as Bill Wilkins, our local grocer.'Whatever are you doing up here Bill?' asked the vicar in surprise. 'I'm trying to repair the bell,' answered Bill. 'I've been coming up here night after night for weeks now. You see, I was hoping to give you a surprise.''You certainly did give me a surprise!' said the vicar. 'You've probably woken up everyone in the village as well. Still, I'm glad the bell is working again. That's the trouble, vicar,' answered Bill. 'It's working all right, but I'm afraid that at one o'clock it will strike thirteen times and there's nothing I can do about it."We'll get used to that, Bill,' said the vicar. "Thirteen is not as good as one, but it's better than nothing. Now let's go downstairs and have a cup of tea.'

Language points:
equal --平等,等于
v. Two plus two equals 4.
a. All men are created equal.
    equal pay for equal work
n. Our boss treated us all as equal.

vicar -- 牧师,神父
priest, pastor, rector, clergyman

raise -- 筹集
raise cash/captial/foud

for one cause or another
cause -- 这里是事业的意思
the cause of world peace
for one thing or another -- 总会
We'll get out of the mess in one way or another.

Pumas are large, cat-like animals which are found in America. When reports came into London Zoo that a wild puma had been spotted forty-five miles south of London, they were not taken seriously. However, as the evidence began to accumulate,   experts from the Zoo felt obliged to investigate, for the descriptions given by people who claimed to have seen the puma were extraordinarily similar. The hunt for the puma began in a small village
    where a woman picking blackberries  saw 'a large cat' only five yards away from her. It immediately  ran away  when she saw it, and experts confirmed that a puma will not attack a human being unless it is cornered. The search proved difficult, for the puma was often observed at one place in the morning and at another place twenty miles away in the evening. Wherever it went, it left behind it a trail of dead deer and small animals like rabbits. Paw prints were seen in a number of places  and puma fur  was found clinging to bushes. Several people complained of "cat-like noises' at night and a businessman on a fishing trip
    saw the puma up a tree. The experts were now fully convinced that the animal was a puma, but where had it come from? As no pumas had been reported missing from any zoo in the country, this one must have been in the possession of a private collector and somehow managed to escape. The hunt went on for several weeks, but the puma was not caught. It is disturbing to think that a dangerous wild animal is still at large in the quiet countryside.

Langue points:
be at large -- 潜逃
The escaped prisoners are still at large.

看见
spotted -- to notice something very difficulty to see.看见了不太容易看见的，或者发现了正在寻找的。I spotted someone coming out of the building.
seen -- 比较常用的
observed -- 比较书面化

accumulate -- 逐渐增加或积累

feel obliged to do -- must, have to
I felt obliged to invite him.
经常用作书面语，有责任或义务做某事。

hunt -- 捕猎，搜寻，search
go on a deer/fox hunt
the hunt for the remains of the Titanic
hunt for second-hand books
job-hunting

pick -- 采摘,挑选
pick cotton
We need to pick someone reliable.
pick and choose -- 挑挑拣拣

escape
[is'keip]
n.
逃, 逃亡, 溢出设备, 出口, 逃跑, [植]野生
vi.
逃脱, 避开, 溜走
vt.
逃避, 避免, 被忘掉

cornered -- 陷入困境，被逼得走投无路

proved -- 证明是，原来是，turn out to be
They proved her innocence
The rumour proved false.

cling to -- 粘在，固守，坚持，固执的相信
cling-clung-clung
His wet shirt clung to his body.
She clings to the belief that her husband will come back.

complain -- 抱怨，诉说
complain about the weather
complain of a headache

disturb -- 打搅，worry，令人担忧，令人不安
Sorry to disturb you.
Do not disturb.
His strange behaviour disturbed me.

link words

常用被动语态表达一种事实
had been spotted
was observed
found clinging
had beed reported