X-Git-Url: http://git.salome-platform.org/gitweb/?a=blobdiff_plain;f=src%2FSMESHGUI%2FSMESH_msg_en.ts;h=fcac5cfe766687640b336103ca6921f80671cc10;hb=b54385ddd41b61114e7d1088048f2f1131c30f1d;hp=90a784488f3c68750d009cfbf6a69efaed4ca936;hpb=5e46af59684e7cdf480e523e46c5e1b5dfc9ee12;p=modules%2Fsmesh.git
diff --git a/src/SMESHGUI/SMESH_msg_en.ts b/src/SMESHGUI/SMESH_msg_en.ts
index 90a784488..fcac5cfe7 100644
--- a/src/SMESHGUI/SMESH_msg_en.ts
+++ b/src/SMESHGUI/SMESH_msg_en.ts
@@ -340,34 +340,6 @@
Construct Group
-
-
- Uniform refinement
-
-
-
- Adaptation with HOMARD
-
-
-
- New case for adaptation with HOMARD
-
-
-
- Existing case
-
-
-
- New iteration
-
-
-
- Compute
-
-
-
- Compute and publish
- Remesh with MG_Adapt
@@ -458,7 +430,7 @@
- local
+ Local
@@ -478,12 +450,20 @@
- size map definition
+ Size map definitionAdvanced Options
+
+
+ Adaptation succeeded.
+
+
+
+ Adaptation failed.
+ Convert to/from quadratic
@@ -3057,38 +3037,6 @@ Check algorithm documentation for supported geometry
None
-
-
- Publication of meshes with HOMARD
-
-
-
- IN mesh
-
-
-
- OUT mesh
-
-
-
- A YACS schema with HOMARD
-
-
-
- Maximal number of iterations
-
-
-
- Maximal number of nodes
-
-
-
- Maximal number of elements
-
-
-
- Test type for a YACS schema with HOMARD
- Adaptation with MG-Adapt
@@ -3372,38 +3320,6 @@ Use Display Entity menu command to show them.
Construct Group
-
-
- Uniform refinement
-
-
-
- Refinement with HOMARD
-
-
-
- Creation of a new case for adaptation with HOMARD
-
-
-
- Creation of a new case: pursuit of a stored iteration
-
-
-
- Creation of a next iteration
-
-
-
- Compute the refinement
-
-
-
- Compute the refinement and publish the final mesh
-
-
-
- Edit
- Remesh with MG_Adapt
@@ -4112,30 +4028,6 @@ Use Display Entity menu command to show them.
Construct Group
-
-
- Uniform refinement
-
-
-
- New case
-
-
-
- Existing case
-
-
-
- New iteration
-
-
-
- Compute
-
-
-
- Compute and publish
- Remesh with MG_Adapt
@@ -7040,7 +6932,7 @@ select mesh or sub-mesh and try again
-The assigned algorithm has the same priority as one assigned to an
+The assigned algorithm has the same priority as one assigned to an
adjacent sub-mesh, hence it's undefined which algorithm to use for
meshing boundary shared by two sub-meshes. Would you like to set
the order of sub-mesh computation?