>> I probably don't have much of a legal mind, but...it would seem odd >> to me if a list of file extensions could really be copyrighted. > > It still was a significant amount of work that someone else did that I > totally stole. It would have taken me a long time to: > > a) Come up with that list > > b) Convert it to the pref format that OS X needs
IANAL. I'm also in Australia, and have no idea under what legal jurisdiction MacVim falls, or the aforementioned not-so-free app, or whether it really matters. But...I do know, or think I know, that - The amount of work put into it is irrelevant. - Nonetheless copyright may well subsist in the 'compilation' of those associations, i.e. the selection and arrangement of them (so, yes the 'coming up with the list' part does make it copyright; not because it was a lot of work, but because it was essentially creative work). - Copyright wouldn't subsist in the individual associations themselves, which is the kinda obvious thing: just because one person associates a filetype to an app doesn't mean nobody else can do the same! So, yeah, I believe basically you can come up with your own list which incidentally will have similar associations to a lot of other people's lists, but you can't just rip someone else's list unless it has a compatible license. Ben. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_mac" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
