Did you search the forum for similar topics?

https://qelectrotech.org/forum/viewtopi … 220#p21220

The translations for titleblocks have to be done in the same way as for elements:
The author of a titleblock has to take care of the translations...

According to your screenshots I translated the items of available titleblocks to Chinese and uploaded them to github-repository of QET.
They will therefore be available in next release of 0.100-dev - version of QElectroTech.


Addendum:
This is a great opportunity for you to contribute to QET-project:
As a native speaker you could proofread/correct the texts in the titleblocks...

Texts in titleblocks are missing for Chinese language!
When I look at the source of default titleblock, there is no Chinese:

<titleblocktemplate name="default">
    <information></information>
    <logos/>
    <grid cols="t22%;r100%;t22%;" rows="25;25;">
        <field valign="center" row="0" hadjust="true" col="0" name="author" displaylabel="true" align="left">
            <value>
                <translation lang="en">%author</translation>
            </value>
            <label>
                <translation lang="ar">المؤلف</translation>
                <translation lang="ca">Autor</translation>
                <translation lang="cs">Autor</translation>
                <translation lang="da">Forfatter</translation>
                <translation lang="de">Autor</translation>
                <translation lang="el">Σχεδίαση</translation>
                <translation lang="en">Author</translation>
                <translation lang="es">Autor</translation>
                <translation lang="fr">Auteur</translation>
                <translation lang="hr">Autor</translation>
                <translation lang="it">Autore</translation>
                <translation lang="pl">Autor</translation>
                <translation lang="pt">Autor</translation>
                <translation lang="pt_BR">Autor</translation>
                <translation lang="ro">Autor</translation>
                <translation lang="ru">Автор</translation>
            </label>
        </field>
        <field valign="center" rowspan="1" row="0" hadjust="true" col="1" name="title" displaylabel="false" align="center">
            <value>
                <translation lang="en">%title</translation>
            </value>
            <label>
                <translation lang="ar">عنوان</translation>
                <translation lang="ca">Títol</translation>
                <translation lang="cs">Název</translation>
                <translation lang="da">Titel</translation>
                <translation lang="de">Titel</translation>
                <translation lang="en">Title</translation>
                <translation lang="es">Título</translation>
                <translation lang="fr">Titre</translation>
                <translation lang="hr">Naslov</translation>
                <translation lang="it">Titolo</translation>
                <translation lang="pl">Tytuł</translation>
                <translation lang="pt_BR">Título</translation>
                <translation lang="pt">Título</translation>
                <translation lang="ro">Titlu</translation>
                <translation lang="ru">Название</translation>
            </label>
        </field>
        <field valign="center" row="0" hadjust="true" col="2" name="file" displaylabel="true" align="left">
            <value>
                <translation lang="en">%filename</translation>
            </value>
            <label>
                <translation lang="ar">ملف</translation>
                <translation lang="ca">Fitxer</translation>
                <translation lang="cs">Soubor</translation>
                <translation lang="da">Filnavn</translation>
                <translation lang="de">Datei</translation>
                <translation lang="el">Αρχείο</translation>
                <translation lang="en">File</translation>
                <translation lang="es">Archivo</translation>
                <translation lang="fr">Fichier</translation>
                <translation lang="hr">Datoteka</translation>
                <translation lang="it">File</translation>
                <translation lang="pl">Plik</translation>
                <translation lang="pt_BR">Arquivo</translation>
                <translation lang="pt">Ficheiro</translation>
                <translation lang="ro">Fisier</translation>
                <translation lang="ru">Файл</translation>
            </label>
        </field>
        <field valign="center" row="1" hadjust="true" col="0" name="date" displaylabel="true" align="left">
            <value>
                <translation lang="en">%date</translation>
            </value>
            <label>
                <translation lang="ar">تاريخ</translation>
                <translation lang="ca">Data</translation>
                <translation lang="cs">Datum</translation>
                <translation lang="da">Dato</translation>
                <translation lang="de">Datum</translation>
                <translation lang="el">Ημ/νία</translation>
                <translation lang="en">Date</translation>
                <translation lang="es">Fecha</translation>
                <translation lang="fr">Date</translation>
                <translation lang="hr">Datum</translation>
                <translation lang="it">Data</translation>
                <translation lang="pl">Data</translation>
                <translation lang="pt_BR">Data</translation>
                <translation lang="pt">Data</translation>
                <translation lang="ro">Data</translation>
                <translation lang="ru">Дата</translation>
            </label>
        </field>
        <field valign="center" row="1" hadjust="true" col="2" name="folio" displaylabel="true" align="left">
            <value>
                <translation lang="en">%folio</translation>
            </value>
            <label>
                <translation lang="ar">صفحة</translation>
                <translation lang="ca">Folio</translation>
                <translation lang="cs">Folio</translation>
                <translation lang="da">Ark</translation>
                <translation lang="de">Seite</translation>
                <translation lang="el">Σελίδα</translation>
                <translation lang="en">Folio</translation>
                <translation lang="es">Folio</translation>
                <translation lang="fr">Folio</translation>
                <translation lang="hr">List</translation>
                <translation lang="it">Foglio</translation>
                <translation lang="pl">Arkusz</translation>
                <translation lang="pt_BR">Folha</translation>
                <translation lang="pt">Folha</translation>
                <translation lang="ro">Pagina</translation>
                <translation lang="ru">Фолио</translation>
            </label>
        </field>
    </grid>
