Than you Nuri for quick and well written information 
Nuri wrote:First, i am not sure how all variables in folio properties are intended to be used.
like you did in your screenshot
Then it is like i want it to be already 
Nuri wrote:Do we have some description of the concept/idea?
No, these concepts are pretty new (only in 0.51 devel) and were developped by Davi.
See here for more informations:
forum topic
There is an online manual but it's not finished and it was written for QET v0.4.
For sure, it would be nice to explain the variable concept in the online manual.
That forum topic link do not work...
I like that manual. I think it is well designed and written. It "just" need to be extended and updated... by someone having the time
Do we have some overview of what variables can be used where and when and when they are defined where?
no, not at the moment. If you have some ideas how this could be shown in the GUI, please explain them.
I think we need to integrate in the GUI some URL to the online manual to automatically open in a web browser.
It would be the easiest way to keep informations up to date. But the online manual must be written by some people how can correctly write in english...
I see there are already short explanations here and there where variables can be defined and used.
IMO, you should keep those short explanations there, (make sure they are complete and correct, but short) and every such place link to a chapter that carries full information; beginning by why, concept, how to use by simple example, then a table(?) listing all variables and where they can be set, then listing or explaining where they can be used. And some syntactic how they can be combined, what characters are legal, etc.
It would be good if manual could be installed locally, by distro package or manually downloaded and uncompressed some specific place that works with those links. Not everybody have internet access always.
I also have not understood what a "Reports folio" is
They are the arrows to interrupt a conductor that is continued on another folio. In my opinion, "reports folio" is not a good translation. Some proposals?
Ah. I completely misunderstood that naming. ( To me it sounded like some report that can be generated onto some page. )
Why not use the naming "Sheet referencing" as that is already how the element section is named that contain the linking elements
p, li { white-space: pre-wrap; } Chemin de la collection : common://10_electric/10_allpole/100_sheet_referencing
Chemin dans le système de fichiers : /usr/local/share/qelectrotech/elements/10_electric/10_allpole/100_sheet_referencing
I also have seen them named "ports", "off page connector", "signal flag" and such. I think "port" is short and tells what it is, while "sheet referencing" tells what it does.. so ... "sheet referenced port" tell whole story but is too long... ... whatever, just use *same* name everywhere IMO, and ask whoever set the original name about it before changing from "Sheet referencing".
...To say it short: change "Reports folio" to "Sheet referencing" - few changes, much better to understand.
EDIT: "Label of report folio" -> "Label of Sheet referencing symbols" /EDIT
I am not sure how Folio is intended to be used
by default, QET can only number folio in a continuous way (1, 2, 3, 4...)
If you want something else, you can write the folio number in the field "folio" and check the option "Use labels of folio instead of their ID" in the QET settings window.
OK.
It seems i can also there write a short name for a small part of the system, have that same short name for more than one page, and to differentiate the pages in the inset, i can there use variables directly in that template: %folio-id(%folio-total)
BTW, how do i make the .qet file name show in title blocks?
type it by hand! There is no function that automatically writes the file name in it.
IMO, there should be a variable carrying the file name, and be usable in the title block
I often save many slightly different versions of my work, differentiated only by some number at end of file name.
Both when sketching different design solutions, and/or different ways to divide it onto pages
... and/or using software that crashes 
