Skip to content

Commit 4440ec3

Browse files
author
Colin Robertson
committed
Bulk fix ja-jp-228 ellipsis misspelling
1 parent d751f00 commit 4440ec3

13 files changed

Lines changed: 21 additions & 21 deletions

‎docs/atl/reference/cpatht-class.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -51,8 +51,8 @@ The ATL/MFC string class to use for the path (see [CStringT](../../atl-mfc-share
5151
|[CPathT::Canonicalize](#canonicalize)|Call this method to convert the path to canonical form.|
5252
|[CPathT::Combine](#combine)|Call this method to concatenate a string representing a directory name and a string representing a file path name into one path.|
5353
|[CPathT::CommonPrefix](#commonprefix)|Call this method to determine whether the specified path shares a common prefix with the current path.|
54-
|[CPathT::CompactPath](#compactpath)|Call this method to truncate a file path to fit within a given pixel width by replacing path components with ellipses.|
55-
|[CPathT::CompactPathEx](#compactpathex)|Call this method to truncate a file path to fit within a given number of characters by replacing path components with ellipses.|
54+
|[CPathT::CompactPath](#compactpath)|Call this method to truncate a file path to fit within a given pixel width by replacing path components with ellipsis.|
55+
|[CPathT::CompactPathEx](#compactpathex)|Call this method to truncate a file path to fit within a given number of characters by replacing path components with ellipsis.|
5656
|[CPathT::FileExists](#fileexists)|Call this method to check whether the file at this path name exists.|
5757
|[CPathT::FindExtension](#findextension)|Call this method to find the position of the file extension within the path.|
5858
|[CPathT::FindFileName](#findfilename)|Call this method to find the position of the file name within the path.|
@@ -237,7 +237,7 @@ A prefix is one of these types: "C:\\\\", ".", "..", "..\\\\". For more informat
237237
238238
## <a name="compactpath"></a> CPathT::CompactPath
239239
240-
Call this method to truncate a file path to fit within a given pixel width by replacing path components with ellipses.
240+
Call this method to truncate a file path to fit within a given pixel width by replacing path components with ellipsis.
241241
242242
```
243243
BOOL CompactPath(HDC hDC, UINT nWidth);
@@ -261,7 +261,7 @@ For more information, see [PathCompactPath](/windows/win32/api/shlwapi/nf-shlwap
261261
262262
## <a name="compactpathex"></a> CPathT::CompactPathEx
263263
264-
Call this method to truncate a file path to fit within a given number of characters by replacing path components with ellipses.
264+
Call this method to truncate a file path to fit within a given number of characters by replacing path components with ellipsis.
265265
266266
```
267267
BOOL CompactPathEx(UINT nMaxChars, DWORD dwFlags = 0);

‎docs/c-language/calls-with-a-variable-number-of-arguments.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Calls with a Variable Number of Arguments"
33
ms.date: "11/04/2016"
4-
helpviewer_keywords: ["arguments [C++], function", "arguments [C++], variable number of", "VARARGS.H", "ellipses (...), variable number of arguments", "STDARGS.H", "function calls, arguments", "... ellipsis", "function calls, variable number of arguments"]
4+
helpviewer_keywords: ["arguments [C++], function", "arguments [C++], variable number of", "VARARGS.H", "ellipsis (...), variable number of arguments", "STDARGS.H", "function calls, arguments", "... ellipsis", "function calls, variable number of arguments"]
55
ms.assetid: 8808fb26-4822-42f5-aba3-ac64b54e151b
66
---
77
# Calls with a Variable Number of Arguments

‎docs/c-language/parameters.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Parameters"
33
ms.date: "11/04/2016"
4-
helpviewer_keywords: ["arguments [C++], function", "function parameters", "parameters [C++]", "function arguments, vs. parameters", "parameters [C++], function", "functions [C], parameters", "function parameters, syntax", "ellipses (...), parameters", "... ellipsis"]
4+
helpviewer_keywords: ["arguments [C++], function", "function parameters", "parameters [C++]", "function arguments, vs. parameters", "parameters [C++], function", "functions [C], parameters", "function parameters, syntax", "ellipsis (...), parameters", "... ellipsis"]
55
ms.assetid: 8f2b8026-78b5-4e21-86a3-bf0f91f05689
66
---
77
# Parameters

‎docs/c-runtime-library/format-specification-syntax-printf-and-wprintf-functions.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -163,7 +163,7 @@ The *type* character determines either the interpretation of *precision* or the
163163

164164
## Argument size specification
165165

166-
In a conversion specification, the *size* field is an argument length modifier for the *type* conversion specifier. The *size* field prefixes to the *type* field—**hh**, **h**, **j**, **l** (lowercase L), **L**, **ll**, **t**, **w**, **z**, **I** (uppercase i), **I32**, and **I64**—specify the "size" of the corresponding argument—long or short, 32-bit or 64-bit, single-byte character or wide character—depending on the conversion specifier that they modify. These size prefixes are used with *type* characters in the `printf` and `wprintf` families of functions to specify the interpretation of argument sizes, as shown in the following table. The *size* field is optional for some argument types. When no size prefix is specified, the formatter consumes integer arguments—for example, signed or unsigned `char`, `short`, `int`, `long`, and enumeration types—as 32-bit `int` types, and `float`, `double`, and `long double` floating-point arguments are consumed as 64-bit `double` types. This behavior matches the default argument promotion rules for variable argument lists. For more information about argument promotion, see Ellipses and Default Arguments in [Postfix expressions](../cpp/postfix-expressions.md). On both 32-bit and 64-bit systems, the conversion specification of a 64-bit integer argument must include a size prefix of **ll** or **I64**. Otherwise, the behavior of the formatter is undefined.
166+
In a conversion specification, the *size* field is an argument length modifier for the *type* conversion specifier. The *size* field prefixes to the *type* field—**hh**, **h**, **j**, **l** (lowercase L), **L**, **ll**, **t**, **w**, **z**, **I** (uppercase i), **I32**, and **I64**—specify the "size" of the corresponding argument—long or short, 32-bit or 64-bit, single-byte character or wide character—depending on the conversion specifier that they modify. These size prefixes are used with *type* characters in the `printf` and `wprintf` families of functions to specify the interpretation of argument sizes, as shown in the following table. The *size* field is optional for some argument types. When no size prefix is specified, the formatter consumes integer arguments—for example, signed or unsigned `char`, `short`, `int`, `long`, and enumeration types—as 32-bit `int` types, and `float`, `double`, and `long double` floating-point arguments are consumed as 64-bit `double` types. This behavior matches the default argument promotion rules for variable argument lists. For more information about argument promotion, see Ellipsis and Default Arguments in [Postfix expressions](../cpp/postfix-expressions.md). On both 32-bit and 64-bit systems, the conversion specification of a 64-bit integer argument must include a size prefix of **ll** or **I64**. Otherwise, the behavior of the formatter is undefined.
167167

168168
Some types are different sizes in 32-bit and 64-bit code. For example, `size_t` is 32 bits long in code compiled for x86, and 64 bits in code compiled for x64. To create platform-agnostic formatting code for variable-width types, you can use a variable-width argument size modifier. Alternatively, use a 64-bit argument size modifier and explicitly promote the variable-width argument type to 64 bits. The Microsoft-specific **I** (uppercase i) argument size modifier handles variable-width integer arguments, but we recommend the type-specific **j**, **t**, and **z** modifiers for portability.
169169

‎docs/cpp/anonymous-class-types.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ Anonymous classes are subject to certain restrictions. (For more information abo
4545

4646
- Cannot have a constructor or destructor.
4747

48-
- Cannot be passed as arguments to functions (unless type checking is defeated using ellipses).
48+
- Cannot be passed as arguments to functions (unless type checking is defeated using ellipsis).
4949

5050
- Cannot be returned as return values from functions.
5151

‎docs/cpp/ellipses-and-variadic-templates.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
2-
title: "Ellipses and Variadic Templates"
2+
title: "Ellipsis and Variadic Templates"
33
ms.date: "11/04/2016"
44
ms.assetid: f20967d9-c967-4fd2-b902-2bb1d5ed87e3
55
---
6-
# Ellipses and Variadic Templates
6+
# Ellipsis and Variadic Templates
77

88
This article shows how to use the ellipsis (`...`) with C++ variadic templates. The ellipsis has had many uses in C and C++. These include variable argument lists for functions. The `printf()` function from the C Runtime Library is one of the most well-known examples.
99

‎docs/cpp/postfix-expressions.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -126,26 +126,26 @@ double& func2( double& d, const char *c ) {
126126
}
127127
```
128128

129-
## Ellipses and default arguments
129+
## Ellipsis and default arguments
130130

131131
Functions can be declared to accept fewer arguments than specified in the function definition, using one of two methods: ellipsis (`...`) or default arguments.
132132

133-
Ellipses denote that arguments may be required but that the number and types are not specified in the declaration. This is normally poor C++ programming practice because it defeats one of the benefits of C++: type safety. Different conversions are applied to functions declared with ellipses than to those functions for which the formal and actual argument types are known:
133+
Ellipsis denotes that arguments may be required but that the number and types are not specified in the declaration. This is normally poor C++ programming practice because it defeats one of the benefits of C++: type safety. Different conversions are applied to functions declared with ellipsis than to those functions for which the formal and actual argument types are known:
134134

135135
- If the actual argument is of type **float**, it is promoted to type **double** prior to the function call.
136136

137137
- Any signed or unsigned **char**, **short**, enumerated type, or bit field is converted to either a signed or an unsigned **int** using integral promotion.
138138

139139
- Any argument of class type is passed by value as a data structure; the copy is created by binary copying instead of by invoking the class's copy constructor (if one exists).
140140

141-
Ellipses, if used, must be declared last in the argument list. For more information about passing a variable number of arguments, see the discussion of [va_arg, va_start, and va_list](../c-runtime-library/reference/va-arg-va-copy-va-end-va-start.md) in the *Run-Time Library Reference*.
141+
Ellipsis, if used, must be declared last in the argument list. For more information about passing a variable number of arguments, see the discussion of [va_arg, va_start, and va_list](../c-runtime-library/reference/va-arg-va-copy-va-end-va-start.md) in the *Run-Time Library Reference*.
142142

143143
For information on default arguments in CLR programming, see [Variable Argument Lists (...) (C++/CLI)](../extensions/variable-argument-lists-dot-dot-dot-cpp-cli.md).
144144

145145
Default arguments enable you to specify the value an argument should assume if none is supplied in the function call. The following code fragment shows how default arguments work. For more information about restrictions on specifying default arguments, see [Default Arguments](../cpp/default-arguments.md).
146146

147147
```cpp
148-
// expre_Ellipses_and_Default_Arguments.cpp
148+
// expre_Ellipsis_and_Default_Arguments.cpp
149149
// compile with: /EHsc
150150
#include <iostream>
151151

‎docs/cpp/sizeof-operator.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.assetid: 8bc3b6fb-54a1-4eb7-ada0-05f8c5efc532
1010
Yields the size of its operand with respect to the size of type **char**.
1111

1212
> [!NOTE]
13-
> For information about the `sizeof ...` operator, see [Ellipses and Variadic Templates](../cpp/ellipses-and-variadic-templates.md).
13+
> For information about the `sizeof ...` operator, see [Ellipsis and variadic templates](../cpp/ellipses-and-variadic-templates.md).
1414
1515
## Syntax
1616

‎docs/cpp/templates-cpp.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ The keyword **class** is equivalent to **typename** in this context. You can exp
6464
template <class T, class U, class V> class Foo{};
6565
```
6666
67-
You can use the ellipses operator (...) to define a template that takes an arbitrary number of zero or more type parameters:
67+
You can use the ellipsis operator (...) to define a template that takes an arbitrary number of zero or more type parameters:
6868
6969
```cpp
7070
template<typename... Arguments> class vtclass;

‎docs/extensions/variable-argument-lists-dot-dot-dot-cpp-cli.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.assetid: db1a27f4-02a8-4318-8690-1f2893f52b38
1010
This example shows how you can use the `...` syntax in C++/CLI to implement functions that have a variable number of arguments.
1111

1212
> [!NOTE]
13-
> This topic pertains to C++/CLI. For information about using the `...` in ISO Standard C++, see [Ellipses and Variadic Templates](../cpp/ellipses-and-variadic-templates.md) and Ellipses and Default Arguments in [Postfix expressions](../cpp/postfix-expressions.md).
13+
> This topic pertains to C++/CLI. For information about using the `...` in ISO Standard C++, see [Ellipsis and variadic templates](../cpp/ellipses-and-variadic-templates.md) and Ellipsis and default arguments in [Postfix expressions](../cpp/postfix-expressions.md).
1414
1515
The parameter that uses `...` must be the last parameter in the parameter list.
1616

0 commit comments

Comments
 (0)