</titleblocktemplate>

I didn't look at the QET-Sources yet, where to find the position of missing language.
But as a workaround you can translate the missing texts in your template by hand...

Why?
What is wrong?

I only see that you use different titleblocks.

LievenC wrote:

(...) the terminal block shows the extra terminals but the text is missing
if I take the terminal block from imported elements it shows the texts

same behavior here.

LievenC wrote:

what goes wrong?

(How) is this described in docu of plugin?

bisherfisher73 wrote:

Hi there, (...)

This seems to be a post by an "intelligence" that isn't well informed!
The "tb" in qet_tb_generator stands for terminal-block.
As old as the quoted post, that's how old the python-versions suggested here...
And: QET itself does not use python! It calls executable binaries!

107

(7 replies, posted in Code)

Hej elevatormind,

haven't heard from you in a while, are you okay?

Could you please create a PR for your additions to the fonts?
Then we could finalize that topic from here.
I have already adjusted the tabs for the licenses locally: All licenses are grouped in one tab and can be selected for viewing via ComboBox.
But that only makes sense to upload once the fonts are available.
And the customized element collection is also waiting to be activated: Only the fonts are missing...

Didn't the tutorials say, that scaling of Elements is only possible in Element-Editor?

Mark the graphical primitives (at least two!) with the mouse and then you can pull at the edges.

The other possibility to scale elements with QET 0.100-dev: QET_ElementScaler
Use forum-search to find out how!

please also notice the correct writing: "qet_labels.xml"

Did you search the forum for "qet_labels.xml"?

I guess: No!

There you find a thread "Autonummerierung" with some helpful hints in the latest posts.

"Network-share" is a very old issue.
You need to search the forum for posts of "Scorpio810": I know he mentioned this several times, but at the moment I can't recall the solution.
His native language is French, so it could be an advantage for you!  nomicons/wink

Try the same thing in the user collection. It could be that this detail with qet_labels.xml does not work as planned with the company collection.
Or try using a local drive instead of a network drive for the company collection for a test...

QElectroTech uses the RichText-Editor from Qt for Text-Fields.

"border-radius" is supported by plain html / css but not in RichText-Editor of Qt:
See here: https://doc.qt.io/qt-6/richtext-html-subset.html

As a workaround you may create an element with a rounded rect, place it in diagram and place a free text above it in diagram-editor...

Now I guess I know what you mean:

For terminals no additional properties can be added in element-editor, so in diagram-editor these edit-fields are also not visible.
If you choose a "simple" element, all properties are available also in diagram-editor.
see attachment.

When I recall correctly, there was no change to that behavior recently...

galexis wrote:

Yes, it's possible, but on this version. It's impossible to set properties like  machine, localisation

Can not confirm: Everything can be entered here to the edit-fields. See attachment.

It's the version from Package qelectrotech-0.100.0+git8440-x86-win64-readytouse.7z

QElectroTech V 0.100.0-dev
Compilation: GCC 13.3.0
Built with Qt 5.15.16 - x86_64 - Date : Mar 26 2025 : 12:21:06
Run with Qt 5.15.16 using 2 thread(s)

Wovon ist das ein Screenshot? Vom pdf?
Es wäre absolut hilfreich gewesen, wenn Du das entsprechende Element auch mit angehängt hättest: So kann ich nur Vermutungen anstellen.
Für mich sieht es so aus, daß das Terminal nicht zentriert im Kreis platziert ist. Aber: Nur eine Vermutung!

