From f47c24964db12066d6bf78edda8b1aca5e2ab038 Mon Sep 17 00:00:00 2001 From: eap Date: Fri, 15 Jan 2021 11:57:29 +0300 Subject: [PATCH] Typo-fix by Kunda https://www.salome-platform.org/forum/forum_9/875695368/351290391 --- doc/dev/sphinx/fr/medcalc-userguide-api.rst | 2 +- doc/dev/sphinx/medcalc-userguide-gui.rst | 2 +- doc/tut/addfields/operations.py | 2 +- idl/MEDDataManager.idl | 8 ++++---- src/MEDCalc/cmp/MEDCalculator_i.cxx | 12 ++++++------ src/MEDCalc/test/gui/README.txt | 2 +- .../Test/MEDCouplingMeshFieldFactoryComponent.cxx | 2 +- .../MEDCouplingCorbaSwigTest.py | 2 +- 8 files changed, 16 insertions(+), 16 deletions(-) diff --git a/doc/dev/sphinx/fr/medcalc-userguide-api.rst b/doc/dev/sphinx/fr/medcalc-userguide-api.rst index 45ddab248..dd246eb59 100644 --- a/doc/dev/sphinx/fr/medcalc-userguide-api.rst +++ b/doc/dev/sphinx/fr/medcalc-userguide-api.rst @@ -42,7 +42,7 @@ installed together with this module by the installation process of SALOME. Nevertheless, it is possible for low-weight deployment to install only the MEDMEM library from the source files embedded in the SALOME FIELDS module. Keep in mind that the MEDMEM library is designed to -be a self-consistent library with very few third party softwares (only +be a self-consistent library with very few third party software (only med-file, glibc and mpi typically). In particular, it is strictly independent from the SALOME framework even if it distributed with SALOME for convenience reasons. diff --git a/doc/dev/sphinx/medcalc-userguide-gui.rst b/doc/dev/sphinx/medcalc-userguide-gui.rst index 4e6497af6..d85194a38 100644 --- a/doc/dev/sphinx/medcalc-userguide-gui.rst +++ b/doc/dev/sphinx/medcalc-userguide-gui.rst @@ -650,4 +650,4 @@ The following TUI commands need to work in graphical environment: * ``medcalc.MakeVectorField`` -.. LocalWords: softwares +.. LocalWords: software diff --git a/doc/tut/addfields/operations.py b/doc/tut/addfields/operations.py index eb24e7b5f..0872cf0de 100644 --- a/doc/tut/addfields/operations.py +++ b/doc/tut/addfields/operations.py @@ -73,7 +73,7 @@ p4.setMesh(mesh) result = p3+p4 result.setName("p3+p4") -# We can finally save the result together with the operandes fields +# We can finally save the result together with the operands fields outfilename = "addition.med" MEDLoader.WriteField(outfilename,result,True) MEDLoader.WriteField(outfilename,p3,False) diff --git a/idl/MEDDataManager.idl b/idl/MEDDataManager.idl index 8fa024d34..20596ce5d 100644 --- a/idl/MEDDataManager.idl +++ b/idl/MEDDataManager.idl @@ -45,17 +45,17 @@ module MEDCALC typedef sequence MeshHandlerList; /** - * The Fieldseries is a virtal object that does not exist in the MED + * The Fieldseries is a virtual object that does not exist in the MED * data model (at least in the MEDCoupling data model). It is just a - * point that aggregate a list of fields that relie on the same mesh + * point that aggregates a list of fields that rely on the same mesh * with the same type (the fields in a timeseries differ by their * time step). * * Then you could have a field with no fieldseries associated but * directly associated to a mesh. That is typically the case of - * fields created by MED operations: if you operate tow fields + * fields created by MED operations: if you operate two fields * coming from 2 different timeseries (and relying on the same - * mesh), you obtain a field that can not be associate to the + * mesh), you obtain a field that can not be associated to the * original timeseries. Then this new created field must be directly * associated to its underlying mesh (as defined in the MEDCoupling * data model). diff --git a/src/MEDCalc/cmp/MEDCalculator_i.cxx b/src/MEDCalc/cmp/MEDCalculator_i.cxx index a7b71cabb..d8f4ca7cb 100644 --- a/src/MEDCalc/cmp/MEDCalculator_i.cxx +++ b/src/MEDCalc/cmp/MEDCalculator_i.cxx @@ -59,13 +59,13 @@ MEDCalculator_i::~MEDCalculator_i() MEDCALC::FieldHandler * MEDCalculator_i::add(const MEDCALC::FieldHandler & f1_hdl, const MEDCALC::FieldHandler & f2_hdl) { - // We first check that both operandes share the same mesh id. Note + // We first check that both operands share the same mesh id. Note // that it's not strictly required because the MEDCoupling operation // would raise an exception if the fields does not share the same // mesh support. if ( f1_hdl.meshid != f2_hdl.meshid ) { std::string message = - std::string("ERROR: Mesh ids are different for the field operandes ") + + std::string("ERROR: Mesh ids are different for the field operands ") + std::string(f1_hdl.fieldname) + std::string(" and ") + std::string(f2_hdl.fieldname); throw KERNEL::createSalomeException(message.c_str()); } @@ -103,7 +103,7 @@ MEDCALC::FieldHandler * MEDCalculator_i::add(const MEDCALC::FieldHandler & f1_hd // >>>>>>>>> // _GBO_ We should test here if the iteration and order of the input - // files are identical for both operandes. A convention has to be + // files are identical for both operands. A convention has to be // defined here. By default, we let the iteration and order be // determined by the resulting MEDCouplingFieldDouble instance (see // function addField of the data manager). @@ -126,7 +126,7 @@ MEDCALC::FieldHandler * MEDCalculator_i::sub(const MEDCALC::FieldHandler & f1_hd { if ( f1_hdl.meshid != f2_hdl.meshid ) { std::string message = - std::string("ERROR: Mesh ids are different for the field operandes ") + + std::string("ERROR: Mesh ids are different for the field operands ") + std::string(f1_hdl.fieldname) + std::string(" and ") + std::string(f2_hdl.fieldname); throw KERNEL::createSalomeException(message.c_str()); } @@ -165,7 +165,7 @@ MEDCALC::FieldHandler * MEDCalculator_i::mul(const MEDCALC::FieldHandler & f1_hd { if ( f1_hdl.meshid != f2_hdl.meshid ) { std::string message = - std::string("ERROR: Mesh ids are different for the field operandes ") + + std::string("ERROR: Mesh ids are different for the field operands ") + std::string(f1_hdl.fieldname) + std::string(" and ") + std::string(f2_hdl.fieldname); throw KERNEL::createSalomeException(message.c_str()); } @@ -203,7 +203,7 @@ MEDCALC::FieldHandler * MEDCalculator_i::div(const MEDCALC::FieldHandler & f1_hd { if ( f1_hdl.meshid != f2_hdl.meshid ) { std::string message = - std::string("ERROR: Mesh ids are different for the field operandes ") + + std::string("ERROR: Mesh ids are different for the field operands ") + std::string(f1_hdl.fieldname) + std::string(" and ") + std::string(f2_hdl.fieldname); throw KERNEL::createSalomeException(message.c_str()); } diff --git a/src/MEDCalc/test/gui/README.txt b/src/MEDCalc/test/gui/README.txt index ad68b0df1..b0f15f11a 100644 --- a/src/MEDCalc/test/gui/README.txt +++ b/src/MEDCalc/test/gui/README.txt @@ -5,7 +5,7 @@ Tests based on QtTesting framework from ParaView. Main entry point is test_qttesting.py. Each scenario is described in a XML file and can be recorded directly in the GUI via the "Record test" button. -A scneario must save a final screenshot of the ParaView view in a file located in the temp directory (TODO: review +A scenario must save a final screenshot of the ParaView view in a file located in the temp directory (TODO: review this). This file is compared against a baseline saved in the baselines subdirectory. diff --git a/src/MEDCouplingCorba/Test/MEDCouplingMeshFieldFactoryComponent.cxx b/src/MEDCouplingCorba/Test/MEDCouplingMeshFieldFactoryComponent.cxx index 9a884d897..ca9b21a3e 100644 --- a/src/MEDCouplingCorba/Test/MEDCouplingMeshFieldFactoryComponent.cxx +++ b/src/MEDCouplingCorba/Test/MEDCouplingMeshFieldFactoryComponent.cxx @@ -244,7 +244,7 @@ namespace SALOME_TEST MEDCoupling::MEDCouplingCurveLinearMesh *targetMesh=MEDCoupling::MEDCouplingCurveLinearMesh::New(); targetMesh->setTime(2.3,4,5); targetMesh->setTimeUnit("us"); - targetMesh->setName("Example of Cuve linear mesh"); + targetMesh->setName("Example of Curve linear mesh"); targetMesh->setDescription("buildCLMesh"); MEDCoupling::DataArrayDouble *a1=MEDCoupling::DataArrayDouble::New(); a1->alloc(3*20,1); diff --git a/src/MEDCouplingCorba_Swig/MEDCouplingCorbaSwigTest.py b/src/MEDCouplingCorba_Swig/MEDCouplingCorbaSwigTest.py index c31cd604a..8ecafbcfe 100644 --- a/src/MEDCouplingCorba_Swig/MEDCouplingCorbaSwigTest.py +++ b/src/MEDCouplingCorba_Swig/MEDCouplingCorbaSwigTest.py @@ -194,7 +194,7 @@ class MEDCouplingCorbaServBasicsTest: targetMesh=MEDCouplingCurveLinearMesh(); targetMesh.setTime(2.3,4,5); targetMesh.setTimeUnit("us"); - targetMesh.setName("Example of Cuve linear mesh"); + targetMesh.setName("Example of Curve linear mesh"); targetMesh.setDescription("buildCLMesh"); a1=DataArrayDouble(3*20,1); a1.iota(7.) ; a1.rearrange(3); -- 2.39.2