* Systems based on ASCII or a compatible character set use either LF (Line Feed, 0x0A) or CR (Carriage Return, 0x0D) individually, or CR followed by LF (CR+LF, 0x0D 0x0A).
o LF: Unix and Unix-like systems, Linux, AIX, Xenix, Mac OS X, BeOS, Amiga, RISC OS and others
o CR+LF: CP/M, MP/M, DOS, Microsoft Windows
o CR: Apple II family and Mac OS through version 9
* EBCDIC systems--mainly IBM mainframe systems, including z/OS (OS/390), i5/OS (OS/400)--use NEL (Next Line, 0x15) as the newline character. Note that EBCDIC also has control characters called CR and LF, but the numerical value of LF differs from the one used by ASCII. Additionally, there are some EBCDIC variants that also use NEL but assign a different numeric code to the character.
* OpenVMS uses a record-based file system and stores text files as one record per line. No line terminators are actually stored, but the system can transparently add a terminator to each line when it is retrieved by an application.
Most textual Internet protocols (including HTTP, SMTP, FTP, IRC and many others) mandate the use of ASCII CR+LF (0x0D 0x0A) on the protocol level, but recommend that tolerant applications recognize lone LF as well. In practice, there are many applications that erroneously use the C newline character '\n' instead (see section Newline in programming languages below). This leads to problems when trying to communicate with systems adhering to a stricter interpretation of the standards; one such system is the qmail MTA that actively refuses to accept messages from systems that send bare LF instead of the required CR+LF.
16 bit per channel is under development for gimp as I remember to have read somewhere.
Stolen somewhere:
Re:16 bits per channel (Score:0) By Anonymous Reader on 2005.10.05 14:38 (#118545) The problem is not to be able to see a difference between images with 8 and 16 bits per channel.
The problem is that 8 bits postprocessing is less accurate.
For example, if one of your photos is partly underexposed then you probably want to raise the luminosity in the shadows.
If your image is 8 bits (256 levels), the shadows will provide, let's say, 10 levels of 'gray' to play with. This is not a lot and the result is likely to be crap (and noisy).
Now, if your digital camera provides 16bit per channel then the same shadows will provide 2500 levels to plays with. That's a hell of a difference.
Most digital cameras only provide 12bits but 4bit more bits means 16 times more levels to play with.
Anyways, the situation in The Gimp is not so bad for digital camera owners. The UFRAW plugin can load almost any RAW image files. Also, UFRAW allows you to adjust your image (levels, WB,...) using all available bits.
Once loaded, The Gimp has to work in 8bits but that is less of a problem.
"In other words, you want them to break a few laws to give you a Windows clone with some actual Windows parts."
Does my post say that they must do anything at all?
I love linux and it works perfectly for me.
But (just like you) I also get frustrated of criticism regarding linux, and tell people that it's Microsoft's fault that linux doesn't work the way they want it to. The people I love most are extremely headstrong, so the 'microsofts fault' excuse is not accepted by them.
Moving from NTFS to ext3 or Reiser shouldn't require NTFS write support, should it?
Most people I got so far that they want to try linux, don't want to completely rely on this OS that they have never used before. They want to be able to open/write their documents in their trusted environment anytime they feel alienated in the linux environment.
People for who I installed linux, say the following is missing:
Good MSN with all smileys, filetransfer, videochat. Support for all streaming media in your webbrowser. All multimedia files supported (without having to add (unofficial) repositories to have support for win32codecs and such).
Oh yeah, for the transition, full NTFS writing support.
Apart from that, my friends, mother, sister and girlfriend really like linux.
"1) It quickly becomes a collection of files (figures, pictures, diagrams, charts, formulas, etc) which are inconvenient to manage. You have to attach say six different files to your email, or mess around with zipping it up, likewise at the recipient end."
Slashdot Mirror
Is there somebody who has something +5 to say about his?
http://en.wikipedia.org/wiki/Newline
* Systems based on ASCII or a compatible character set use either LF (Line Feed, 0x0A) or CR (Carriage Return, 0x0D) individually, or CR followed by LF (CR+LF, 0x0D 0x0A).
o LF: Unix and Unix-like systems, Linux, AIX, Xenix, Mac OS X, BeOS, Amiga, RISC OS and others
o CR+LF: CP/M, MP/M, DOS, Microsoft Windows
o CR: Apple II family and Mac OS through version 9
* EBCDIC systems--mainly IBM mainframe systems, including z/OS (OS/390), i5/OS (OS/400)--use NEL (Next Line, 0x15) as the newline character. Note that EBCDIC also has control characters called CR and LF, but the numerical value of LF differs from the one used by ASCII. Additionally, there are some EBCDIC variants that also use NEL but assign a different numeric code to the character.
* OpenVMS uses a record-based file system and stores text files as one record per line. No line terminators are actually stored, but the system can transparently add a terminator to each line when it is retrieved by an application.
Most textual Internet protocols (including HTTP, SMTP, FTP, IRC and many others) mandate the use of ASCII CR+LF (0x0D 0x0A) on the protocol level, but recommend that tolerant applications recognize lone LF as well. In practice, there are many applications that erroneously use the C newline character '\n' instead (see section Newline in programming languages below). This leads to problems when trying to communicate with systems adhering to a stricter interpretation of the standards; one such system is the qmail MTA that actively refuses to accept messages from systems that send bare LF instead of the required CR+LF.
Linus Benedict Torvalds
-vs-
Benedict XVI
>> Sure...not at 100000x6800000 resolution
Yeah, that would be a really weird aspect ratio man.
As a nine years old it was damn hard to find out to "use rubber".
Ouch, TTL drop.
It's the positive viewpoint; the glass is half-full.
"The screen on an iPod is also completely devoid of any warantee."
Long live iPod Shuffle
If you use such a structure;
...
...
From TFA:
<section>
<h>Level 1 heading</h>
<section>
<h>Level 2 heading</h>
</section>
</section>
Your can use classes or IDs even.
Good communication is as stimulating as black coffee and just as hard to sleep after. -- Anne Morrow Lindbergh
We need an Ellen Feiss!!!
o vies/ellen_feiss.mov]
[URL:http://ellenfeiss.net/temp/movie.php?movie=m
Like a fighting plane using chaff. :-)
Officials can't confirm, nor deny that companies that are using the OpenDocument format might or might not be influenced by Microsoft.
Wow! Did you just make that up?
8 29992
Or did you read it in my post yesterday?
http://slashdot.org/comments.pl?sid=165780&cid=13
I can imagine, that when it freezes, your pimped & overtuned H2 car leaves behind a trail of snow when you burnout to impress bystanders!
Stolen quote: The great thing about standards is that there are so many to choose from.
There already is.
1. Wait for a good open standard to come out.
2. Embrace.
3. Extend incompatibly.
4. PROFIT!!!
PNG supports lots of bits already. 16 bits per channel. RGBA (red green blue aplha) makes 64 bits per pixel.
http://en.wikipedia.org/wiki/PNG
16 bit per channel is under development for gimp as I remember to have read somewhere.
...) using all available bits.
Stolen somewhere:
Re:16 bits per channel (Score:0)
By Anonymous Reader on 2005.10.05 14:38 (#118545)
The problem is not to be able to see a difference between images with 8 and 16 bits per channel.
The problem is that 8 bits postprocessing is less accurate.
For example, if one of your photos is partly underexposed then you probably want to raise the luminosity in the shadows.
If your image is 8 bits (256 levels), the shadows will provide, let's say, 10 levels of 'gray' to play with. This is not a lot and the result is likely to be crap (and noisy).
Now, if your digital camera provides 16bit per channel then the same shadows will provide 2500 levels to plays with. That's a hell of a difference.
Most digital cameras only provide 12bits but 4bit more bits means 16 times more levels to play with.
Anyways, the situation in The Gimp is not so bad for digital camera owners.
The UFRAW plugin can load almost any RAW image files.
Also, UFRAW allows you to adjust your image (levels, WB,
Once loaded, The Gimp has to work in 8bits but that is less of a problem.
The eight bits he mentioned is eight bits PER COLOUR!
red, green, blue = 3 colours.
3x8=24
"In other words, you want them to break a few laws to give you a Windows clone with some actual Windows parts."
Does my post say that they must do anything at all?
I love linux and it works perfectly for me.
But (just like you) I also get frustrated of criticism regarding linux, and tell people that it's Microsoft's fault that linux doesn't work the way they want it to. The people I love most are extremely headstrong, so the 'microsofts fault' excuse is not accepted by them.
I summed their complaints just FYI.
Moving from NTFS to ext3 or Reiser shouldn't require NTFS write support, should it?
Most people I got so far that they want to try linux, don't want to completely rely on this OS that they have never used before. They want to be able to open/write their documents in their trusted environment anytime they feel alienated in the linux environment.
People for who I installed linux, say the following is missing:
Good MSN with all smileys, filetransfer, videochat.
Support for all streaming media in your webbrowser.
All multimedia files supported (without having to add (unofficial) repositories to have support for win32codecs and such).
Oh yeah, for the transition, full NTFS writing support.
Apart from that, my friends, mother, sister and girlfriend really like linux.
"1) It quickly becomes a collection of files (figures, pictures, diagrams, charts, formulas, etc) which are inconvenient to manage. You have to attach say six different files to your email, or mess around with zipping it up, likewise at the recipient end."
tar or tar.gz will do the job.
It will be a matter of years untill the 'BSD trolls are dying posts' are dying.