Consider the fact that the spinoff project took all the code from your project, and that it's all GPLed. You should make the other project leader aware of that fact.
What if, after the CD "presented itself" as a CD-ROM to my computer, I ripped the CDDA part to OGG just as with any other CD? Would the CD then notice and yell at me?
This is another DRM fad that will do absolutely nothing.
What they haven't even thought about is whose data gets stored by whom.
Say Mr. Jones uses his Albania Online connection to send an e-mail to Mr. Smith. Mr. Jones' e-mail server, however, is located on Mbwawanga Island in Mbwamwere, and Mr. Smith's e-mail server resides in his living room.
If we assume that Albania Online is obligated to store all e-mail and voice traffic that even passes through its network for an extended period of time, we can also assume that after said period, there will, of course, be no Albania Online.
Simply put, X-Chat is in violation of the GPL if it uses GPLed code without providing the source code for said Windows binary. However, it's reasonable to assume that a free Windows client can be produced using the source tarball + a Windows version of GTK+, and thus any violation that might arise is probably minor.
I know how the encoding is handled, I'm more worried about the actual rendering. Can the Java virtual machines on phones with limited memory render Asian fonts?
As for the Japanese input methods, they need to use the Japanese kana alphabets, not kanji, since you can't write Japanese using kanji alone.
Well, Japanese and Korean at least necessitate either romanized input, or input with a uniquely Japanese layout. I'm guessing that for an English-speaking user, romanized input is just as well.
It's interesting how Java uses Unicode internally, though... The encoding conversion necessary to send the e-mails off to an Asian phone might not be that hard, and if the current Java-capable phones (like the Nokia 3510i) are already capable of correctly rendering Asian text, then it's more or less just a matter of creating an input method and a simple e-mail client.
Support for Chinese characters isn't actually one package that can be supported as such. First of all, you need fonts: Traditional fonts, simplified, Korean and Japanese fonts. Then you need support for encodings, like GB18030, ISO-2022-JP, ISO-2022-KR, Unicode, etc. And last but not least you need input methods, and Asian input methods are often rather complex.
Since at least Japanese users often prefer to send e-mail over their phones rather than text messages, it would be feasible to make a Java e-mail app that supported a few input methods and encoding conversions, as well as a rendering engine for Asian characters. However, I wouldn't hold my breath. It's a good thing if Nokia's trying to address this.
Yeah, there's no obligation to release the source, but there are a few other obligations that aren't strictly necessary. A few projects, like wxGTK, have chosen to use the LGPL, but make an exception for projects that link to it, exempting them from all the obligations of the LGPL.
I personally feel that anything using static linking is (possibly) a derivative work, while with dynamic linking it's probably not. It would be great to see a simple license that implements this.
I agree. However, the FSF licenses do have flaws. For instance, linking to a library such as libc or GTK+ requires you to advertise the libraries and the license in the binary executable. Making an exception for dynamic linking would remove that requirement, but the FSF does not exempt any type of linking. I believe a new license should be created with the simplicity of the BSD license, but some of the protection of GPL.
All you really have to do, of course, is make sure your software gets really famous. That way, if anyone ever patents it (which they will, of course), the victim can just refer to your program during the trial, after a busy morning of reading Slashdot.
There really should be an official office for registering prior art, though... One shouldn't have to turn to Slashdot for a task that could be performed by the government.
COST211: Redundancy Reduction Techniques for Video Signals (1977-1982)
Outcome: CCITT Recommendation H.121 2 Mbit/s codec for videoconferencing
COST211bis: Redundancy Reduction Techniques for Coding of Broadband Video Signals (1983-1990)
Outcome: CCITT Recommendation H.261 p x 64 kbit/s codec (1991)
Surely these people are just trying to benefit from obvious uses of other peoples' inventions. I can't even see a description of a codec in the application.
Wouldn't this kind of wallpaper mean a significant health benefit for anyone living next to a high-voltage power line? Add a few panels to your roof as well, and you've got a house that lets TV/radio signals etc. in, but keeps low-frequency radiation out.
The standard that you speak of is to design a website to work on any resolution. If you find at some point that your website only works at a particular resolution, then it's more or less a failure as a web site.
Use relative sizes for what they're worth, and stay away from those pixel sizes.
Whether or not you support de jure independence for Taiwan, it has got to be said that it's a pretty autonomous region. What could be more natural than for them to have a flag?
I have to admit though, that I do support de jure independence.
Slashdot Mirror
Now, actually. Children can even point and click before they can read, so the question is "when should they be given books", not the other way round.
Consider the fact that the spinoff project took all the code from your project, and that it's all GPLed. You should make the other project leader aware of that fact.
What if, after the CD "presented itself" as a CD-ROM to my computer, I ripped the CDDA part to OGG just as with any other CD? Would the CD then notice and yell at me?
This is another DRM fad that will do absolutely nothing.
What they haven't even thought about is whose data gets stored by whom.
Say Mr. Jones uses his Albania Online connection to send an e-mail to Mr. Smith. Mr. Jones' e-mail server, however, is located on Mbwawanga Island in Mbwamwere, and Mr. Smith's e-mail server resides in his living room.
If we assume that Albania Online is obligated to store all e-mail and voice traffic that even passes through its network for an extended period of time, we can also assume that after said period, there will, of course, be no Albania Online.
I wonder how they're going to solve that?
Does he have a timer on books too? Could be quite useful if he wants to shield his kids from taking in too much information.
Why do you actually "need" this? Would your life be so much worse if you just let them use the Internet however they wanted?
It mashes two lines into one by averaging the values? How is that not stone-age technology?
Wow. So let's take a few seconds to summarize these technologies:
1. Zooming an image to the proportion 1:2.
2. Inverted CMYK.
The white pixel on the screen's pretty clever though...
Though usually this is called "simple, plain, old downsampling", and not "subpixel drive". :)
Simply put, X-Chat is in violation of the GPL if it uses GPLed code without providing the source code for said Windows binary. However, it's reasonable to assume that a free Windows client can be produced using the source tarball + a Windows version of GTK+, and thus any violation that might arise is probably minor.
Ha ha.
Thanks man, that's excellent. I'll be considering this phone when I go to Japan.
If Slashdot switched to Unicode, this whole problem would disappear. But the question remains whether it's actually a problem.
I know how the encoding is handled, I'm more worried about the actual rendering. Can the Java virtual machines on phones with limited memory render Asian fonts?
As for the Japanese input methods, they need to use the Japanese kana alphabets, not kanji, since you can't write Japanese using kanji alone.
Well, Japanese and Korean at least necessitate either romanized input, or input with a uniquely Japanese layout. I'm guessing that for an English-speaking user, romanized input is just as well.
It's interesting how Java uses Unicode internally, though... The encoding conversion necessary to send the e-mails off to an Asian phone might not be that hard, and if the current Java-capable phones (like the Nokia 3510i) are already capable of correctly rendering Asian text, then it's more or less just a matter of creating an input method and a simple e-mail client.
Support for Chinese characters isn't actually one package that can be supported as such. First of all, you need fonts: Traditional fonts, simplified, Korean and Japanese fonts. Then you need support for encodings, like GB18030, ISO-2022-JP, ISO-2022-KR, Unicode, etc. And last but not least you need input methods, and Asian input methods are often rather complex.
Since at least Japanese users often prefer to send e-mail over their phones rather than text messages, it would be feasible to make a Java e-mail app that supported a few input methods and encoding conversions, as well as a rendering engine for Asian characters. However, I wouldn't hold my breath. It's a good thing if Nokia's trying to address this.
Yeah, there's no obligation to release the source, but there are a few other obligations that aren't strictly necessary. A few projects, like wxGTK, have chosen to use the LGPL, but make an exception for projects that link to it, exempting them from all the obligations of the LGPL.
I personally feel that anything using static linking is (possibly) a derivative work, while with dynamic linking it's probably not. It would be great to see a simple license that implements this.
I agree. However, the FSF licenses do have flaws. For instance, linking to a library such as libc or GTK+ requires you to advertise the libraries and the license in the binary executable. Making an exception for dynamic linking would remove that requirement, but the FSF does not exempt any type of linking. I believe a new license should be created with the simplicity of the BSD license, but some of the protection of GPL.
What's paper preciouss?
All you really have to do, of course, is make sure your software gets really famous. That way, if anyone ever patents it (which they will, of course), the victim can just refer to your program during the trial, after a busy morning of reading Slashdot. There really should be an official office for registering prior art, though... One shouldn't have to turn to Slashdot for a task that could be performed by the government.
And from http://www.dip.ee.bilkent.edu.tr/cost211.html
Outcome: CCITT Recommendation H.121 2 Mbit/s codec for videoconferencing
Outcome: CCITT Recommendation H.261 p x 64 kbit/s codec (1991)
Surely these people are just trying to benefit from obvious uses of other peoples' inventions. I can't even see a description of a codec in the application.
Wouldn't this kind of wallpaper mean a significant health benefit for anyone living next to a high-voltage power line? Add a few panels to your roof as well, and you've got a house that lets TV/radio signals etc. in, but keeps low-frequency radiation out.
The standard that you speak of is to design a website to work on any resolution. If you find at some point that your website only works at a particular resolution, then it's more or less a failure as a web site.
Use relative sizes for what they're worth, and stay away from those pixel sizes.
Cutlery, flatware, eating utensils are some words that could cover the same range of items.
That is so sad!
Whether or not you support de jure independence for Taiwan, it has got to be said that it's a pretty autonomous region. What could be more natural than for them to have a flag?
I have to admit though, that I do support de jure independence.