Dutch translation of the manual

[JoopN]

If I'm going to translate the manual then its not only the manual which has to be translated but also all pictures if there is a part of the menu visible. How are we going to do that? Taking a screenshot is not a problem if you can use the source of the picture, ie download the fcd file, load it into the nationalised version of FidoCadj and make a screenshot. But now the problem where to put in on Github?

[DarwinNE]

Hello, thank you for your intention to translate the manual! Which language are you targeting, in particular?

When I worked on the French and Italian manuals (that now are unfortunately outdated), I used the same pictures and screenshots I took for the English version of the manual. Of course, it would be better to grab new screenshots.

Every resource related to the manual is present here:

https://github.com/DarwinNE/FidoCadJ/tree/master/manual

If you think you will add pictures associated with your translation, you may create a sub-directory of "images".

By the way, I received very few feedbacks about the english version of the manual, the only one I currently maintain. If you spot paragraphs that are not clear or that give obsolete information, do not hesitate to open issues to discuss about them.

Cheers

[JoopN]

I want to translate it to Dutch, don't know how long it will take. Did translate jobs before and it took a few months up to two years for a large manual (100+ pages) with also translating the program. FidoCadj is already translated to Dutch, so it should be an easy task.

[JoopN]

I downloaded the English manual, a LaTex file. What program do you use for maintaining this file? I have jEdit, but I'm not pleased with this package for this job.

[DarwinNE]

I use a standard text editor, with LaTeX syntax highlighting. Textwrangler on macOS, to be more precise. I have an old MacBook Pro as my primary computer. The day I will change my computer I will check BBEdit. On Linux I sometimes use Vim, but I have some troubles memorizing all the shortcuts and commands. I think I might use Vim if I had to develop more often on Linux.

[JoopN]

Thanks, Vim got me moving with a search in the browser. Didn't succeed there, but got a top 12 list for LaTex editors. I'm on a Raspberry Pi so I settled for TEXstudio and I tried a part with translation, so now I have a FidoCadj manual partly English and partly Dutch. Lets see where this end ;-)

[JoopN]

Busy now with translating. I read this; \chapter*{Abstract}

\pdfbookmark[1]{Abstract}{Abstract}

Dit document is de FidoCadJ gebruikershandleiding. Na een korte inleiding over de (part which is already Dutch)

By doing this in this way your bookmark will start with the line "Dit document is de..." and NOT with the head "Abstract". Furthermore the line starts at the first line or top line in your program window, so you don't see what's above or where you are. When I use the bookmark "Abstract" then my expectation is that I will see as first line "Abstract". It can be overcome very easy by setting "\pdfbookmark[1]{Abstract}{Abstract}" (as an example) above "\chapter*{Abstract}". Of course, my opinion and based on how we do things in the Netherlands, don't now how its done in Italy.

[DarwinNE]

Hello, if I have understood well what you mean, I think the problem is indeed the same with the English manual as well. I did not notice that, but indeed I think you are right.

Do not hesitate to correct it and to do a commit and a push request.

Kind regards, D.

[JoopN]

Update.. I am at chapter one, before you think nothing happened, there is a lot which goes before chapter one. In chapter one I had to make some decisions about pictures with examples of old versions. Those have French or Italian in the bar and I decided not to redo it to Dutch. All pictures with actual version are redone with Dutch layout. Doing so I remarked that the translation of Dutch in the program is a little off, so I have to redo that too. Also I have to learn Latex along I proceed in the manual.

[DarwinNE]

That's some very good news!

BTW could you correct the small error about \pdfbookmark in the English version of the manual?

[JoopN]

Yes I can correct the small "errors" in the English version of the manual, but first I want to complete the Dutch translation, after that corrections and may be insert some new parts. With the translation I get deeper and deeper into the program, also I'm busy with designing new electronic test equipment and found out that my math for electronics is a little rusty after 20+ years absence. The problems of 20+ years back are still there, no progress which amazes me.

[JoopN]

I am somewhere in chapter 2, but I got lost in the bars, probably something from old versions. Made pictures en/nl with names how the bars are called. Have to see what happen if pdf is made and if it is in the right place. After that insert it into the English manual.

[JoopN]

You(?) wrote this in the manual (2.1 second part, page 6) "Such changes in the settings become effective after a restart of the application, since it is arguably something that we may want to change every day."

