Karbon or Karbon14?

[Friedrich W. H. Kossebau]

Am Donnerstag, 23. Februar 2012, 23:22:46 schrieb jaham at gmx.net:
> On Thursday 23 February 2012 15:37:59 Friedrich W. H. Kossebau wrote:
> > Hi,
> > 
> > IIRC the official name of Karbon14 is now (Calligra) Karbon. But in the
> > sources (including the .desktop files) the name is still Karbon14.
> > Something inside me wants to fix this :)
> > 
> > Okay if I provide a patch to change the name from "Karbon14" to "Karbon"
> > in
> > all places left?
> 
> Yeah I think nobody is calling it Karbon14, it is too bothersome to call it
> like that. However I am not sure about it, but I think the name was chosen
> to avoid any legal/trademark issues which might come up (i.e. not to repeat
> history as with the KIllustrator name).
> So to sum it up, i would prefer dropping the 14 and just call it Karbon
> (which we all do already), provided nobody thinks we might get into any
> legal trouble.

So that potential trouble is actually why no real decision has happened I 
guess? Hm. The only thing I saw whose name is close was some API set, but that 
seems not a registered trademark and at least I do not see a risk for user 
confusion (thus legal rights for the first user of the name group), as the 
fields are quite different. But IANAL and do not know what actually strange 
rights are applied in whatever countries (e.g. having software still as one 
single group of products).

Then, calligra.org already says "Karbon", so that trouble is risked already. 

So jump or stay where you are. Having just one leg in the water is enough for 
biting fish anyway ;)

> > PS: Have I already told how awesome I find Karbon? So far whatever I
> > created as ODG file was nicely displayed, as expected! Only now I might
> > have found the first bug (x y attributes in tspan ignored, but have to
> > check this).
> Thanks for you kind words, it is highly appreciated!
> Regarding the bug, that refers to the svg:tspan child element from svg:text,
> right? It should support the x and y attributes, but I am sure there are
> still issues with that, so might be a real bug.

The attributes are read in the code, but something in the processing might not 
work. You can see an error yourself easily: add an artistic text shape, enter 
text with a linebreak, save the file and reload. The second line will now be 
placed somewhere different.

Will file a bug about that, so it is not forgotten.

Cheers
Friedrich