doc/standards_fr.po
author Andrey Skvortsov <andrej.skvortzov@gmail.com>
Fri, 24 Aug 2018 13:41:43 +0300
changeset 2297 96ca6b056c55
parent 811 66a8812457d6
permissions -rw-r--r--
Proper fix for error 'object has no attribute 'getSlave' in EtherCAT extension

traceback:
File "/home/developer/WorkData/PLC/beremiz/beremiz/IDEFrame.py", line 1433, in OnPouSelectedChanged
window.RefreshView()
File "/home/developer/WorkData/PLC/beremiz/beremiz/etherlab/ConfigEditor.py", line 837, in RefreshView
self.RefreshProcessVariables()
File "/home/developer/WorkData/PLC/beremiz/beremiz/etherlab/ConfigEditor.py", line 886, in RefreshProcessVariables
slaves = self.Controler.GetSlaves(**self.CurrentNodesFilter)
File "/home/developer/WorkData/PLC/beremiz/beremiz/etherlab/EthercatMaster.py", line 341, in GetSlaves
for slave in self.Config.getConfig().getSlave():
<type 'exceptions.AttributeError'>:_'lxml.etree._Element'_object_has_no_attribute_'getSlave'

Steps to reproduce problem:

- Add new EtherCAT master
- Add new EthercatNode to the master
- double click on


Revert commit "Dirty fix for error '_object_has_no_attribute_'getSlave' in EtherCAT extension"
[a3ac46366b86a0b237dac93be6b2281ac70b98a8].

The problem was that XML elements (proxy object) in some cases were created using custom XML
classes constructors and lxml.etree.Element() call and live python
patching. This causes that lxml backend doesn't know that custom python class
should be used for these XML elements.
Proxy object can be move/deleted and recreated by lxml
backend at any point in time or this can be done in python by copy/deepcopy operations.
If this happens, then newly created
proxy elements are using default class lxml.etree._Element. And all
custom functionality is lost.

All created XML elements should be always created through corresponding
parser and class lookup callback done by lxml backend.
It's described in more details in lxml documentation:
https://lxml.de/element_classes.html
# SOME DESCRIPTIVE TITLE.
# Copyright (C) is 21st century inquisition
# This file is distributed under the same license as the Beremiz package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: Beremiz 1.1\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2012-09-08 00:41\n"
"PO-Revision-Date: 2012-09-07 14:32+0100\n"
"Last-Translator: \n"
"Language-Team: \n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Poedit-Language: French\n"
"X-Poedit-Country: FRANCE\n"
"X-Poedit-SourceCharset: utf-8\n"

# 344fd0acb601413ab6ca95d448467f30
#: ../../standards.rst:2
msgid "IEC 61131-3"
msgstr "CEI 61131-3"

# 805a294642fa45d6bde054a5cbaebff4
#: ../../standards.rst:4
msgid ""
"IEC-61131 is a normative document provided by the standards organization IEC "
"(International Electrotechnical Commission) and describing a standard for "
"implementing programmable controllers."
msgstr ""
"La CEI 61131 est une norme industrielle de la Commission électrotechnique "
"internationale (CEI) définissant des langages de programmation à utiliser "
"pour les automates programmables."

# 39146aa0d8a64bec958bbf6f03efc336
#: ../../standards.rst:9
msgid ""
"The part 3 of this document (commonly named IEC 61131-3) specifies syntax "
"and semantics for programming language for programmable controllers. Beremiz "
"implements all the languages described in this document."
msgstr ""
"La troisième partie de ce document, appelé CEI 61131-3, spécifie la syntaxe "
"et la sémantique des langages de programmation des automates. Beremiz "
"implémente l'ensemble des langages décrits dans ce document."

# 02dd6ad924064d3db0b12c72bce36f8c
#: ../../standards.rst:14
msgid "http://www.iec.eu"
msgstr "http://www.iec.eu"

# 876bae27356140f997ac52f76f873976
#: ../../standards.rst:17
msgid "PLCopen TC6"
msgstr "PLCopen TC6"

# 0af4d2fd04ff43de81c06498a0c43180
#: ../../standards.rst:19
msgid ""
"PLCopen is a vendor- and product-independent worldwide association defining "
"international standards for various topics related to control programming. "
"For this purpose, PLCopen has 6 technical committees."
msgstr ""

# 2dcfeef2c4f344bca696fbd36f0bcf3e
#: ../../standards.rst:24
msgid ""
"The goal of the sixth committee (TC6) is to define a standard file format, "
"based on XML, for exchanging programmables controllers programmed using IEC "
"61131-3 languages. Beremiz uses this file format for saving the PLC programs "
"of projects."
msgstr ""

# 69d997c95b6b4a728b1129c0ec49ed94
#: ../../standards.rst:30
msgid "http://www.plcopen.org"
msgstr "http://www.plcopen.org"