I think you forgot the word "not" between "since it is" and "arguably something", because I have a hard time in believing that users are switching every day or every month or so. This is in my mind once set never touch again. But who knows, may be I have it wrong.

[JoopN]

I want to insert this almost at the beginning of P2;

With it some naming what refers to what, because in the manual some are mixed up.

[DarwinNE]

"Such changes in the settings become effective after a restart of the application, since it is arguably something that we may want to change every day."

Oh, yes, the "not" is definitely missing in the sentence!

[DarwinNE]

I want to insert this almost at the beginning of P2;

I think it is a good idea. If it is not a problem for you, I am adding this picture (slightly modified) to the English version of the manual, too. At the same time I think the picture showing the Metal look and feel is not useful anymore.

[JoopN]

I had made the picture for adding to the English version, but the picture might not be a definitive version, just for me as a reference. I have to do some upgrading in the English manual, this will come along, have to fix some text too. I haven't looked at the setup, don't know if I can change looks in Linux, not important for me at the moment. Things do differ between Apple and the rest of computers, so I don't know if you can keep it to one look, think you have to make more looks.

[JoopN]

I'm constant falling over this error: File `pgf.sty' not found. \usepackage What is it, something special in Apple? Where can I find it, now I can't make pdf or export to html and I want to see how it is going in order to set some things right in the end product, ie tables and pictures on the right place.

[JoopN]

I think it is usefull to make a chapter with how to do with examples and how you get there. What' s your opinion on this?

[DarwinNE]

I'm constant falling over this error: File `pgf.sty' not found. \usepackage

You should have TiKZ/PGF installed in your LaTeX distribution:

https://www.ctan.org/pkg/pgf

It is a pretty common package, it is much probably part of your distribution, but you have to see how to install it. IIRC it may not be included in some "base" install.

I think it is usefull to make a chapter with how to do with examples and how you get there. What' s your opinion on this?

What do you mean, exactly?

[JoopN]

I think it is usefull to make a chapter with how to do with examples and how you get there. What' s your opinion on this?

What do you mean, exactly? Somewhere there is a comment on more examples. Might be interesting to show how to get to something , how to make your own lib, within FidoCadJ or with an ASCII editor. How to start a schematic drawing, add colour to it. Make colours specific for that drawing, next drawing will be again the standard. Show a complete small design. Do something totally different like my setup for furniture for a room. That kind of stuff.

[JoopN]

Op Sat, 25 Jun 2022 14:36:23 -0700 Davide Bucci @.***> schreef:

I'm constant falling over this error: File `pgf.sty' not found. \usepackage

You should have TiKZ/PGF installed in your LaTeX distribution:

https://www.ctan.org/pkg/pgf

It is a pretty common package, it is much probably part of your distribution, but you have to see how to install it. IIRC it may not be included in some "base" install.

Yes, its even installed, only its called probably differently, so I have to adjust TexStudio. Thanks, I now now where to look for.

[JoopN]

Still had problems. Today I decided to use your English manual and that one DOES compile, so that's good news. This means that all dependencies are there on my system. Now I have to look for what's wrong in my translation (so far somewhere chapter two), may be I translated a word too much ;-)

[JoopN]

Sorry for some delay, was work related and it took me 3 months to solve problems. Between I did more tests and the problem was my approach of translating, ie some parts here, some parts there with still the English parts present. All has to do that a strait translation gives "broken" Dutch, but not the way we use it daily. I saved the file for copy/past already translated parts. At some point I deleted all and copy back the English part. So that gives a document part Dutch part English. The good news then is that this document DOES compile. Way to go now is to translate a part and try to compile it, if success go on if error try to find out what did go wrong. I think that this approach will speed up things.

[JoopN]

I'm almost at chapter 3... Lots of fights with Latex in order to get things where I wanted it, not full 100%, but satisfying enough. An other thing which doesn't go at the moment is to change the locale from English to Dutch in the document. Something with Babel, but where it comes from in my system I don't know. Linux isn't friendly in locating files, even so with search.

[JoopN]

