Hi,
Snapping hints are awesome. However, there is one thing that worries me a lot about them: they are constructed with English syntax in mind. I foresee lots of complains from translators, including myself :)
Take 'cusp node to cusp node' for example. It's fine for English, but in Russian these two 'cusp node' instances will be in different cases and thus have different case endings --- both 'cusp' and 'node'.
Is there something we can do about that?
Alexandre
On 03/06/2009 10:32 PM, Alexandre Prokoudine wrote:
Hi,
Snapping hints are awesome. However, there is one thing that worries me a lot about them: they are constructed with English syntax in mind. I foresee lots of complains from translators, including myself :)
Take 'cusp node to cusp node' for example. It's fine for English, but in Russian these two 'cusp node' instances will be in different cases and thus have different case endings --- both 'cusp' and 'node'.
Is there something we can do about that?
They are two different strings, concatenated together. It's "Cusp node" + " to " + "cusp node". Notice the capital C. Isn't that sufficient?
If it's not, then please forgive me my ignorance.
Diederik
On Mar 6, 2009, at 1:41 PM, Diederik van Lierop wrote:
They are two different strings, concatenated together. It's "Cusp node"
- " to " + "cusp node". Notice the capital C. Isn't that sufficient?
If the code is actually doing string concatenation, then that's not really good.
What we should have is some single parameterized string. I'll have to look into what we have available code-wise.
On Sat, Mar 7, 2009 at 12:32 AM, Alexandre Prokoudine wrote:
Hi,
Snapping hints are awesome. However, there is one thing that worries me a lot about them: they are constructed with English syntax in mind. I foresee lots of complains from translators, including myself :)
Take 'cusp node to cusp node' for example. It's fine for English, but in Russian these two 'cusp node' instances will be in different cases and thus have different case endings --- both 'cusp' and 'node'.
Is there something we can do about that?
Eh, I do ask for apologize. It looks like this was already solved by capitalizing the first letter :-/
However, I believe there is a bug: when I try to snap a node to a cusp node of a path created in paraxial mode, it reports 'Cusp node to path intersection'.
Alexandre
On 03/06/2009 10:44 PM, Alexandre Prokoudine wrote:
However, I believe there is a bug: when I try to snap a node to a cusp node of a path created in paraxial mode, it reports 'Cusp node to path intersection'.
Ah yes, I see. There really is an intersection there though, exactly at the location of the node. I think I should make Inkscape ignore intersections of "path segment n at t=1" with "pathsegment n+1 at t=0", or something like that...
Diederik
participants (3)
-
Alexandre Prokoudine -
Diederik van Lierop -
Jon A. Cruz