Hello guys,
A quick update just to tell you that this morning I was glad to find a
follow up message from Crowdin about my request for man pages improved
support (above simple txt file)
While there, be assured I haven't let this down, but rather decided to get
used to this on a smaller
Men, may I kindly ask you stop hijacking this thread please
Le lun. 30 nov. 2020 à 17:12, Jon Elson a écrit :
> On 11/30/2020 01:07 AM, Gene Heskett wrote:
> >
> > And this has an encoder generating good quadrature signals optically, on
> > the back end of the motor, from which the encoder
On 11/30/2020 01:07 AM, Gene Heskett wrote:
And this has an encoder generating good quadrature signals optically, on
the back end of the motor, from which the encoder module will output
both position in counts (for comparison to SCALE) and velocity. Can I
use both signals in 2 pid's in series?
Olà,
Le dim. 29 nov. 2020 à 23:46, andy pugh a écrit :
> On Sun, 29 Nov 2020 at 21:50, J.M. Garcia wrote:
>
> > Second, what is the benefit of this approach from the point of view of
> pure
> > translation work? I can't see any.
>
> I don't know enough about it, but I can see that a
On Sunday 29 November 2020 22:21:10 Jon Elson wrote:
> On 11/29/2020 08:09 PM, Gene Heskett wrote:
> > But what characteristic is it that actually determines
> > what sort of a servo it is? As in torque vs velocity? I
> > intend for this to work under cutting loads. That is why
> > the double
On 11/29/2020 08:09 PM, Gene Heskett wrote:
But what characteristic is it that actually determines
what sort of a servo it is? As in torque vs velocity? I
intend for this to work under cutting loads. That is why
the double reduction of two worm drives in series that
this will be.
A velocity
On Sunday 29 November 2020 20:24:27 Jon Elson wrote:
> On 11/29/2020 07:02 PM, Gene Heskett wrote:
> > I should be at about the servo tuning step by this time
> > next week, something I have only done with steppers, and
> > likely at less than optimum settings.
> >
> > Is there a tut on adjusting
On 11/29/2020 07:02 PM, Gene Heskett wrote:
I should be at about the servo tuning step by this time
next week, something I have only done with steppers, and
likely at less than optimum settings.
Is there a tut on adjusting such a servo?
You could look at my page on servo tuning at :
On Sunday 29 November 2020 17:45:33 andy pugh wrote:
> On Sun, 29 Nov 2020 at 21:50, J.M. Garcia wrote:
> > Second, what is the benefit of this approach from the point of view
> > of pure translation work? I can't see any.
>
> I don't know enough about it, but I can see that a purpose-made
>
On Sun, 29 Nov 2020 at 21:50, J.M. Garcia wrote:
> Second, what is the benefit of this approach from the point of view of pure
> translation work? I can't see any.
I don't know enough about it, but I can see that a purpose-made
translation platform might make it easier to keep track of new
Hi all
Andy was kind enough to use my Spanish translations in his recent work on
linuxcnc 2.8.
Many of the issues that are being discussed here (the halcompile issue, for
example) produced, and still do, severe headaches.
Now I just want to give my opinion on the separation of translation work.
Hi all
Andy was kind enough to use my Spanish translations in his recent work on
linuxcnc 2.8.
Many of the issues that are being discussed here (the halcompile issue, for
example) produced, and still do, severe headaches.
Now I just want to give my opinion on the separation of translation work.
Le ven. 27 nov. 2020 à 13:44, andy pugh a écrit :
>
> That sounds promising. What happens next?
>
If there's no problem for everyone at this stage, I'd like to push the
Crowdin test, together with POedit, as well as OmegaT, up to what could be
considered an alpha setup.
All documentation files
On Wed, 25 Nov 2020 at 06:39, Jérémie Tarot wrote:
Feel free to invite translators to your project and translate the content :)
> New Crowdin version is also right here to give a try:
> https://enterprise.crowdin.com
> You can freely launch your project here and invite the community - we'd be
>
Le mar. 24 nov. 2020 à 00:32, andy pugh a écrit :
> On Sun, 22 Nov 2020 at 21:30, Jérémie Tarot wrote:
>
> > https://crowdin.com/project/linuxcnc) would really help translators work
> > and maybe build a team for this task...
>
> Does it cost money? The LinuxCNC project has literally no money.
Hi
Le mar. 24 nov. 2020 à 08:03, Sebastian Kuzminsky
a écrit :
> Francis Tisserant and I played around with po4a a couple of years ago.
> po4a is a tool that helps maintain translations of documentation - it
> lets you use gettext on asciidoc docs. I'm not sure if it would work on
> .comp
Le mar. 24 nov. 2020 à 10:42, Les Newell a
écrit :
> On 23/11/2020 23:31, andy pugh wrote:
>
> Gettext is primarily designed to work with relatively short strings in
> source code. It's not really aimed at translating documents. There is no
> reason why it couldn't be used for the main
Le mar. 24 nov. 2020 à 20:41, andy pugh a écrit :
> On Tue, 24 Nov 2020 at 09:42, Les Newell
> wrote:
>
> The issue I was trying to address is with the .comp files that create
> many of the HAL components. These contain documentation as part of the
> file, but those strings are not part of the
On Tue, 24 Nov 2020 at 09:42, Les Newell wrote:
> However for
> strings contained in the source - gui, hal modues etc- it works really
> well with only minor changes to the source code.
The issue I was trying to address is with the .comp files that create
many of the HAL components. These
On 23/11/2020 23:31, andy pugh wrote:
I _think_ that gettext only works in the context of source code. I
could be wrong, though.
I looked in to gettext for halcompile and couldn't see how to make it work.
Gettext is primarily designed to work with relatively short strings in
source code. It's
On 11/23/20 4:31 PM, andy pugh wrote:
On Sun, 22 Nov 2020 at 21:30, Jérémie Tarot wrote:
https://crowdin.com/project/linuxcnc) would really help translators work
and maybe build a team for this task...
Does it cost money? The LinuxCNC project has literally no money.
To better benefit
On Sun, 22 Nov 2020 at 21:30, Jérémie Tarot wrote:
> https://crowdin.com/project/linuxcnc) would really help translators work
> and maybe build a team for this task...
Does it cost money? The LinuxCNC project has literally no money.
> To better benefit these, it seems preferable that l10n
Hey Andy,
Thank you for yours answers
Le dim. 22 nov. 2020 à 18:11, andy pugh a écrit :
> I moved the docs into a sub-directory.
>
Let's say that's a start ;-)
I have done some work to enable multilingual documentation in .comp
> files, and translated manually-written manpages (should) be
>
On Sat, 21 Nov 2020 at 13:29, Jérémie Tarot wrote:
> Configuration
> pncconf
> stepconf
> halscope ?
> (other power user tools I don't kow yet ?)
A launcher for Halscope (and also Halshow and Halmeter) is a good
idea. I don't know why it has typically been
On Sat, 21 Nov 2020 at 13:29, Jérémie Tarot wrote:
> It surely can be better organized. I'd personally rather restructure all
> its content and promote it to top level while demoting all the standard
> entries to some kind of "System" entry.
I moved the docs into a sub-directory.
> 1000% ! Can
Hello from France,
Please forgive me for reviving this old thread but stumbled on it while
trying to map the land of project's translation and looking for a proper
way to jump in...
Le dim. 12 juil. 2020 à 15:32, andy pugh a écrit :
> I consider the "CNC" menu to be excessively cluttered.
>
> On Sun, 12 Jul 2020 at 21:59, Rod Webster wrote:
>
>> It is possible to generate translations on the fly on a web site using
>> Google Translate.
>
> There is an interesting problem with computer translation, which needs
> to be kept in mind and that is character encoding.
> There is some
On Sun, 12 Jul 2020 at 21:59, Rod Webster wrote:
> It is possible to generate translations on the fly on a web site using
> Google Translate.
There is an interesting problem with computer translation, which needs
to be kept in mind and that is character encoding.
There is some risk of
> On 07/12/2020 03:59 PM, Rod Webster wrote:
> > Personally, I think the power of Google Translate makes this redundant.
> > If I open a non-english HTML page Google Translate just translates it for
> > me.
> > I asked a French speaking person to review a 20 page technical document of
> > mine
On Monday 13 July 2020 11:07:33 Jon Elson wrote:
> On 07/12/2020 12:49 PM, andy pugh wrote:
> > On Sun, 12 Jul 2020 at 18:44, Leonardo Marsaglia
wrote:
> >> By the way. I second the dropping the PDF docs in favour of the
> >> HTML ones. It's much more easy to find the info in the HTML docs
> >>
On 07/12/2020 03:59 PM, Rod Webster wrote:
Personally, I think the power of Google Translate makes this redundant.
If I open a non-english HTML page Google Translate just translates it for
me.
I asked a French speaking person to review a 20 page technical document of
mine which I had translated
On 07/12/2020 12:49 PM, andy pugh wrote:
On Sun, 12 Jul 2020 at 18:44, Leonardo Marsaglia wrote:
By the way. I second the dropping the PDF docs in favour of the HTML ones.
It's much more easy to find the info in the HTML docs that I almost forget
there are PDF docs uploaded.
The PDF ones are
On 07/12/2020 10:52 AM, andy pugh wrote:
On Sun, 12 Jul 2020 at 16:39, wrote:
Go for it AndyP.
Is this support for dropping the multilingual docs?
Well, horribly out of date multilingual docs should maybe be
removed from the main directory tree, but retained in git so
if somebody so
If we keep the French docs they should be only in the version where they
are up to date.
The Spanish docs can be dropped as only a few pages were translated.
JT
On 7/12/20 8:31 AM, andy pugh wrote:
I consider the "CNC" menu to be excessively cluttered. It has links to
the PDF docs in all
> On Mon, 13 Jul 2020 at 03:18, Reinhard wrote:
>
> > When I run pncconf last days I noted the bad translation status of german
> > texts. Well - not the docs, as there is no german variant.
>
> I can read French and German well enough to tell if the docs are
> correct, but not well enough to
> On Mon, 13 Jul 2020 at 03:18, Reinhard wrote:
>
> > When I run pncconf last days I noted the bad translation status of german
> > texts. Well - not the docs, as there is no german variant.
>
> I can read French and German well enough to tell if the docs are
> correct, but not well enough to
On Mon, 13 Jul 2020 at 03:18, Reinhard wrote:
> When I run pncconf last days I noted the bad translation status of german
> texts. Well - not the docs, as there is no german variant.
I can read French and German well enough to tell if the docs are
correct, but not well enough to correct them.
> I thought, every german would know english, as it is teached at elementary
> school already. But reality is different. I met several germans interested in
> cnc, that don't know english. So having docs in native language can help
> spread the project.
Could confirm this, one of my old
> If a translation is not being actively maintained there is really no point
> including it in a distribution.
> I only ever use the HTML docs on the web site.
No Internet on machines in workshop, locally available then pressing F1 would
be good unless there are any major disadvantages.
>
Hi,
On Sonntag, 12. Juli 2020, 22:59:09 CEST Rod Webster wrote:
> I asked a French speaking person to review a 20 page technical document of
> mine which I had translated in Google Drive from English to French using
> Google Translate. He said there was nothing for him to do as it was perfect!
If a translation is not being actively maintained there is really no point
including it in a distribution.
I only ever use the HTML docs on the web site.
Personally, I think the power of Google Translate makes this redundant.
If I open a non-english HTML page Google Translate just translates it
Just signed up Andy, I don't want to touch anything (although I guess there
are invitations or user privileges) but whenever you need it let me know so
I can make the translations :)
El dom., 12 jul. 2020 a las 15:50, andy pugh ()
escribió:
> On Sun, 12 Jul 2020 at 19:46, Leonardo Marsaglia
>
On Sun, 12 Jul 2020 at 19:46, Leonardo Marsaglia wrote:
> Could the "[[cha:getting-linuxcnc]]" string be the cause of the
> problem? I'm just guessing here.
It's certainly the obvious difference.
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial
>
> For some reason it doesn't recognise the english version of that doc
> as asciidoc, so leaves it plain text.
Could the "[[cha:getting-linuxcnc]]" string be the cause of the
problem? I'm just guessing here.
El dom., 12 jul. 2020 a las 15:39, andy pugh ()
escribió:
> On Sun, 12 Jul 2020 at
On Sun, 12 Jul 2020 at 19:08, Leonardo Marsaglia wrote:
> Thanks Andy, I've only entered Github just too see how some components
> were coded but I now can see how powerful it is :).
For some reason it doesn't recognise the english version of that doc
as asciidoc, so leaves it plain text.
--
>
> Both HTML and PDF docs are generated from the same asciidoc markup.
> For example:
>
> https://github.com/LinuxCNC/linuxcnc/blob/master/docs/src/getting-started/getting-linuxcnc-es.txt
> (Click the "Raw" button to see the Asciidoc. Github knows how to
> convert asciidoc to pretty)
Thanks
On Sun, 12 Jul 2020 at 18:56, Leonardo Marsaglia wrote:
> I'm not that sucked in into programming yet (even less into
> web programming) but, couldn't the PDF docs be automatically updated or
> generated from the HTML ones?
Both HTML and PDF docs are generated from the same asciidoc markup.
>
> The PDF ones are added to the package by the build system. I don't
> _think_ that the HTML ones are.
I'm not that sucked in into programming yet (even less into
web programming) but, couldn't the PDF docs be automatically updated or
generated from the HTML ones?
El dom., 12 jul. 2020 a las
>
> Yes, it would help a lot, even if only the updates to "getting
> started" and "updating linuxcnc"
More than happy to give back something to this wonderful
project/community.
>
>
I need to update the English docs to reflect the current reality
> first, then I will come back to you :-)
>
On Sun, 12 Jul 2020 at 18:44, Leonardo Marsaglia wrote:
> By the way. I second the dropping the PDF docs in favour of the HTML ones.
> It's much more easy to find the info in the HTML docs that I almost forget
> there are PDF docs uploaded.
The PDF ones are added to the package by the build
On Sun, 12 Jul 2020 at 18:40, Leonardo Marsaglia wrote:
> I can translate myself the docs to Spanish if that helps.
Yes, it would help a lot, even if only the updates to "getting
started" and "updating linuxcnc"
I need to update the English docs to reflect the current reality
first, then I
By the way. I second the dropping the PDF docs in favour of the HTML ones.
It's much more easy to find the info in the HTML docs that I almost forget
there are PDF docs uploaded.
El dom., 12 jul. 2020 14:39, Leonardo Marsaglia
escribió:
> I can translate myself the docs to Spanish if that
I can translate myself the docs to Spanish if that helps. But honestly
being a native Spanish language speaker I really don't see the need of
having so many languages when clearly English is the preferred language in
almost every field humanity has developed.
But to be fair, lots of people could
Good point there Reinhard. If there is interest in some translation work
will be done in the future. There is no interest now for sure..
Keep going further Andy..
On Sun, Jul 12, 2020, 18:41 Reinhard wrote:
> Hi,
>
> On Sonntag, 12. Juli 2020, 17:52:15 CEST andy pugh wrote:
> > On Sun, 12 Jul
Hi,
On Sonntag, 12. Juli 2020, 17:52:15 CEST andy pugh wrote:
> On Sun, 12 Jul 2020 at 16:39, wrote:
> > Go for it AndyP.
>
> Is this support for dropping the multilingual docs?
I don't think, that dropping multilingual docs is a good decision.
But it can't be the responsability of Andy to
On Sun, 12 Jul 2020 at 16:39, wrote:
>
> Go for it AndyP.
Is this support for dropping the multilingual docs?
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta
Go for it AndyP..
Also agree with stripping the liveCD down. No Office, games, media, or other
bs..
It's a machine controller, not a game boy or juke box.
___
Emc-developers mailing list
I consider the "CNC" menu to be excessively cluttered. It has links to
the PDF docs in all languages, the HTML "G-code quick-start" in
English, French (out of date) and Vietnamese (no idea about currency)
as well as the main app. the wizards and the latency test.
Personally I find the HTML docs
58 matches
Mail list logo
