From 12de1eb9a0d17c4e6c9f22eaf28ada3406533d77 Mon Sep 17 00:00:00 2001 From: Vivian Kong Date: Mon, 16 Apr 2007 17:48:06 +0000 Subject: [PATCH] fix for bug 182559: Hard-coded fonts in CDT user docs --- .../reference/cdt_o_mproj_pref_env.htm | 8 +-- .../reference/cdt_o_mproj_pref_macro.htm | 5 +- .../reference/cdt_u_mprop_env.htm | 57 ++++++++----------- .../reference/cdt_u_mprop_macros.htm | 33 +++++------ .../reference/cdt_u_mprop_manage.htm | 2 +- .../reference/cdt_u_mprop_new.htm | 2 +- .../reference/cdt_u_mprop_rename.htm | 2 +- .../tasks/cdt_t_debug_exes.htm | 4 +- .../tasks/cdt_t_indexer_enablectags.html | 5 +- .../indexer_importing_large_project.html | 5 +- 10 files changed, 52 insertions(+), 71 deletions(-) diff --git a/doc/org.eclipse.cdt.doc.user/reference/cdt_o_mproj_pref_env.htm b/doc/org.eclipse.cdt.doc.user/reference/cdt_o_mproj_pref_env.htm index 30dbb785a3c..451e3513f79 100644 --- a/doc/org.eclipse.cdt.doc.user/reference/cdt_o_mproj_pref_env.htm +++ b/doc/org.eclipse.cdt.doc.user/reference/cdt_o_mproj_pref_env.htm @@ -20,12 +20,12 @@ and one for non user-defined environment variables. Each table contains two columns:

Name of the environment variable

-

Value of the environment variable. 

+

Value of the environment variable.

You can view all environment variables that are not user-defined in the System - Variables table. 

+ Variables table. 

You can view all user-defined variables in the User - Variables table.   - A user-defined variable overrides a non user-defined variable of the same + Variables table.   + A user-defined variable overrides a non user-defined variable of the same name.  Overridden variables are displayed in bold in the System Variables table.

For more detailed information about the managed make Environment diff --git a/doc/org.eclipse.cdt.doc.user/reference/cdt_o_mproj_pref_macro.htm b/doc/org.eclipse.cdt.doc.user/reference/cdt_o_mproj_pref_macro.htm index f084e2eec60..8a5752e5008 100644 --- a/doc/org.eclipse.cdt.doc.user/reference/cdt_o_mproj_pref_macro.htm +++ b/doc/org.eclipse.cdt.doc.user/reference/cdt_o_mproj_pref_macro.htm @@ -21,10 +21,9 @@ Each table contains three columns:

Type of value contained in the build macro (see below)

Value of the build macro. 

You can view all build macros that are not user-defined in the System - Macros table.  

+ Macros table.

You can view all user-defined macros in the User - Macros table.   - A user-defined macro overrides a non user-defined macro of the same + Macros table. A user-defined macro overrides a non user-defined macro of the same name.  Overridden macros are displayed in bold in the System Macros table.

For more detailed information about managed make project build macros diff --git a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_mprop_env.htm b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_mprop_env.htm index 004a627ce8b..14f223efb97 100644 --- a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_mprop_env.htm +++ b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_mprop_env.htm @@ -11,7 +11,6 @@ {mso-style-parent:""; margin-bottom:.0001pt; font-size:12.0pt; - font-family:"Times New Roman"; margin-left:0in; margin-right:0in; margin-top:0in} --> @@ -40,15 +39,12 @@ environment variables.  Each table contains two columns:

Value of the environment variable. 

You can view all environment variables that are not user-defined in the System Variables table.  You can choose to also display all variables defined for lower-precedence contexts in the System Variables table by checking the Show parent level variables checkbox. System variables are read-only.

You can view all user-defined variables in the - User Variables table.   - A user-defined variable overrides a non user-defined + User Variables table. A user-defined variable overrides a non user-defined variable of the same name for the given level.  Overridden variables are displayed in bold in the System Variables table.

@@ -83,26 +79,22 @@ or case insensitive (on Windows systems) in its own operations be specified at several levels:

1.      - Configuration level – variables specific to the selected + lang="EN-US">1.    + Configuration level – variables specific to the selected configuration

- 2.      - Project level – variables specific to the selected project and + 2.    +Project level – variables specific to the selected project and common for all project configurations

- 3.      - Workspace level – variables specific to the current workspace

+ 3.    + Workspace level – variables specific to the current workspace

- 4.      - System environment passed to eclipse

+ 4.    + System environment passed to eclipse

