forked from buildingSMART/IFC4.3.x-output
-
Notifications
You must be signed in to change notification settings - Fork 0
/
IfcUtilityResource.pot
243 lines (176 loc) · 12.8 KB
/
IfcUtilityResource.pot
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
# Industry Foundation Classes IFC.
# Copyright (C) 2020 buildingSMART
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2020-09-25 10:09+0200\n"
"X-Crowdin-SourceKey: msgstr\n"
"Language-Team: buildingSMART community\n"
#:IFC.xml:44588
msgid "IfcApplication"
msgstr "IfcApplication"
msgid "IfcApplication_DEFINITION"
msgstr "[[IfcApplication]] holds the information about an IFC compliant application developed by an application developer. The [[IfcApplication]] utilizes a short identifying name as provided by the application developer. HISTORY New entity in IFC1.5. bSI Documentation"
#:IFC.xml:189
msgid "IfcApplication_ApplicationDeveloper"
msgstr "ApplicationDeveloper"
msgid "IfcApplication_ApplicationDeveloper_DEFINITION"
msgstr "ApplicationDeveloper"
#:IFC.xml:44597
msgid "IfcApplication_Version"
msgstr "Version"
msgid "IfcApplication_Version_DEFINITION"
msgstr "The version number of this software as specified by the developer of the application."
#:IFC.xml:44602
msgid "IfcApplication_ApplicationFullName"
msgstr "ApplicationFullName"
msgid "IfcApplication_ApplicationFullName_DEFINITION"
msgstr "The full name of the application as specified by the application developer."
#:IFC.xml:44607
msgid "IfcApplication_ApplicationIdentifier"
msgstr "ApplicationIdentifier"
msgid "IfcApplication_ApplicationIdentifier_DEFINITION"
msgstr "Short identifying name for the application."
#:IFC.xml:44637
msgid "IfcChangeActionEnum"
msgstr "IfcChangeActionEnum"
msgid "IfcChangeActionEnum_DEFINITION"
msgstr "[[IfcChangeActionEnum]] identifies the type of change that might have occurred to the object during the last session for example, added, modified, deleted . This information is required in a partial model exchange scenario so that an application or model server will know how an object might have been affected by the previous application. Valid enumerations are Consider Application A will create an IFC dataset that it wants to publish to others for modification and have the ability to subsequently merge these changes back into the original model. Before publication, it may want to set the [[IfcChangeActionEnum]] to NOCHANGE to establish a baseline so that other application changes can be easily identified. Application B then receives this IFC dataset and adds a new object and sets [[IfcChangeActionEnum]] to ADDED with Application B defined as the OwningApplication. Application B then modifies an existing object and re defines the LastModifiedDate to the time of the modification, LastModifyingUser to the [[IfcPersonAndOrganization]] making the change, and sets the LastModifyingApplication to Application B. When Application A receives this modified dataset, it can determine which objects have been added and modified by Application B and either merge or reject these changes as necessary. Consequently, the intent is that an application only modifies the value of [[IfcChangeActionEnum]] when it does something to the object, with the further intent that a model server is responsible for clearing the [[IfcChangeActionEnum]] back to NOCHANGE when it is ready to be republished. HISTORY New enumeration in IFC2.0. .change ifc2x4 IFC4 CHANGE Enumerators MODIFIEDADDED and MODIFIEDDELETED have been removed bSI Documentation"
#:IFC.xml:44644
msgid "IfcOwnerHistory"
msgstr "IfcOwnerHistory"
msgid "IfcOwnerHistory_DEFINITION"
msgstr "[[IfcOwnerHistory]] defines all history and identification related information. In order to provide fast access it is directly attached to all independent objects, relationships and properties. [[IfcOwnerHistory]] is used to identify the creating and owning application and user for the associated object, as well as capture the last modifying application and user. HISTORY New entity in IFC1.0. .change ifc2x4 IFC4 CHANGE ChangeAction is now optional and a related WHERE rule enforces conditions when it is asserted. .spec head Informal Propositions 1. If LastModifiedDate is defined but ChangeAction is not asserted, then the state of ChangeAction is assumed to be UNDEFINED. 2. If both LastModifiedDate and ChangeAction are asserted, then the state of ChangeAction applies to the value asserted in LastModifiedDate. bSI Documentation"
#:IFC.xml:329
msgid "IfcOwnerHistory_LastModifyingUser"
msgstr "LastModifyingUser"
msgid "IfcOwnerHistory_LastModifyingUser_DEFINITION"
msgstr "LastModifyingUser"
#:IFC.xml:341
msgid "IfcOwnerHistory_OwningUser"
msgstr "OwningUser"
msgid "IfcOwnerHistory_OwningUser_DEFINITION"
msgstr "OwningUser"
#:IFC.xml:44613
msgid "IfcOwnerHistory_OwningApplication"
msgstr "OwningApplication"
msgid "IfcOwnerHistory_OwningApplication_DEFINITION"
msgstr "OwningApplication"
#:IFC.xml:44625
msgid "IfcOwnerHistory_LastModifyingApplication"
msgstr "LastModifyingApplication"
msgid "IfcOwnerHistory_LastModifyingApplication_DEFINITION"
msgstr "LastModifyingApplication"
#:IFC.xml:44649
msgid "IfcOwnerHistory_State"
msgstr "State"
msgid "IfcOwnerHistory_State_DEFINITION"
msgstr "Enumeration that defines the current access state of the object."
#:IFC.xml:44654
msgid "IfcOwnerHistory_ChangeAction"
msgstr "ChangeAction"
msgid "IfcOwnerHistory_ChangeAction_DEFINITION"
msgstr "Enumeration that defines the actions associated with changes made to the object."
#:IFC.xml:44659
msgid "IfcOwnerHistory_LastModifiedDate"
msgstr "LastModifiedDate"
msgid "IfcOwnerHistory_LastModifiedDate_DEFINITION"
msgstr "Date and Time expressed in UTC Universal Time Coordinated, formerly Greenwich Mean Time or GMT at which the last modification was made by LastModifyingUser and LastModifyingApplication."
#:IFC.xml:44664
msgid "IfcOwnerHistory_CreationDate"
msgstr "CreationDate"
msgid "IfcOwnerHistory_CreationDate_DEFINITION"
msgstr "The date and time expressed in UTC Universal Time Coordinated, formerly Greenwich Mean Time or GMT when first created by the original OwningApplication. Once defined this value remains unchanged through the lifetime of the entity."
#:IFC.xml:44670
msgid "IfcStateEnum"
msgstr "IfcStateEnum"
msgid "IfcStateEnum_DEFINITION"
msgstr "The [[IfcStateEnum]] enumeration identifies the state or accessibility of the object for example, read write, locked . Valid enumerations are HISTORY New enumeration in IFC2.0. .change ifc2x3 IFC2x3 CHANGE This concept was initially introduced in IFC2.0 as IfcModifiedFlag of type BINARY 3 FIXED and has been modified in R2x3 to an enumeration. It was initially introduced as a first step towards providing facilities for partial model exchange and is intended for use primarily by a model server so that an application can identify the state of the object. bSI Documentation"
#:IFC.xml:44677
msgid "IfcTable"
msgstr "IfcTable"
msgid "IfcTable_DEFINITION"
msgstr "An [[IfcTable]] is a data structure for the provision of information in the form of rows and columns. Each instance may have [[IfcTableColumn]] instances that define the name, description and units for each column. The rows of information are stored as a list of [[IfcTableRow]] objects. Limitation For backwards compatibility, the rows of an [[IfcTable]] object are constrained to have the same number of cells. The first row of the table provides the number of cells. All other rows are forced to include the same number of cells. This is enforced by the WR2. Figure 1 illustrates table use. .. .. .. .. .. .. figures ifctable image1.gif Figure 1 Table use Figure 2 depicts how tables were structured prior to IFC4. .. .. .. .. .. .. figures ifctable image2.gif Figure 2 Table use alternative HISTORY New entity in IFC1.5. .change ifc2x4 IFC4 CHANGE Columns attribute added. bSI Documentation"
#:IFC.xml:44707
msgid "IfcTable_Rows"
msgstr "Rows"
msgid "IfcTable_Rows_DEFINITION"
msgstr "Rows"
#:IFC.xml:44720
msgid "IfcTable_Columns"
msgstr "Columns"
msgid "IfcTable_Columns_DEFINITION"
msgstr "Columns"
#:IFC.xml:44686
msgid "IfcTable_Name"
msgstr "Name"
msgid "IfcTable_Name_DEFINITION"
msgstr ""
#:IFC.xml:44691
msgid "IfcTable_NumberOfCellsInRow"
msgstr "NumberOfCellsInRow"
msgid "IfcTable_NumberOfCellsInRow_DEFINITION"
msgstr "The number of cells in each row, this complies to the number of columns in a table. See WR2 that ensures that each row has the same number of cells. The actual value is derived from the first member of the Rows list."
#:IFC.xml:44696
msgid "IfcTable_NumberOfHeadings"
msgstr "NumberOfHeadings"
msgid "IfcTable_NumberOfHeadings_DEFINITION"
msgstr "The number of headings in a table. This is restricted by WR3 to max. one."
#:IFC.xml:44701
msgid "IfcTable_NumberOfDataRows"
msgstr "NumberOfDataRows"
msgid "IfcTable_NumberOfDataRows_DEFINITION"
msgstr "The number of rows in a table that contains data, i.e. total number of rows minus number of heading rows in table."
#:IFC.xml:44733
msgid "IfcTableColumn"
msgstr "IfcTableColumn"
msgid "IfcTableColumn_DEFINITION"
msgstr "An [[IfcTableColumn]] is a data structure that captures column information for use in an [[IfcTable]] . Each instance defines the identifier, name, description, and units of measure that are applicable to the columnar data associated with the [[IfcTableRow]] objects. The use of [[IfcTableColumn]] supersedes the IsHeading flag associated with [[IfcTableRow]] . HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:2725
msgid "IfcTableColumn_ReferencePath"
msgstr "ReferencePath"
msgid "IfcTableColumn_ReferencePath_DEFINITION"
msgstr "ReferencePath"
#:IFC.xml:44734
msgid "IfcTableColumn_Identifier"
msgstr "Identifier"
msgid "IfcTableColumn_Identifier_DEFINITION"
msgstr "The Identifier identifies the column within the table. If provided, it must be unique within the table. Columns may be cross referenced across multiple tables by sharing the same column identifier."
#:IFC.xml:44739
msgid "IfcTableColumn_Name"
msgstr "Name"
msgid "IfcTableColumn_Name_DEFINITION"
msgstr "The Name is a human readable caption for the table column. It is not necessarilly unique."
#:IFC.xml:44744
msgid "IfcTableColumn_Description"
msgstr "Description"
msgid "IfcTableColumn_Description_DEFINITION"
msgstr "The Description provides human readable text describing the table column."
#:IFC.xml:44749
msgid "IfcTableColumn_Unit"
msgstr "Unit"
msgid "IfcTableColumn_Unit_DEFINITION"
msgstr "The Unit indicates the unit of measure to be used for this column s data. If not provided, then project default units are assumed. If ReferencePath is provided, the the unit must be of the same measure as the referenced attribute."
#:IFC.xml:44755
msgid "IfcTableRow"
msgstr "IfcTableRow"
msgid "IfcTableRow_DEFINITION"
msgstr "[[IfcTableRow]] contains data for a single row within an [[IfcTable]] . Limitation For backward compatibility, all [[IfcTableRow]] objects referenced by an [[IfcTable]] shall have the same number of Row Cells. The actual number of Cells shall be taken from the number of cells of the first [[IfcTableRow]] for that table. The number of Cells is calculated by the derived attribute NumberOfCellsInRow in the associated [[IfcTable]] . NOTE The attribute IsHeading exists for backward compatibility. [[IfcTableColumn]] should be used instead beginning with IFC4. Figure 337 illustrates table row use. Figure 337 Table row use Figure 338 depicts how table rows were structured prior to IFC4 with the use of the IsHeading flag. Note that the use of the [[IfcTableColumn]] constructs should be used instead of the IsHeading flag which remains for backward compatibility only . Figure 338 Table row use alternative HISTORY New entity in IFC1.5. bSI Documentation"
#:IFC.xml:44756
msgid "IfcTableRow_RowCells"
msgstr "RowCells"
msgid "IfcTableRow_RowCells_DEFINITION"
msgstr "The data value of the table cell.."
#:IFC.xml:44761
msgid "IfcTableRow_IsHeading"
msgstr "IsHeading"
msgid "IfcTableRow_IsHeading_DEFINITION"
msgstr "Flag which identifies if the row is a heading row or a row which contains row values. X 0D NOTE If the row is a heading, the flag takes the value TRUE."
#:IFC.xml:44767
msgid "IfcGloballyUniqueId"
msgstr "IfcGloballyUniqueId"
msgid "IfcGloballyUniqueId_DEFINITION"
msgstr "An [[IfcGloballyUniqueId]] holds an encoded string identifier that is used to uniquely identify an IFC object. An [[IfcGloballyUniqueId]] is a Globally Unique Identifier GUID which is an auto generated 128 bit number. Since this identifier is required for all IFC object instances, it is desirable to compress it to reduce overhead. The encoding of the base 64 character set is shown below 1 2 3 4 5 6 X 09 X 09 0123456789012345678901234567890123456789012345678901234567890123 X 09 X 09 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz The resulting string is a fixed 22 character length string to be exchanged within the IFC exchange file structure. NOTE Refer to the BuildingSMART website www.buildingsmart tech.org http www.buildingsmart tech.org for more information and sample encoding algorithms. HISTORY New type in IFC1.5.1. bSI Documentation"