RomandevJavaScript
diff --git a/‎docs/mfc/a-portrait-of-the-document-view-architecture.md‎
Lines changed: 3 additions & 3 deletions b/‎docs/mfc/a-portrait-of-the-document-view-architecture.md‎
Lines changed: 3 additions & 3 deletions
diff --git a/‎docs/mfc/accessing-the-embedded-month-calendar-control.md‎
Lines changed: 2 additions & 2 deletions b/‎docs/mfc/accessing-the-embedded-month-calendar-control.md‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎docs/mfc/activex-controls-on-the-internet.md‎
Lines changed: 2 additions & 2 deletions b/‎docs/mfc/activex-controls-on-the-internet.md‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎docs/mfc/adding-columns-to-the-control-report-view.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/mfc/adding-columns-to-the-control-report-view.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/mfc/adding-controls-by-hand.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/mfc/adding-controls-by-hand.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/mfc/adding-controls-to-a-property-sheet.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/mfc/adding-controls-to-a-property-sheet.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/mfc/adding-items-to-the-control.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/mfc/adding-items-to-the-control.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/mfc/allocating-gdi-resources.md‎
Lines changed: 3 additions & 3 deletions b/‎docs/mfc/allocating-gdi-resources.md‎
Lines changed: 3 additions & 3 deletions
diff --git a/‎docs/mfc/asynchronous-monikers-on-the-internet.md‎
Lines changed: 3 additions & 3 deletions b/‎docs/mfc/asynchronous-monikers-on-the-internet.md‎
Lines changed: 3 additions & 3 deletions
@@ -46,15 +46,15 @@ translation.priority.ht:
 Documents and views are paired in a typical MFC application. Data is stored in the document, but the view has privileged access to the data. The separation of document from view separates the storage and maintenance of data from its display.  
 
 ## Gaining Access to Document Data from the View  
- The view accesses its document's data either with the [GetDocument](../mfc/reference/cview-class.md#getdocument) function, which returns a pointer to the document, or by making the view class a C++ `friend` of the document class. The view then uses its access to the data to obtain the data when it is ready to draw or otherwise manipulate it.  
+ The view accesses its document's data either with the [GetDocument](../mfc/reference/cview-class.md#cview__getdocument) function, which returns a pointer to the document, or by making the view class a C++ `friend` of the document class. The view then uses its access to the data to obtain the data when it is ready to draw or otherwise manipulate it.  
 
- For example, from the view's [OnDraw](../mfc/reference/cview-class.md#ondraw) member function, the view uses **GetDocument** to obtain a document pointer. Then it uses that pointer to access a `CString` data member in the document. The view passes the string to the `TextOut` function. To see the code for this example, see [Drawing in a View](../mfc/drawing-in-a-view.md).  
+ For example, from the view's [OnDraw](../mfc/reference/cview-class.md#cview__ondraw) member function, the view uses **GetDocument** to obtain a document pointer. Then it uses that pointer to access a `CString` data member in the document. The view passes the string to the `TextOut` function. To see the code for this example, see [Drawing in a View](../mfc/drawing-in-a-view.md).  
 
 ## User Input to the View  
  The view might also interpret a mouse click within itself as either selection or editing of data. Similarly it might interpret keystrokes as data entry or editing. Suppose the user types a string in a view that manages text. The view obtains a pointer to the document and uses the pointer to pass the new data to the document, which stores it in some data structure.  
 
 ## Updating Multiple Views of the Same Document  
- In an application with multiple views of the same document — such as a splitter window in a text editor — the view first passes the new data to the document. Then it calls the document's [UpdateAllViews](../mfc/reference/cdocument-class.md#updateallviews) member function, which tells all views of the document to update themselves, reflecting the new data. This synchronizes the views.  
+ In an application with multiple views of the same document — such as a splitter window in a text editor — the view first passes the new data to the document. Then it calls the document's [UpdateAllViews](../mfc/reference/cdocument-class.md#cdocument__updateallviews) member function, which tells all views of the document to update themselves, reflecting the new data. This synchronizes the views.  
 
 ### What do you want to know more about  
 
 
@@ -38,7 +38,7 @@ translation.priority.ht:
   - "zh-tw"
 ---
 # Accessing the Embedded Month Calendar Control