When running the build utility for the selected configuration, the process' total environment @@ -126,37 +118,36 @@ definition will appear.
the value, the delimiter and the "operation" to perform on the variable of the same name defined at the lower-precedence level. The following "operations" are defined: 

+

The resulting value of the variable used for the build process will be calculated by querying all levels from bottom to top and performing the operations for the variables defined at those levels.

diff --git a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_mprop_macros.htm b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_mprop_macros.htm index 31a9b6b503a..a6845e0d982 100644 --- a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_mprop_macros.htm +++ b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_mprop_macros.htm @@ -10,7 +10,6 @@ table.MsoNormalTable {mso-style-parent:""; font-size:10.0pt; - font-family:"Times New Roman"; } --> @@ -46,16 +45,14 @@ Each table contains three columns:

You can view all build macros that are not user-defined in the System -Macros table.   table.  You can choose to also display all macros defined for lower-precedence contexts in the System Macros table by checking the Show parent context macros checkbox. System macros are read-only.

You can view all user-defined macros in the User -Macros table.   - A user-defined macro overrides a non user-defined macro of +Macros table.   + A user-defined macro overrides a non user-defined macro of the same name for the given context.  Overridden macros are displayed in bold in the System Macros table.

@@ -75,11 +72,11 @@ encouraged that a macro name begin with a letter and contain only letters, digits and underscore signs. Build macro names are case sensitive.
-If the actual value of text property contains ${text}, +If the actual value of text property contains ${text}, it must be pre-pended with a backslash in order to distinguish it from a build macro. The Managed Build System (MBS) pre-defines many useful macros (see below) and allows tool integrators and users to define -additional macros.

+additional macros.

Build Macros can hold several types of values:

    @@ -208,15 +205,13 @@ Type

    Represents the input file name. The input file has the following meaning:

    1.      - If a tool does not accept building multiple files of the + style="text-align: justify; text-indent: -0.25in; margin-left: 0.25in;">1.    + If a tool does not accept building multiple files of the primary input type with one tool invocation, the input file is the file of the primary input type being built.

    2.      - If a tool accepts building multiple files of the primary + style="text-align: justify; text-indent: -0.25in; margin-left: 0.25in;">2.    + If a tool accepts building multiple files of the primary input type with one tool invocation the input file is undefined and the macros representing the input file contain information about one of the inputs of the primary input type being built.

    @@ -297,16 +292,14 @@ input file directory path relative to the builder current directory.

    Represents the output file name. The output file has the following meaning:

    1.      - If a tool is not capable of producing multiple files of + style="text-align: justify; text-indent: -0.25in; margin-left: 0.25in;">1.    + If a tool is not capable of producing multiple files of the primary output type with one tool invocation the output file is the file of the primary output type that is built with a given tool invocation.

    2.      - If a tool is capable of producing multiple files of the + style="text-align: justify; text-indent: -0.25in; margin-left: 0.25in;">2.    + If a tool is capable of producing multiple files of the primary output type with one tool invocation the output file is undefined and the macros representing the output file contain information about one of the files of the primary output type that are diff --git a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_mprop_manage.htm b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_mprop_manage.htm index 0644ddf9eb7..57dfaf83762 100644 --- a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_mprop_manage.htm +++ b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_mprop_manage.htm @@ -19,7 +19,7 @@ rename, remove or convert a configuration.

    Debugging Existing Executables - + @@ -37,7 +37,7 @@

    Expand the executable in the C++ Projects view to see the list of source files. Only executables built with debug symbols will show a list of source files. The source files can be opened in the editor so you can set breakpoints. Use these files only for debugging, you can not change them and rebuild the executable with this project.

    C++ Projects View

- +

Related concepts
Debug overview
Debug information

diff --git a/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_indexer_enablectags.html b/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_indexer_enablectags.html index 37017f0997e..400be5873e4 100644 --- a/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_indexer_enablectags.html +++ b/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_indexer_enablectags.html @@ -3,10 +3,9 @@ + Enable/Disable CTags Indexer - - +

Enable/Disable CTags Indexer

diff --git a/doc/org.eclipse.cdt.doc.user/tasks/indexer_importing_large_project.html b/doc/org.eclipse.cdt.doc.user/tasks/indexer_importing_large_project.html index 6c19c7ad4ae..57dfa599b53 100644 --- a/doc/org.eclipse.cdt.doc.user/tasks/indexer_importing_large_project.html +++ b/doc/org.eclipse.cdt.doc.user/tasks/indexer_importing_large_project.html @@ -3,10 +3,9 @@ + Indexing a large project - - +

Indexing a large project