Only the known measurement translations are included in the spread sheet. It does not contain the translations for the Seamly2D and SeamlyMe apps…which is way out of date with all the changes I have made to the UI.
Not likely… these translations were probably made through Transifex back before the Seamly was forked from Valentina.
There’s a bit more to creating translations for a Qt app. If we take a step back… In the code when ever you want a string translated it’s wrapped with the tr() function. Such as tr(“Pattern Piece”). Then using Qt Liquist or lupdate.exe, all those tr()'s are encoded as an XML .ts file - per language required. Once those are created / updated several things can happen… the ts files can be pushed to the repo - so that they are available to a service such as Transifex, where they are then exported as the runtime binary qm files, pushed back to the repo, and then become part of the next build release. OR a service can be bypassed, and an individual could edit the ts files, export the qm files from Qt Liguist, and push both the ts & qm files to the repo on Github OR a user could just translate the ts files and using Qt and Linquist make their own builds. That being said, to use the xlsx you’re also going to have to build a conversion app to convert the xlsx back to a ts for use in Linquist.
Yeah, I noticed this. Wrote it before looking into the file. Now comes the hard part - get together czech & english tailoring meas. Is it possible for you to export description for measurments?
I mean it’s not revised to be correct, looks like someone just translated words.
Technically the measurement names are not proper English either… if it was the names would be a mess. They’re based on a naming scheme. For example… height_highhip… indicates it’s a vertical height measurement from the floor to the high hip… height_calf - vertical measurement from floor to calf. So yes… they’re a bunch of words, not a grammatically correct phrase.
I would expect to see for example the Czech word for “height” followed by “_” + the Czech word(s) for “high hip”. Note that spaces are not used - it’s a coding thing, so we end up with some names such as highhip - which is not an English word, but rather high and hip put together.
If you start literally translating the measurement names you will kinda mess up the whole naming scheme, and behavior such as searching for a certain term.
That being said… the UI translations on the other hand should follow a more grammatically correct form for the given language. And this is where having a native speaker, fluid in garment pattern making to translate would be invaluable. So we don’t end up with nonsense pattern terms like “passmark”… which I suspect as something Google would have spit out.
I’m really happy that you will correct the Czech terms. Getting these right is highly important to the software, as are the translations of the UI. So thank you very much.
It’s really hard to get patternmaking people to donate their time to something like this, so I guess Google Translate was about the only way to get something into the software, since, as @Douglas has said, patternmaking has a language of it’s own, which includes the points of measure.
Yes… that part is very handy. I also found that it provides for ex: the Frence masculine and feminine translations in some cases. Not sure how that would apply to Seamly, but this site is certainly more robust than Google translate.
Hola a todos mi nombre es Gerardo, estoy estudiando patronaje en mi país, Perú y quisiera aprender a utilizar este programa, el problemita que tengo es que no se ingles. Alguno de ustedes conoce donde puedo encontrar información en español.
Gracias.
Si yo te puedo ayudar en algo dilo. Hay varios videos en youtube para sentar las bases mas los diferentes archivos que pude rescatar en español en la red algunos vienen con el antiguo valentina pero la base de las herramientas son las mismas. En yotube tienes los videos de puntada y pixel, mariana creativa y otro mas con el perfil de negocios digitales para moda. Si encuentro alguno mas te lo hago saber. Baja la velocidad de reproduccion de los videos te ira mejor. En la web de puntada y pixel tambien tienes ejercicios para practicar.
Is there still help needed? I saw that in the file is a column “Dutch” which basically contains German translations but not all of them seem to be correct to me. For example, line 234 says in English “Neck Back to Armfold Front (neck_back_to_armfold_front)” which definitely can’t, in my opinion, have something to do with the length of the arm (armfold to wrist)? As I have the latest version from github, it is probably not the stable one (but works for me) and I don’t have other languages than English in there, so I can’t check the German terms (the apparently stable version didn’t work, some glitches with Qt or so).
Yes, we do still need help with the translations. I created the Excel file so that people can corrent the terms in their language and return it to me so that I can update the master Excel sheet and send it to someone who can update the terms to ts. However, if you can do it directly in QT, that will work, too. Thank you very much.
To edit the translations you don’t need Seamly2D or SeamlyMe apps. The easiest way to edit the translation TS files is using the stand alone Qt Linguist app. You can edit the ts files using any text editor - they’re just xml files, but it’s easier (and safer) to just use Linguist.
That being said, what needs to hapoen first is I will have to run an Lupdate on the translations. That will update / add any new texts to the ts files that need translating. Once I do that - I could just send you whichever ts files (and whichever OS ver of Linguist if you don’t have the Qt framework). Then you can send the ts file(s) back and I can deal with pushing the changes to Github.
The idea was to look up what is standing in the menus there and first of all to look at the pictures of the measurements, where they have to be taken, so that I can see which measurement it would be.
After @Grace mentioned QT yesterday I had a look at github and the German ts-files there in the folder “share” seem to have only German measurement names; is it possible that somebody already worked on those ts-files already?
That would be great Don’t hurry though, next week I’ll travel and won’t have any time to do anything. Starting the week after that it there should be more time.
Unfortunately no. It’s because the project has had a fairly complete measurements set since way back & the few updates have been in the interface, not the measurement list.
Nope. The ts haven’t been touched since forking - as far as I know.
Well I did recently added a new measurement (which was requested years ago) … so it needs to be translated. And yeah… any new measurements at this point would have to be pretty esoteric as the current ones pretty cover everything as far as the drafting systems go.
Than something must have happened to the excel-file. Thanks goddess the ts-file seems to look way better. I’ll have a closer look when I am back the week after next.
Is there any way to compile from source for a currently not so trained linux-user? I am not at all happy with the app-image. I did compile in earlier times but didn’t find something like a config-file.
I don’t recall if you’ve mentioned which version of Linux you use, but I did recently make a topic about building Seamly from source on Ubuntu 22: Building Seamly on Ubuntu 22
It sure will I’ll tackle that beast some-when around Christmas, I guess, as I definitely need to update my system first. And no, I didn’t mention the distro Right now it is still Ubuntu 20.04 but I will change this.
Just to throw it out there… if you have forked the project on Github, you can create your own workflows, and let Github do the building instead of building locally.
I assume Grace tweaked the excel file, but the ts files have not changed. Unless someone has manually edited the ts files or ran an Lupdate, then pushed the changes and created a pull request to be merged - the ts files haven’t changed. In fact I created a make option (noTranslations) to turn off copying the translations (locally) since it can take several extra minutes building as 100’s of (unchanged) translation files are copied (again)… not to mention it just clogs up the compile log with a line for each file copied.
BTW… I knew there was something I forget to do over the weekend - run an Lupdate.
I’ll tackle that beast some-when around Christmas, I guess, as I definitely need to update my system first. And no, I didn’t mention the distro