-The embedded month calendar control object can be accessed from the `CDateTimeCtrl` object with a call to the [GetMonthCalCtrl](../mfc/reference/cdatetimectrl-class.md#getmonthcalctrl) member function.  
+The embedded month calendar control object can be accessed from the `CDateTimeCtrl` object with a call to the [GetMonthCalCtrl](../mfc/reference/cdatetimectrl-class.md#cdatetimectrl__getmonthcalctrl) member function.  
 
 > [!NOTE]
 >  The embedded month calendar control is used only when the date and time picker control does not have the **DTS_UPDOWN** style set.  
@@ -47,7 +47,7 @@ The embedded month calendar control object can be accessed from the `CDateTimeCt
 
  In other words, when the user requests the display of the month calendar control, a new month calendar control is created (before the **DTN_DROPDOWN** notification). The control is destroyed (after the **DTN_CLOSEUP** notification) when dismissed by the user. This means that any attributes you modify, before the embedded control is displayed, are lost when the embedded control is dismissed.  
 
- The following example demonstrates this procedure, using a handler for the **DTN_DROPDOWN** notification. The code changes the background color of the month calendar control, with a call to [SetMonthCalColor](../mfc/reference/cdatetimectrl-class.md#setmonthcalcolor), to gray. The code is as follows:  
+ The following example demonstrates this procedure, using a handler for the **DTN_DROPDOWN** notification. The code changes the background color of the month calendar control, with a call to [SetMonthCalColor](../mfc/reference/cdatetimectrl-class.md#cdatetimectrl__setmonthcalcolor), to gray. The code is as follows:  
 
  [!code-cpp[NVC_MFCControlLadenDialog#5](../mfc/codesnippet/CPP/accessing-the-embedded-month-calendar-control_1.cpp)]  
 
 
@@ -144,11 +144,11 @@ ActiveX controls are the updated version of the OLE control specification. Contr
 
      [!code-cpp[NVC_MFCActiveXControl#4](../mfc/codesnippet/CPP/activex-controls-on-the-internet_4.cpp)]  
 
-6.  In [DoPropExchange](../mfc/reference/colecontrol-class.md#dopropexchange), add the following line:  
+6.  In [DoPropExchange](../mfc/reference/colecontrol-class.md#colecontrol__dopropexchange), add the following line:  
 
      [!code-cpp[NVC_MFCActiveXControl#5](../mfc/codesnippet/CPP/activex-controls-on-the-internet_5.cpp)]  
 
-7.  Override [ResetData](../mfc/reference/cdatapathproperty-class.md#resetdata) to notify the property to reset its control by adding this line:  
+7.  Override [ResetData](../mfc/reference/cdatapathproperty-class.md#cdatapathproperty__resetdata) to notify the property to reset its control by adding this line:  
 
      [!code-cpp[NVC_MFCActiveXControl#6](../mfc/codesnippet/CPP/activex-controls-on-the-internet_6.cpp)]  
 
 
@@ -46,7 +46,7 @@ translation.priority.ht:
 
  Each column has an associated header item (see [CHeaderCtrl](../mfc/reference/cheaderctrl-class.md)) object that labels the column and allows users to resize the column.  
 
- If your list control supports a report view, you need to add a column for each possible subitem in a list control item. Add a column by preparing an [LV_COLUMN](http://msdn.microsoft.com/library/windows/desktop/bb774743) structure and then making a call to [InsertColumn](../mfc/reference/clistctrl-class.md#insertcolumn). After adding the necessary columns (sometimes referred to as header items), you can reorder them using member functions and styles belonging to the embedded header control. For more information, see [Ordering Items in the Header Control](../mfc/ordering-items-in-the-header-control.md).  
+ If your list control supports a report view, you need to add a column for each possible subitem in a list control item. Add a column by preparing an [LV_COLUMN](http://msdn.microsoft.com/library/windows/desktop/bb774743) structure and then making a call to [InsertColumn](../mfc/reference/clistctrl-class.md#clistctrl__insertcolumn). After adding the necessary columns (sometimes referred to as header items), you can reorder them using member functions and styles belonging to the embedded header control. For more information, see [Ordering Items in the Header Control](../mfc/ordering-items-in-the-header-control.md).  
 
 > [!NOTE]
 >  If the list control is created with the **LVS_NOCOLUMNHEADER** style, any attempt to insert columns will be ignored.  
 
@@ -41,7 +41,7 @@ translation.priority.ht:
 # Adding Controls By Hand
 You can either [add controls to a dialog box with the dialog editor](../mfc/using-the-dialog-editor-to-add-controls.md) or add them yourself, with code.  
 
- To create a control object yourself, you will usually embed the C++ control object in a C++ dialog or frame-window object. Like many other objects in the framework, controls require two-stage construction. You should call the control's **Create** member function as part of creating the parent dialog box or frame window. For dialog boxes, this is usually done in [OnInitDialog](../mfc/reference/cdialog-class.md#oninitdialog), and for frame windows, in [OnCreate](../mfc/reference/cwnd-class.md#oncreate).  
+ To create a control object yourself, you will usually embed the C++ control object in a C++ dialog or frame-window object. Like many other objects in the framework, controls require two-stage construction. You should call the control's **Create** member function as part of creating the parent dialog box or frame window. For dialog boxes, this is usually done in [OnInitDialog](../mfc/reference/cdialog-class.md#cdialog__oninitdialog), and for frame windows, in [OnCreate](../mfc/reference/cwnd-class.md#cwnd__oncreate).  
 
  The following example shows how you might declare a `CEdit` object in the class declaration of a derived dialog class and then call the **Create** member function in `OnInitDialog`. Because the `CEdit` object is declared as an embedded object, it is automatically constructed when the dialog object is constructed, but it must still be initialized with its own **Create** member function.  
 
 
@@ -36,7 +36,7 @@ translation.priority.ht:
 # Adding Controls to a Property Sheet
 By default, a property sheet allocates window area for the property pages, the tab index, and the OK, Cancel, and Apply buttons. (A modeless property sheet does not have the OK, Cancel, and Apply buttons.) You can add other controls to the property sheet. For example, you can add a preview window to the right of the property page area to show the user what the current settings would look like if applied to an external object.  
 
- You can add controls to the property sheet dialog in the `OnCreate` handler. Accommodating additional controls usually requires expanding the size of the property sheet dialog. After calling the base class **CPropertySheet::OnCreate**, call [GetWindowRect](../mfc/reference/cwnd-class.md#getwindowrect) to get the width and height of the currently allocated property sheet window, expand the rectangle's dimensions, and call [MoveWindow](../mfc/reference/cwnd-class.md#movewindow) to change the size of the property sheet window.  
+ You can add controls to the property sheet dialog in the `OnCreate` handler. Accommodating additional controls usually requires expanding the size of the property sheet dialog. After calling the base class **CPropertySheet::OnCreate**, call [GetWindowRect](../mfc/reference/cwnd-class.md#cwnd__getwindowrect) to get the width and height of the currently allocated property sheet window, expand the rectangle's dimensions, and call [MoveWindow](../mfc/reference/cwnd-class.md#cwnd__movewindow) to change the size of the property sheet window.  
 
 ## See Also  
  [Property Sheets](../mfc/property-sheets-mfc.md)   
 
@@ -33,7 +33,7 @@ translation.priority.ht:
   - "zh-tw"
 ---
 # Adding Items to the Control
-To add items to the list control ([CListCtrl](../mfc/reference/clistctrl-class.md)), call one of several versions of the [InsertItem](../mfc/reference/clistctrl-class.md#insertitem) member function, depending on what information you have. One version takes a [LV_ITEM](http://msdn.microsoft.com/library/windows/desktop/bb774760) structure that you prepare. Because the `LV_ITEM` structure contains numerous members, you have greater control over the attributes of the list control item.  
+To add items to the list control ([CListCtrl](../mfc/reference/clistctrl-class.md)), call one of several versions of the [InsertItem](../mfc/reference/clistctrl-class.md#clistctrl__insertitem) member function, depending on what information you have. One version takes a [LV_ITEM](http://msdn.microsoft.com/library/windows/desktop/bb774760) structure that you prepare. Because the `LV_ITEM` structure contains numerous members, you have greater control over the attributes of the list control item.  
 
  Two important members (in regard to the report view) of the `LV_ITEM` structure are the `iItem` and `iSubItem` members. The `iItem` member is the zero-based index of the item the structure is referencing and the `iSubItem` member is the one-based index of a subitem, or zero if the structure contains information about an item. With these two members you determine, per item, the type and value of subitem information that is displayed when the list control is in report view. For more information, see [CListCtrl::SetItem](../mfc/reference/clistctrl-class.md#clistctrl__setitem).  
 
 
@@ -42,11 +42,11 @@ This article explains how to allocate and deallocate the Windows graphics device
   
  Suppose you need to use certain fonts, pens, or other GDI objects for printing, but not for screen display. Because of the memory they require, it's inefficient to allocate these objects when the application starts up. When the application isn't printing a document, that memory might be needed for other purposes. It's better to allocate them when printing begins, and then delete them when printing ends.  
 
- To allocate these GDI objects, override the [OnBeginPrinting](../mfc/reference/cview-class.md#onbeginprinting) member function. This function is well suited to this purpose for two reasons: the framework calls this function once at the beginning of each print job and, unlike [OnPreparePrinting](../mfc/reference/cview-class.md#onprepareprinting), this function has access to the [CDC](../mfc/reference/cdc-class.md) object representing the printer device driver. You can store these objects for use during the print job by defining member variables in your view class that point to GDI objects (for example, **CFont \*** members, and so on).  
+ To allocate these GDI objects, override the [OnBeginPrinting](../mfc/reference/cview-class.md#cview__onbeginprinting) member function. This function is well suited to this purpose for two reasons: the framework calls this function once at the beginning of each print job and, unlike [OnPreparePrinting](../mfc/reference/cview-class.md#cview__onprepareprinting), this function has access to the [CDC](../mfc/reference/cdc-class.md) object representing the printer device driver. You can store these objects for use during the print job by defining member variables in your view class that point to GDI objects (for example, **CFont \*** members, and so on).  
 
- To use the GDI objects you've created, select them into the printer device context in the [OnPrint](../mfc/reference/cview-class.md#onprint) member function. If you need different GDI objects for different pages of the document, you can examine the `m_nCurPage` member of the [CPrintInfo](../mfc/reference/cprintinfo-structure.md) structure and select the GDI object accordingly. If you need a GDI object for several consecutive pages, Windows requires that you select it into the device context each time `OnPrint` is called.  
+ To use the GDI objects you've created, select them into the printer device context in the [OnPrint](../mfc/reference/cview-class.md#cview__onprint) member function. If you need different GDI objects for different pages of the document, you can examine the `m_nCurPage` member of the [CPrintInfo](../mfc/reference/cprintinfo-structure.md) structure and select the GDI object accordingly. If you need a GDI object for several consecutive pages, Windows requires that you select it into the device context each time `OnPrint` is called.  
 
- To deallocate these GDI objects, override the [OnEndPrinting](../mfc/reference/cview-class.md#onendprinting) member function. The framework calls this function at the end of each print job, giving you the opportunity to deallocate printing-specific GDI objects before the application returns to other tasks.  
+ To deallocate these GDI objects, override the [OnEndPrinting](../mfc/reference/cview-class.md#cview__onendprinting) member function. The framework calls this function at the end of each print job, giving you the opportunity to deallocate printing-specific GDI objects before the application returns to other tasks.  
 
 ## See Also  
  [Printing](../mfc/printing.md)   
 
@@ -66,15 +66,15 @@ The Internet requires new approaches to application design because of its slow n
 ## MFC Classes for Data Paths in ActiveX Controls  
  The MFC classes `CDataPathProperty` and [CCachedDataPathProperty](../mfc/reference/ccacheddatapathproperty-class.md) implement ActiveX control properties that can be loaded asynchronously. Asynchronous properties are loaded after synchronous initiation. Asynchronous ActiveX controls repeatedly invoke a callback to indicate availability of new data during a lengthy property exchange process.  
 
- `CDataPathProperty` is derived from `CAsyncMonikerFile`. `CCachedDataPathProperty` is derived from `CDataPathProperty`. To implement asynchronous properties in your ActiveX controls, derive a class from `CDataPathProperty` or `CCachedDataPathProperty`, and override [OnDataAvailable](../mfc/reference/casyncmonikerfile-class.md#ondataavailable) and other notifications you wish to receive.  
+ `CDataPathProperty` is derived from `CAsyncMonikerFile`. `CCachedDataPathProperty` is derived from `CDataPathProperty`. To implement asynchronous properties in your ActiveX controls, derive a class from `CDataPathProperty` or `CCachedDataPathProperty`, and override [OnDataAvailable](../mfc/reference/casyncmonikerfile-class.md#casyncmonikerfile__ondataavailable) and other notifications you wish to receive.  
 
 #### To download a file using asynchronous monikers  
 
 1.  Declare a class derived from [CAsyncMonikerFile](../mfc/reference/casyncmonikerfile-class.md).  
 
-2.  Override [OnDataAvailable](../mfc/reference/casyncmonikerfile-class.md#ondataavailable) to display the data.  
+2.  Override [OnDataAvailable](../mfc/reference/casyncmonikerfile-class.md#casyncmonikerfile__ondataavailable) to display the data.  
 
-3.  Override other member functions, including [OnProgress](../mfc/reference/casyncmonikerfile-class.md#onprogress), [OnStartBinding](../mfc/reference/casyncmonikerfile-class.md#onstartbinding), and [OnStopBinding](../mfc/reference/casyncmonikerfile-class.md#onstopbinding).  
+3.  Override other member functions, including [OnProgress](../mfc/reference/casyncmonikerfile-class.md#casyncmonikerfile__onprogress), [OnStartBinding](../mfc/reference/casyncmonikerfile-class.md#casyncmonikerfile__onstartbinding), and [OnStopBinding](../mfc/reference/casyncmonikerfile-class.md#casyncmonikerfile__onstopbinding).  
 
 4.  Declare an instance of this class and use it to open URLs.