Okay, I have now a manual in Dutch, say version 0. How to proceed? I want that you take a look at it because I changed a few things. One of those things is that issue 16 is addressed. Also not all things are up to present version of FidoCadJ. That's why version 0. Its some kind of preview. I know that you probably don't speak or read Dutch, but you can evaluate the build, way of presenting, if you agree with the examples shown and you can even try some picture references which I fixed. I'm going to find out if I can do the same for tables, for now that's a no go in Latex. Another reason for version 0 is that I didn't have everything, so I could not set Babel right with Dutch. I did download and installed the necessary files, but setting the file strait is something else if I have to believe the comments on the net about this subject. So please get in contact.

[JoopN]

Hello Davide,

Please go to the issues page in Github. Manual translated to Dutch, version 0. Want to know how to proceed. One of the things is that I want that you see it end walk through the document, even if you don't read or speak Dutch you can see the build, the way its done. Issue 16 is addressed, Not all is up to date with present version of FidoCadJ ,so I want to address that too. I have to look after the pictures, some might need an upgrade or to Dutch or to present version of FidoCadJ. If you like it I can do the English manual too, so that both manuals have the same topics.

regards, Joop

fixed Babel issues.

[DarwinNE]

Hi @JoopN great work! What you can do is to prepare a pull request only for the Dutch manual. I will review it and if it is OK, I will merge it. After having finished the work on the Dutch manual, we may review the English manual, too, but everything in its own time.

Cheers, D.

[JoopN]

Hi @JoopN great work! What you can do is to prepare a pull request only for the Dutch manual

Cheers, D.

Okay, the only thing I get is something with compare one with the other. But there is nothing to compare and in this case its brand new. No button with upload or so. I understand you have to give info what it is, why, how, changes with the English manual besides the translation and so on. All no problem, but first I have to get that document up. Also complained with Github, but probably they don't see it. Help...

[JoopN]

