On Mon, 26 Dec 2005 aaron@...749... wrote:
Date: Mon, 26 Dec 2005 20:48:12 -0600 From: aaron@...749... To: bulia byak <buliabyak@...400...> Cc: Lucas Vieites <lucas@...212...>, Inkscape Devel List inkscape-devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] Trouble translating extensions
bulia byak wrote:
I really think the original names would benefit from a renaming.
The names were mostly my choice, I cite artistic license. :) But I am in no way opposed to renaming.
"FretFind*": What does ET stand for in "FretFind Multi Length ET"?
This extension seems to be too specialized. Would anyone object if we drop it?
MixedCaseIsOkayInCodeButNotSoGoodInUserVisibleText :(
ET = Equal Temperament. Yes, it is too specialized.
Acronyms ... :(
"Kochify": What do they do, and what does Koch have to do with it?
I'd propose "Fractalize" for this.
Fractalize is too vague.
"Koch Fractal" perhaps? As in "Kock Fractal" (Effect) but the Effect is implied because it is in the Effect menu.
The suggested search keywords "Koch Snowflake" sound pretty good too, if it is good enough for Google?
(If I recall correctly there is a way for developers to add comments before translatable strings to warn about things words like Koch being a proper name.)
"Summer's night": What does it do? Shakespearian reference?
This really should be "Envelope".
(I'd have gone for "Summer Night" because I'd be worried about incorrect use of 's and American versus British Grammar rules which vary slightly on the issue but unless you stick with the abstract artistic name the point is moot)
Envelope is also vague.
Is this related to the SVG Envelope which can be used for certian kinds of distortions? If so then it is great to see progress being made in that area so soon already.
- Alan H.