Kellermorph wrote:

In DXF ist es ja masstabsgetreu. Wird das so übernommen?

Wo kein Maßstab ist, kann keiner übernommen werden: QET enthält keinen Maßstab!

Wir konnten vadoola, den aktuellen Entwickler von dxf2elmt, aber davon überzeugen, auch den Faktor 1mm in real zu 2 px im Element zu verwenden, wenn im dxf eine Bemaßung drin ist!

Wer also die aktuelle Version dxf2elmt von vadoola verwendet, nutzt den Faktor 1mm -> 2 px.

Eine der letzten Versionen gibt's in diesem Thread: https://qelectrotech.org/forum/viewtopi … 123#p21123

galexis wrote:

Properties Machine, localisation have disappeared. Normal ?

In one version at the beginning of February, we incorrectly removed empty properties from the project. This has been fixed in the following version. Unfortunately, this does not bring back the removed properties. They have to be entered again. Sorry for that!
Is it possible that you used this version on the project?

Wie lange hast Du gesucht, um den Knopf nicht zu finden?

Kopieren und einfügen des Textes in einen Online-Übersetzer geht aber auch: en <-> de funktioniert meistens recht gut!

121

(209 replies, posted in Import DXF)

Hello vadoola,

the file pxc_2700975_11_00_ILC-171-ETH-2TX_2D.dxf from Phoenix Contact seems to be a real challenge!
When converting exploded drawing from LibreCAD, the controller is found outside the drawing-area of the A3-sheet.
It is (of course) copyrighted, so no re-distribution here: --> Downloads --> Technische Zeichnung

122

(3 replies, posted in Import DXF)

BAXTERH2000 wrote:

j ai qeletrotech 1.00

surely not: Menu -> Help -> About QElectroTech -> Tab "Version"


BAXTERH2000 wrote:

lorsque je tente une conversion je me retrouve avec un fichier .elm alors que je voudrais avoir un .qet quelq'un peut il m'aider

Reading helps!
Cite from QET - Homepage: 

Dxf2elmt is CLI program which can convert .dxf files into .elmt files.

and:

DXFtoQET : Element DXF Converter
The converter element is a small utility that converts a DXF element to a elmt element.


Create a new QET-Project, place the converted element to the folio and save the file.
Then you have a *.qet - file!

schaumermal wrote:

gibt es hier eine Möglichkeit das gezeichnete (zu große) "Bauteil" Maßstabgetreu zu verkleinern (...)?

Nachtrag:
Du hast nicht geschrieben, welche QElectroTech-Version Du benutzt.

In QET 0.100-dev gibt es im Element-Editor die Möglichkeit, das Kommandozeilen-Tool "QET_ElementScaler" aufzurufen, das ein bestehendes Element gleichmäßig in alle Richtungen skalieren kann. Dabei werden selbstverständlich auch die Beschriftungen entsprechend angepasst.

Dazu gibt es hier im Forum auch schon diverse Fragen und Antworten.

124

(2 replies, posted in Code)

Hallo Achim,

achim wrote:

Wenn Sie es möchten, mach ich einen Pullrequest.

wir können gerne beim "Du" bleiben!  nomicons/wink
Ist so üblich im Forum.

Wir müssen aufpassen, daß uns nicht irgendwann die Tastenkombinationen ausgehen.
Im Moment sehe ich aber keinen Grund, Deinen Patch zurückzuweisen:
Erstelle doch einen PR!

Hallo Leidender!

Kurze Antwort:
Geht nicht!

Für die etwas längere Antwort solltest Du Deine Englisch-Kenntnisse auffrischen, oder einen Online-Übersetzer nutzen:
https://qelectrotech.org/forum/viewtopi … 437#p18437
(Bitte nur den verlinkten Post lesen: die folgenden Posts basieren auf "merkwürdigen" Annahmen.)

Könnte mir eigentlich 'nen Textbaustein dafür machen, so häufig wie hier nach Maßstab bzw scale gefragt wird...
Die Forum-Suche ist auch so schlecht zu finden!  nomicons/wink

Du kannst nur dafür sorgen, daß Deine Elemente untereinander den gleichen Maßstab haben, damit die in Relation passen.
Als guter Wert, den Du ja auch schon bei den LS gefunden hast geht: 1mm = 2px im Element-Editor.