I hope you have received the Dutch manual, don't hear anything. I'm busy with a new translation and with it I found out that I have to fix some parts in the Dutch manual too. Due to fine arrangements of the float system of Latex ;-( . Found also some typo's in part 1 and some words which seems forgotten (Thank you Google ;-(). Also some pictures have too much text... But after all, its open source, so I fix it. No, I'm not busy with the English one, you want that I wait with that... (for some reason?)

[DarwinNE]

Hello, I haven't seen any pull request. Did you send me the manual with another way? If you have done it, the pull request is the way you can show code that I can possibly correct. Do not send anything by email, for instance. My public address filters out automatically all emails containing attachments. I will not include anything in the repository without a pull request. Cheers, D.

[JoopN]

No, for my try with pull request see above. Did send the manual with the answer on an email from you. So that's gone? As before, pull request seems not to work for me. Github is shortsighted with only Windows and Mac. I only get that I can compare a with b, nothing which tells me how to upload. That's what I get with the option pull request. So help..

[JoopN]

Here is the pdf, I want that you look at it first, say what you think about it. Manual-nl.pdf deleted, is coming back in an other way.

[DarwinNE]

It looks very nice! Amazing work.

[JoopN]

I found a solution for text and pictures in the part about the pcb, this works too with the Dutch translation, but have to upgrade it, now busy with the German translation. I also made a repository, but still busy with security. Is it possible to do a pull reguest from a hidden one?

[DarwinNE]

I don't know. I think you must fork of the FidoCadJ project. I think this page should give you the instructions: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork

[JoopN]

I see different numbers with the polylinie. What is the maximum of points you can use, 256, 5000? Are there more of such fixes in the software but not noted in the manual(s)?

[DarwinNE]

Good point. Leave me a day or two and I'll try to check.

[JoopN]

In the explanation of "Natural cubic spline" is a reference to the html page http://www.cse.unsw.edu.au/~lambert/splines/natcubic.html. I checked, but this site will give a 404 error, which means that the site is no longer there. For now I removed the reference until you can point me to a new location.

[DarwinNE]

I checked the code. The maximum number of tokens recognized in a line of FidoCadJ is 10000: https://github.com/DarwinNE/FidoCadJ/blob/ec920a1a22b004ffaca2fc8abacb0bf80da731dd/src/net/sourceforge/fidocadj/circuit/controllers/ParserActions.java#L48 Therefore, for a spline having the following form:

CV aa x1 y1 x2 y2 ... l 
CP aa x1 y1 x2 y2 ... l

you have to count (10000-3)/2 that rounded gives 4998 vertex.

Unfortunately, it is true that the page about the natural splines has vanished. Maybe a workaround is to use the Internet Wayback Machine:

https://web.archive.org/web/20141224163714/http://www.cse.unsw.edu.au/~lambert/splines

I remember I contacted the author to ask for permission to use his code, that he granted me.

[JoopN]

Unfortunately, it is true that the page about the natural splines has vanished. Maybe a workaround is to use the Internet Wayback Machine:

https://web.archive.org/web/20141224163714/http://www.cse.unsw.edu.au/~lambert/splines

I remember I contacted the author to ask for permission to use his code, that he granted me.

Thank you for the number of tokens. The website on archive.org is a nice menu, but all pages are empty and the pointer to the original website does not work due to the 404 error. So in the end we are empty handed.

[DarwinNE]

I see, but I do not have any alternative solution... It's a big problem to reference websites that disappear

:-(

[JoopN]

This is the same man https://pclambert.net/interactivegraphs/ ?

[DarwinNE]

Unfortunately I don't think so. From what I recall it was a computer graphics course.

[JoopN]

With export to pdf you are limited to Helvetica, Courier, Times of Symbol fonts. These are Windows fonts. So on an other system not running under Windows those fonts will have a different name. The question is how strict those names are? Next how does the export decides if it is the right font, has the font name have to begin with one of those four names or can it also somewhere in the middle or the end of the name?

[JoopN]

How do you want to have the pull request? All files separate or for each language one zip file?

[DarwinNE]

There is no need for a zip file. Read this document if in doubt about how to proceed:

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request

Create a subdirectory for each additional language. Put all files related to that language there. Make sort that all the files can be compiled directly from the subdirectory. Include the pdf file in the commits.

[JoopN]

I have 3 manuals (English, Dutch and German), one uploaded. I'm pushing to left and to right, up and down, made it private, made it public, followed the guidelines, but in the end nothing. Seems you are not open for it. I give up. Github is not for me. Something which should be easy seems to be an terrible headache. For some reason Github don't want any code, so you make it as difficult as possible. I can spend my time better.

[DarwinNE]

GitHub works with a philosophy that works well for large participative project but sometimes is overkill for smaller ones.

However, I checked and I don't see any public repository in your account. Of course you will not be able to commit changes directly to my repository, you have to create your own. Usually things work as follows: 1 - You fork the repository in your account. It is quite easy to do, if I recall correctly there is an icon "Fork" in the top right corner of the DarwinNE/FidoCadJ page. That will create in your account a public repository that will be called JoopN/FidoCadJ. You will have write access to this repository. 2 - You commit the manuals and the changes to your repository. 3 - Once you have the commits in your local copy of FidoCadJ, you can create a pull request towards my repository. The system will compare the two repository and propose a pull request.

If you want to have a look at the past pull requests that were merged into the FidoCadJ project, have a look here: https://github.com/DarwinNE/FidoCadJ/pulls?q=is%3Apr

Let me know if you experience difficulties.

[JoopN]

Thanks, that helped. Now I'm at the stage that I can create a pull-request, but I can't choose where they have to go to, ie DarwinNE/FidoCadJ/manuals. Second I have made a /main, in it /Dutch-translation, in it /images and in that /icons. If you start the tex from /Dutch-translation (if that is possible) it should compile because all is at place ie /images and /images/icons are a sub-directory of /Dutch-translation. Or just do the pull-request and you do your own placing into the structure? Need advice in this. For now just the Dutch part, if that's going okay then I can upload English (update) and the German manuals which have there own images and icons directories. The directory /images contain nationalized pictures, the directory /icons is just the standard you already have.

[DarwinNE]

Ok, now I see the repository. GitHub says it is up to date with the main repository that is mine. You should learn how to use Git now. 1 - The idea is that you must have a local working directory on your disk (you obtain it with git clone and the appropriate address, click on your repository on the green button "Code" and use that address. It should be something like "https://github.com/JoopN/FidoCadJ.git" 2 - You can modify the local working copy 3 - You stage and commit the changes. Look at the Git documentation. (commands "git add" and "git commit -m") 4 - You push the changes on your project on GitHub. You may need a token that you can obtain from GitHub. 5 - From your updated GitHub repository, you generate a pull request.