Slashdot Mirror


User: Quila

Quila's activity in the archive.

Stories
0
Comments
3,975
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 3,975

  1. Re:BitTorrent on Local Area Security Linux LiveCD · · Score: 1

    Whole, skim or low-fat?

  2. BitTorrent on Local Area Security Linux LiveCD · · Score: 0

    When I get home I'll download and see if I can set up a tracker and post a torrent somewhere.

  3. Seen it on No EZ Fix For The IRS · · Score: 1

    I did a thing on IRS IT modernization in college in the mid-90s, and it was about the same story back then. Nothing new, really. Any company that actually manages to modernize the IRS deserves a $20 billion fee.

    Of course we could just abolish the IRS and solve the problem rather cheaply.

  4. Re:Lindos.com on Lindows Agreeing to Change Name · · Score: 1

    OTOH, they also updated their other domains, and haven't extended the registration of Lindos.com to as far out as Lindows.com, so they've likely not settled on it yet.

  5. Lindos.com on Lindows Agreeing to Change Name · · Score: 1

    They've already registered lindos.com with no site up, and have recently updated it, so I'd say Lindos is in the running. But unfortunately, Lindos.xx where xx=various country codes is already taken.

  6. Sand Sand Sand on The Worst Development Job You've Ever Had? · · Score: 1

    There aren't enough bottles of compressed air in the world to blow the sand out of the PCs in the backs of the trucks and the tents in the Arabian deserts. Finally scrounged up a hose to hook up to the compressed air tanks of a 5-ton truck.

    Fast forward a bit over 10 years and this time we remember to bring a compressor. Probably a good idea since these new Pentiums run a bit hotter than the 286s we had the first time.

  7. Re:Double-rubbish on Why You Should Choose MS Office Over OO.org · · Score: 1
    Yes, just saying it's XML is uselsess. They could do the following and still claim a Word document is XML compliant, with a published DTD:
    <?xml version="1.0" encoding="ISO8859-1" ?>
    <!DOCTYPE worddoc [
    <!ELEMENT content (#CDATA)>
    ]>
    <worddoc>
    <content>[character representation of closed binary doc format here]</content>
    </worddoc>
  8. Re:Some real reasons not to use OpenOffice... on Why You Should Choose MS Office Over OO.org · · Score: 1

    Publisher is desktop publishing. The Open Source equivalent for that is Scribus.

  9. Open Office is now officially ready for prime time on Why You Should Choose MS Office Over OO.org · · Score: 1

    As happened with Linux, you know you're ready for prime time as soon as Microsoft breaks out the FUD machine for your product.

  10. Re:Adobe is killing FrameMaker, entirely. on Adobe Kills FrameMaker for Mac · · Score: 1

    Nice ligatures, but that comma intersecting the K swash is annoying.

  11. XML on Why You Should Choose MS Office Over OO.org · · Score: 4, Informative

    I love it. They touted Office's lip service to XML as an advantage, forgetting that OO's internal file format is pure XML with an open published DTD. A decent programmer can make software to read and repurpose an OO document with 100% accuracy.

    Anyone with knowledge of both can blow away most of these arguments. However, some do have merit in certain circumstances.

  12. Re:Jobs need new Strategy on Adobe Kills FrameMaker for Mac · · Score: 1

    Then you must have been to one I was in. When I left that one we were running PM 6.5, Photoshop 5 and Illustrator 8 on Windows 98/2000. The platform wasn't a limiting factor on what went to our Heidelberg presses. However, our imagesetter was crap so we had to outsource for quality color separations because management wouldn't spring for a better imagesetter (ours was good enough for the rest of the work).

    But at least that way I got lots of cool gifts from the service bureau we used.

  13. Re: Adobe on Adobe Kills FrameMaker for Mac · · Score: 1

    But even there, they "shine" primarily because Quark dropped the ball and took so LONG

    Interestingly, relative upstart Quark is only where it is because Aldus dropped the ball on PageMaker for several years.

  14. Re:I don't think this is the first time... on Adobe Kills FrameMaker for Mac · · Score: 1

    Pagemaker: Executive Secretary and home stuff

    Sad thing is that PageMaker was almost up to par with Quark, and even beat it in areas, before Adobe decided to rename the upcoming PageMaker 7 to InDesign. PageMaker's name could have lived on as the premier DTP app it has been at times in history, but is instead relegated to secretary and home use in the marketplace (although I do know many who still use it for pro publishing).

  15. Re:I don't think this is the first time... on Adobe Kills FrameMaker for Mac · · Score: 1

    that Adobe has puchased a competitor and then killed off the competing product. Didn't they do the same thing with PageMaker?


    No, Adobe bought out Aldus, sold Freehand to Macromedia because they already had Illustrator, and went ahead with improving PageMaker as their page layout product. PM7 is worlds better than the PM5 of Aldus days.

  16. Re:...is it really a problem? on Adobe Kills FrameMaker for Mac · · Score: 1

    It's all about multiple channels and masks, proper color profile support and things like channel mixing and calculations which no other program can do.

    Add 16 bpp color and certified PANTONE and HKS matching, although the latter is really only a question of copyright. But if you work with PANTONE or HKS you can afford Photoshop and the bit of the price that goes to license PANTONE and HKS.

  17. Re:Let it die. on Adobe Kills FrameMaker for Mac · · Score: 1

    Why the hell are you importing Acrobat files into a document? An Acrobat file is an end-product, not an exchange format.

    Although for his specific case it appears you may be right, trying to import a multi-page document into Frame, Acrobat is a good exchange format. It's practically industry standard for moving ads and other stuff among publishers and companies to be included in other documents.

  18. Re:Adobe is killing FrameMaker, entirely. on Adobe Kills FrameMaker for Mac · · Score: 1

    A lot of this is why I think they should make a version of InDesign for long documents. It doesn't yet do the cool document structure and head stuff like Tex or even Frame, but:

    Automatic ligatures: Done, with automatic ligature substitution.

    H&J: Not only controlled by paragraph styles, but will also run back through the entire paragraph to get the "color" right. It will adjust a break on line 2 and watch the effects cascade in order to try to fix a bad line 23. To help things, you can specify a lot of factors in hyphenation decisions and allowable letter spacing ranges. It will also hyphenate in most popular languages out of the box.

    Baseline shifting: Of course, extremely fine.

    Plus optical kerning and optical margin alignment with hanging punctuation can in cases give a very clean look to the paragraphs (like how normally a hyphen in fully justified text leaves an indentation in the block).

  19. Re:Adobe is killing FrameMaker, entirely. on Adobe Kills FrameMaker for Mac · · Score: 1

    They said that the core code is such a mess, they couldn't find any programmers willing or talented enough to make sense of it.

    That's the same problem they had with PageMaker. It was written in different languages, even some using custom Aldus development tools. Plus, the structure of the database that constitutes a document was hopelessly broken. Nobody wanted to touch that stuff.

  20. Re:Adobe is killing FrameMaker, entirely. on Adobe Kills FrameMaker for Mac · · Score: 1

    Adobe decided to replace PageMaker with InDesign when PageMaker wasn't that old.

    PageMaker was pretty old, but only recently acquired by Adobe just prior to version 6. InDesign was supposed to be PageMaker 7 rewritten from the ground up to overcome various architectural problems with PM, but the stigma of the PageMaker name in many DTP circles made them pick a new name. Since they had a new name, and therefore a new product, they decided to keep PM around, slap some templates and such on it, and market it against Publisher and the like.

    I don't see InDesign integrating FrameMaker's features. InDesign is not a word processor.

    I see it coming. InDesign is built on a small core framework, with everything including text composition and color being a plugin. Repurposing InDesign to long document work shouldn't be hard within that framework.

  21. Re:slashbot on New Documents Shed Light on Microsoft's Tactics · · Score: 1

    For Netscape, add that they messed with DLLs so that Netscape wouldn't work anymore.

  22. Re:Insane or bought? Or is there another option? on MS Word File Reveals Changes to SCO's Plans · · Score: 1

    One possibility is that they're buying licenses so that SCO can be nailed for fraud when its case for owning Linux folds. Not likely, but it makes me smile.

  23. Illegal? on Microsoft Warning Leaked Code Traders · · Score: 1

    warning them that playing peek-a-boo with the four year old code is a violation of the law.

    IANAL, but I'm not sure this is illegal. I don't think receiving copyrighted work is illegal, although distributing without license is. I also don't know how simply reading the code could be a copyright violation.

    Someone help me out on what laws could be violated by downloading and looking. Although I have no interest in seeing it myself, I'd like to know the legal angles.

  24. Re:So is this one on U.S. Representatives Torpedo UN Information Summit · · Score: 1

    Because your post seemed to refer to it as a closed example that needs to be open.

  25. So is this one on U.S. Representatives Torpedo UN Information Summit · · Score: 1

    if a PDF reader is bought from Adobe, there must be a way to read PDF files even if Adobe goes under and the software becomes unavailable for the new machines, possibly for a different OS in a few years. PDF should be an open standard, at minimum,

    PDF is an open format. The specs are there for anyone to write his own reader or writer. I agree with your point, but you picked a bad example.