one line can have several midpoints ?
by Cristian Secară
I have this string
#: ../src/widgets/toolbox.cpp:1817
msgid "Line Midpoints"
I am not sure, but it sound strange to me that a line can have more
than one midpoint.
Is this ok ? Or perhaps it should be Lines Midpoints ? Or just Line
Midpoint ?
Cristi
--
Cristian Secară
http://www.secarica.ro
10 years, 1 month
Doubts and typos translating strings from Gcode graffiti extension
by Lucas Vieites
Hi,
I'm finishing the Spanish translation for the current 0.49 version and
I'm having trouble with a couple of strings, especially from the Gcode
extension:
"Preview's paint emmit (pts/s):" I have no clue about this one; Google
doesn't either ;-)
There's also this one, which I think originally had some new lines:
"This function creates path to engrave letters or any shape with sharp
angles. Cutter's depth as a function of radius is defined by the tool.
Depth may be any Python expression. For instance: cone....(45
degrees)......................: w cone....(height/diameter=10/3)..: 10*w/3
sphere..(radius r)...........................: math.sqrt(max(0,r**2-w**2))
ellipse.(minor axis r, major 4r).....: math.sqrt(max(0,r**2-w**2))*4"
Here's a typo:
"Sort paths to reduse rapid distance" => "*reduce"
I hope someone can help me here...
Cheers,
--
Lucas Vieites
lucas@...162...
http://blog.codexion.com
http://www.linkedin.com/in/lucasvieites
10 years, 2 months
Re: [Inkscape-translator] Translate and wiki.inkscape.org
by Alexandre Prokoudine
On Mon, Jan 14, 2013 at 4:56 AM, Federico Leva <federicoleva@...296...> wrote:
> Hello,
> I see that wiki.inkscape.org is a multilingual wiki.
> Have you considered using the Translate extension, which allows to easily
> make your MediaWiki multilingual? It makes you save enormous amounts of time
> which otherwise is wasted on templates wizardry, manual synchronisation of
> pages and so on, scarying off most translators; and offers many other aids
> to efficient translation.
> https://www.mediawiki.org/wiki/Extension:Translate
> Now it's also available in handy tarball bundles.
> The page explains how to get help and more information, and there is
> extensive documentation; asking on #mediawiki-i18n @ freenode is probably
> your best chance for immediate assistance if needed.
> Regards,
> Federico / [[User:Nemo_bis]]
Federico,
I personally haven't considered using anything like that, because I'm
simply the wrong person to ask :)
CCing the reply to Inkscape translators mailing list which is a better
place for a question like that.
Alexandre Prokoudine
http://libregraphicsworld.org
10 years, 2 months
cannot find some strings for translation
by Cristian Secară
There are some strings I want to translate but I don't know where to
find them. The strings from
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head:/po/
are very different than the stable 0.48.4 ?
I tried also with a development version, "inkscape R10800" from
oss-marketplace, but there was no difference.
Example:
- when opening Inkscape, I cannot find the the string from status bar
"No objects selected. Click, Shift+click, or drag around objects to
select."
- when opening a .png file, a dialog will prompt for embedding or link
to the file; the strings "embed" and "link" appears to be missing
from my .po
On the other hand, in bitmap export dialog there is "Bitmap size"
which *is* translated in .po file (<b>Export area</b> = <b>Zona de
exportat</b>) but appears in English, "Batch export all selected
objects" is translated but with _ accelerator on B_atch, "Hide all
except selected" also appears in English while in .po file is with
accelerator on a_ll, Filename don't know where to find in .po (but it
also appears it has an useless accelerator on F).
??
I am using the .pot file from this place
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files
Cristi
--
Cristian Secară
http://www.secarica.ro
10 years, 2 months
Official status of 0.49 & future dev cycles
by Josh Andler
Hey All,
I want to try something different with this dev cycle based on
feedback that has been received as well as it being our least
predictable cycle thus far. First, I want to thaw trunk to a degree.
New features are allowed if they really appear to be "complete"...
this means no committing anything that is known to not be fully
implemented, introduce regressions, or otherwise has known issues. On
top of that, if the author of said feature does not have time to
polish/bugfix within a month based on feedback, it's just not the
right time to merge it.
Once we are clearly moving forward toward a release, at that time I
will propose a freeze. Once all blocker bugs are closed out a release
branch will be made. At that point is when string freeze will
officially set in on that release branch. 6 wonderful weeks of further
bug fixes and translating will then take place.
Yes, it seems like the release is "just sitting there" while getting
wrapped up, but one benefit is a planned period to get test builds out
in the wild so we can possibly get an even more stable new release
out. Regular users always catch our oversights, so the more of them
with their hands dirty helps save us some potential bug tracker grief.
Hopefully some other great new stuff has the potential to land in 0.49
now. It's a shame for development to not still charge ahead if
people's work is far along enough. We'll see how this works out this
time and if appropriate perhaps do the same again in future releases.
I will let everyone know when it looks like we should actually go back
into feature, but from where I sit, I don't foresee that being too
soon.
As usual, any questions, comments, or feedback are welcome.
TL;DR: We're mostly thawed, but commit quality matters more than
usual. An update will be posted when it's merited.
Cheers,
Josh
10 years, 2 months