QUCS nomenclature for "Relays" in the ".sch" file is "Relais" - Typo?

Question

QUCS nomenclature for "Relays" in the ".sch" file is "Relais" - Typo?

Circa-Tree opened this issue 3 years ago · comments

"Relays" in the schematic diagram are called "Relais" in the ".sch" file - Typo?

Relays in the schematic diagram are called "Relais" in the .sch file, which is not consistent naming, and is probably a typo.
Not helpful, when working at the sch file level (using text editor).

Relais in French can mean hotel, or staging post, but when using the english version of the program, it is expectable that the english word (in the .sch file) is used to represent the english component name.

felix · Answer 1 · Fri Oct 22 2021 00:29:03 GMT+0800 (China Standard Time)

The real issue is, components and their names are hardwired, making customisation difficult. Nobody is maintaining or developing legacy Qucs at the moment, but feel free to do so.

We need to leave the old design behind and move on e.g. to component libraries. In "modular Qucs" you can have any number of Relay, Relais, Switch components and/or define aliases. But modular Qucs not ready yet. Choose your pick.

but when using the english version

Qucs Schematic files are not localised or localisable. This is an interesting idea. Still I have not yet seen anybody doing it. Do you have a reference?

NB: Relais happens to be the German spelling, and is not a typo.

Circa-Tree · Answer 2 · Fri Oct 22 2021 11:31:22 GMT+0800 (China Standard Time)

Looked for "modular QUCS" and only found QUC-S which seems to a module for use in "modular QUCS".

Is there a link for "modular QUCS" ?
If it is possible to install modular QUCS along side original QUCS, without causing problems then it can be conveniently trialled.

Not seen a reference to localization of QUCS, but there are users from a diversity of languages, who probably represent a small proportion of potential users in each of those languages.

Alias component names will be great (as might other parameters) as the analysis engine can be used for many different 'systems' (other than electronic, especially if it is possible to easily switch between alias modes/languages/'field of study'.

felix · Answer 3 · Fri Oct 22 2021 15:04:23 GMT+0800 (China Standard Time)

On Thu, Oct 21, 2021 at 08:31:32PM -0700, Circa-Tree wrote: Is there a link for "modular QUCS" ?

Clone qucs and checkout the "modular" branch.

If it is possible to install modular QUCS along side original QUCS, without causing problems then it can be conveniently trialled.

Modular Qucs does not require installation for running. In the long run, e.g. if you want to develop extension modules, better install it. But you can choose a prefix, and it should not collide with anything. Fingers crossed.

Not seen a reference to localization of QUCS, [..]

Not localisation of Qucs. I meant localisation of circuit models or schematics. I don't think we should try and invent fancy new stuff, before we have a functioning baseline.

Circa-Tree · Answer 4 · Mon Oct 25 2021 18:29:22 GMT+0800 (China Standard Time)

Installing Modular QUCS -

Modular Qucs does not require installation for running.

In the long run, e.g. if you want to develop extension modules, better install it.

But you can choose a prefix, and it should not collide with anything.

I clicked on the Code tab (top right), selected branch 'modular', downloaded the zip file, and extracted. Looked in "Main" folder, and some others but did not see any files that looked like they might be run as they were.

So what file do I need to run? or (later) , for testing trialling - what do I need to install? - hopefully without needing to install/setup a complete development environment.

If Modular QUCS is where development of QUCS is heading towards, then awareness of this new version could be promoted through the "About QUCS" section of the "Help" menu in QUCS, or have an "About Modular QUCS" section in the help. Including how to find out more and get involved - reach the users directly. "About - the future".

Localisation - if this is left till later, then it will require retrospective editing of items that get designed in the meantime, and the updating may not happen, or happen slowly., or those items will be outdated.
If localisation is available, then designers can decide to use it or not, but at least there will be compatibility. Other people can do translations (of a simple list) at any future stage (or concurrently along with the item designers).

felix · Answer 5 · Mon Oct 25 2021 18:59:05 GMT+0800 (China Standard Time)

On Mon, Oct 25, 2021 at 03:29:32AM -0700, Circa-Tree wrote: I clicked on the Code tab (top right), selected branch 'modular', downloaded the zip file, and extracted. Looked in "Main" folder, and some others but did not see any files that looked like they might be run as they were. So what file do I need to run? or (later) , for testing trialling - what do I need to install? - hopefully without needing to install/setup a complete development environment.

Perhaps README.md is a suitable resource at this stage. Modular Qucs does not technically depend on anything except a compiler. Clearly, the GUI depends on Qt, and the build system may have references to other stuff that should rather be optional. It's a work in progress.

If Modular QUCS is where development of QUCS is heading towards, then awareness of this new version could be promoted through the "About QUCS" section of the "Help" menu in QUCS, or have an "About Modular QUCS" section in the help. Including how to find out more and get involved - reach the users directly. "About - the future".

If you like the idea, and have time to spend, please campaign for it. My current situation does not admit full involvement. I'm happy to spell out details or give advice, as time permits. Please open more tickets for more specific questions, or use individual threads on the mailing list.