If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#421
|
|||
|
|||
[OT] Apple registered developers
nospam writes:
In article , Mark Lloyd wrote: so what? if a developer can't be bothered to pay $99 to become a registered developer then their software isn't worth using. That sounds like nonsense. Willingness to pay $99 (provide personal information, and "agree" to some legal junk few can even understand) has nothing to do with their quality of software. why should users trust *anything* from a developer who refuses to provide information about themselves? if a developer can't be bothered to become a registered developer, then they're not serious about their product. Well, there're developers that I trust more than Apple. Some even participate in one of the Newsgroups: listed. (Why, if Apple would register with them, I may consider running Apple software.) but it's not required. anyone can anything and release it in the wild but don't be surprised if very few people bother running it without knowing something about who wrote it or choose a more reputable developer. The authors of WRF (below) look reputable enough. Since you seem to be experienced with Apple products, could you please check if they're registered? Also for CORSIKA, if that's not much trouble. TIA. http://www.mmm.ucar.edu/weather-rese...ecasting-model The effort to develop WRF began in the latter part of the 1990's and was a collaborative partnership of the National Center for Atmospheric Research (NCAR), the National Oceanic and Atmospheric Administration (represented by the National Centers for Environmental Prediction (NCEP) and the (then) Forecast Systems Laboratory (FSL)), the (then) Air Force Weather Agency (AFWA), the Naval Research Laboratory, the University of Oklahoma, and the Federal Aviation Administration (FAA). http://ikp.kit.edu/corsika/ -- FSF associate member #7257 np. If Eternity Should Fail -- Iron Maiden |
Ads |
#422
|
|||
|
|||
Unless they've changed it with the move to OSX... (Was: With DaaS Windows Coming, Say Goodbye To Your PC As You Know It)
In article , The Natural Philosopher
wrote: Anyway the point is that a macinstosh data 'file' be it a single entity with two forks internal to HFS or two files as mapped onto any other file system is INCOMPATIBLE with any other opearting system's understanding of a 'file'. I am not concerned with its ultimate representation, just as an example of Apples unconcerned indiffenece to interoperability with others. What the hell are you talking about?! Copying files between macOS, windows and linux is just fine regardless of the source and destination. A pdf or jpeg file is always a pdf or jpeg. Try an image file or a font file jpegs *are* image files, and fonts are not an issue at all. |
#423
|
|||
|
|||
With DaaS Windows Coming, Say Goodbye To Your PC As You Know It
In article , The Natural Philosopher
wrote: I think you're describing metadata files. Finder does this to store information about a file (e.g. thumbnail versions of images). Other OSes do the same, but may store it in different places. They are disposable and are recreated by the Finder if required. Nope. Fonts for example use the metadata to store vital info. nope. So do images in some cases. image metadata, known as exif and a part of images from digital cameras, is stored in the *data* fork, although not all image formats support exif data. nothing is lost when copying images with exif data between platforms. |
#424
|
|||
|
|||
Unless they've changed it with the move to OSX... (Was: With DaaS Windows Coming, Say Goodbye To Your PC As You Know It)
In article , The Natural Philosopher
wrote: Anyway the point is that a macinstosh data 'file' be it a single entity with two forks internal to HFS or two files as mapped onto any other file system is INCOMPATIBLE with any other opearting system's understanding of a 'file'. I am not concerned with its ultimate representation, just as an example of Apples unconcerned indiffenece to interoperability with others. What the hell are you talking about?! Copying files between macOS, windows and linux is just fine regardless of the source and destination. A pdf or jpeg file is always a pdf or jpeg. yep. there are no issues. https://blog.jay2k1.com/2010/02/03/w...h-fonts-from-s mb-shares/ So, you are lying. There are SERIOUS issuess. no there aren't. the author of that article is clueless and would rather blame apple than admit he doesn't know what he's doing, much like you. macs use various industry standard font types, including truetype and opentype, without resource forks and has been the case for around 20 years, perhaps longer. there are *no* issues in copying fonts between macs and other systems, unless of course, the person doing the copying is inept. in fact, many web sites use custom fonts with their pages without any issues for mac or windows users. https://www.w3schools.com/css/css3_fonts.asp |
#425
|
|||
|
|||
Unless they've changed it with the move to OSX... (Was: With DaaSWindows Coming, Say Goodbye To Your PC As You Know It)
On 08/08/18 14:17, nospam wrote:
In article , The Natural Philosopher wrote: Anyway the point is that a macinstosh data 'file' be it a single entity with two forks internal to HFS or two files as mapped onto any other file system is INCOMPATIBLE with any other opearting system's understanding of a 'file'. I am not concerned with its ultimate representation, just as an example of Apples unconcerned indiffenece to interoperability with others. What the hell are you talking about?! Copying files between macOS, windows and linux is just fine regardless of the source and destination. A pdf or jpeg file is always a pdf or jpeg. yep. there are no issues. https://blog.jay2k1.com/2010/02/03/w...h-fonts-from-s mb-shares/ So, you are lying. There are SERIOUS issuess. no there aren't. the author of that article is clueless and would rather blame apple than admit he doesn't know what he's doing, much like you. macs use various industry standard font types, including truetype and opentype, without resource forks and has been the case for around 20 years, perhaps longer. there are *no* issues in copying fonts between macs and other systems, unless of course, the person doing the copying is inept. in fact, many web sites use custom fonts with their pages without any issues for mac or windows users. https://www.w3schools.com/css/css3_fonts.asp Well managed a mac for 5 years and I had all these issues as decribed. Its very easy to sit there and say 'stupid' to anyone who even hints that the Great Jobs might have ****ed things up. -- Truth welcomes investigation because truth knows investigation will lead to converts. It is deception that uses all the other techniques. |
#426
|
|||
|
|||
Unless they've changed it with the move to OSX... (Was: With DaaSWindows Coming, Say Goodbye To Your PC As You Know It)
On 08/08/18 14:17, nospam wrote:
In article , The Natural Philosopher wrote: Anyway the point is that a macinstosh data 'file' be it a single entity with two forks internal to HFS or two files as mapped onto any other file system is INCOMPATIBLE with any other opearting system's understanding of a 'file'. I am not concerned with its ultimate representation, just as an example of Apples unconcerned indiffenece to interoperability with others. What the hell are you talking about?! Copying files between macOS, windows and linux is just fine regardless of the source and destination. A pdf or jpeg file is always a pdf or jpeg. Try an image file or a font file jpegs *are* image files, and fonts are not an issue at all. Oh dear. Just TRY it. Apple style Fonts store ALL the information in the resource fork. You cannot copy a font file off a mac - you only get the data fork, which is empty. And a hidden resource fork. -- Truth welcomes investigation because truth knows investigation will lead to converts. It is deception that uses all the other techniques. |
#427
|
|||
|
|||
Unless they've changed it with the move to OSX... (Was: With DaaSWindows Coming, Say Goodbye To Your PC As You Know It)
On 08/08/2018 08:05 AM, The Natural Philosopher wrote:
On 08/08/18 14:17, nospam wrote: In article , The Natural Philosopher wrote: Anyway the point is that a macinstosh data 'file' be it a single entity with two forks internal to HFS or two files as mapped onto any other file system is INCOMPATIBLE with any other opearting system's understanding of a 'file'. I am not concerned with its ultimate representation, just as an example of Apples unconcerned indiffenece to interoperability with others. What the hell are you talking about?! Copying files between macOS, windows and linux is just fine regardless of the source and destination. A pdf or jpeg file is always a pdf or jpeg. yep. there are no issues. https://blog.jay2k1.com/2010/02/03/w...h-fonts-from-s mb-shares/ So, you are lying. There are SERIOUS issuess. no there aren't. the author of that article is clueless and would rather blame apple than admit he doesn't know what he's doing, much like you. macs use various industry standard font types, including truetype and opentype, without resource forks and has been the case for around 20 years, perhaps longer. there are *no* issues in copying fonts between macs and other systems, unless of course, the person doing the copying is inept. in fact, many web sites use custom fonts with their pages without any issues for mac or windows users. https://www.w3schools.com/css/css3_fonts.asp Well managed a mac for 5 years and I had all these issues as decribed. Its very easy to sit there and say 'stupid' to anyone who even hints that the Great Jobs might have ****ed things up. Actually with his alternative medicine choices he ****ed himself up to a Terminal condition. Why should he be better at the practical aspects of computing? His was the Grand Vision of an information appliance in many users' hands, the iPhones, the iPads and so forth. And he arranged the harvesting of money and information from every device from Apple. Great man? Sure but so was Howard Hughes. Elon Musk is a greater man as far as helping the human race. IMHO bliss -- bliss dash SF 4 ever at dslextreme dot com |
#428
|
|||
|
|||
Unless they've changed it with the move to OSX... (Was: With DaaS Windows Coming, Say Goodbye To Your PC As You Know It)
In article , Bobbie Sellers
wrote: Its very easy to sit there and say 'stupid' to anyone who even hints that the Great Jobs might have ****ed things up. Actually with his alternative medicine choices he ****ed himself up to a Terminal condition. maybe. nobody knows what would have happened had he chose a different course. Why should he be better at the practical aspects of computing? one has nothing to do with the other. His was the Grand Vision of an information appliance in many users' hands, the iPhones, the iPads and so forth. that part is true. And he arranged the harvesting of money and information from every device from Apple. that part is very definitely not true. google, on the other hand, gets nearly all of its revenue from data mining and monetizing users, regardless of what device is used, or even if the user disables location services. https://qz.com/1131515/google-collec...tions-even-whe n-location-services-are-disabled/ Since the beginning of 2017, Android phones have been collecting the addresses of nearby cellular towers‹even when location services are disabled‹and sending that data back to Google. Great man? Sure but so was Howard Hughes. Elon Musk is a greater man as far as helping the human race. except when he tweets. https://www.usatoday.com/story/tech/.../elon-musk-tha i-cave-rescue-diver-pedophile-twitter/786527002/ Tesla CEO Elon Musk is taking heat*for calling British diver*Vern*Unsworth, who helped orchestrate the Thai cave rescue,*a 'pedo' on Twitter Sunday. |
#429
|
|||
|
|||
Unless they've changed it with the move to OSX... (Was: With DaaS Windows Coming, Say Goodbye To Your PC As You Know It)
In article , The Natural Philosopher
wrote: Anyway the point is that a macinstosh data 'file' be it a single entity with two forks internal to HFS or two files as mapped onto any other file system is INCOMPATIBLE with any other opearting system's understanding of a 'file'. I am not concerned with its ultimate representation, just as an example of Apples unconcerned indiffenece to interoperability with others. What the hell are you talking about?! Copying files between macOS, windows and linux is just fine regardless of the source and destination. A pdf or jpeg file is always a pdf or jpeg. yep. there are no issues. https://blog.jay2k1.com/2010/02/03/w...with-fonts-fro m-smb-shares/ So, you are lying. There are SERIOUS issuess. no there aren't. the author of that article is clueless and would rather blame apple than admit he doesn't know what he's doing, much like you. macs use various industry standard font types, including truetype and opentype, without resource forks and has been the case for around 20 years, perhaps longer. there are *no* issues in copying fonts between macs and other systems, unless of course, the person doing the copying is inept. in fact, many web sites use custom fonts with their pages without any issues for mac or windows users. https://www.w3schools.com/css/css3_fonts.asp Well managed a mac for 5 years and I had all these issues as decribed. then you also don't know what you're doing. just because you supposedly managed 'a mac' doesn't mean much of anything. Its very easy to sit there and say 'stupid' to anyone who even hints that the Great Jobs might have ****ed things up. it's even easier to say stupid to someone who demonstrates incompetence. how is it that users (other than you) can copy fonts between macs, windows and unix without any issues? how is it that there are web sites that offer fonts for download that work on mac, windows and unix, also without issues? also, the resource fork was not a ****up. it was an incredibly good idea, one which microsoft copied but intentionally made it incompatible, as they do with a lot of things. |
#430
|
|||
|
|||
Unless they've changed it with the move to OSX... (Was: With DaaS Windows Coming, Say Goodbye To Your PC As You Know It)
In article , The Natural Philosopher
wrote: Anyway the point is that a macinstosh data 'file' be it a single entity with two forks internal to HFS or two files as mapped onto any other file system is INCOMPATIBLE with any other opearting system's understanding of a 'file'. I am not concerned with its ultimate representation, just as an example of Apples unconcerned indiffenece to interoperability with others. What the hell are you talking about?! Copying files between macOS, windows and linux is just fine regardless of the source and destination. A pdf or jpeg file is always a pdf or jpeg. Try an image file or a font file jpegs *are* image files, and fonts are not an issue at all. Oh dear. Just TRY it. i have. works perfectly fine. Apple style Fonts store ALL the information in the resource fork. You cannot copy a font file off a mac - you only get the data fork, which is empty. And a hidden resource fork. nonsense. it's trivial to copy fonts to/from macs without any issues whatsoever. mac fonts haven't used resource forks in at least 20 years, and back then, it was easy to convert them if needed, in either direction. also keep in mind that copying windows fonts to other systems doesn't always work either. |
#431
|
|||
|
|||
With DaaS Windows Coming, Say Goodbye To Your PC As You Know It
In comp.os.linux.misc Dan Purgert wrote:
Seems a bit odd that setting up multi-arch (or your distro's variant thereto) isn't a possibility. Or has it simply not been tested? I have tried this. Perhaps you might be able to help me with it? My feeble expertise comes from a strong desire to use WordPerfect in places that it wasn't designed to run, rather than any real Linux expertise. I did try to follow Peter Stone's XWP (WordPerfect for Linux) install instructions. I'm running 64-bit Linux Mint 18.1. All of the legacy libraries install, exept for when I get to the package type1inst_0.6.1-6_i386.deb Unfortunately it gives the error: Cannot install 'perl:i386' Because of this error, I'm currently forced to run XWP inside a 32-bit Linux Mint 13 virtual machine. I regret that I didn't select a 32-bit version of Linux Mint to install from the outset as it would have saved me a lot of problems. Thanks for your insights, David B. |
#432
|
|||
|
|||
By any other name...
In comp.os.linux.misc Kenny McCormack wrote:
In article , David B wrote: ... I have used WordPerfect on a Linux machine for a number of years. There are four ways of doing this, none of which use WINE. ... 2) Use PC WordPerfect 12 under Crossover. Everything works except macros. Crossover *is* Wine, pretty much. Of course you are entirely correct. From my limited point of view, the difference is that Crossover costs money (and will run WP 12), but the no fee version of Wine will not run any variant of WordPerfect in acceptable fashion. I don't really know much about Wine or how it works, but I guess this key difference is why Crossover costs money. |
#433
|
|||
|
|||
With DaaS Windows Coming, Say Goodbye To Your PC As You Know It
David B wrote:
In comp.os.linux.misc Dan Purgert wrote: Seems a bit odd that setting up multi-arch (or your distro's variant thereto) isn't a possibility. Or has it simply not been tested? I have tried this. Perhaps you might be able to help me with it? My feeble expertise comes from a strong desire to use WordPerfect in places that it wasn't designed to run, rather than any real Linux expertise. I did try to follow Peter Stone's XWP (WordPerfect for Linux) install instructions. I'm running 64-bit Linux Mint 18.1. All of the legacy libraries install, exept for when I get to the package type1inst_0.6.1-6_i386.deb Unfortunately it gives the error: Cannot install 'perl:i386' What was the link again? Google-fu isn't strong today it seems. Two things to check: 1. Is multiarch actually enabled? You can check with the command dpkg --print-foreign-architectures 2. Is apt actually able to install all the required sources? You can check this by trying to install perl all by itself. Sometimes what happens is that the i386 and x86_64 binaries are mutually-exclusive though, and if it's choking on perl, this may be the case. Sometimes though, it's just an issue of the package being daft, and you have to manually resolve its dependencies ... or skip out on the "packaged" version and add the 32-bit perl libs yourself, and essentially workaround the issue all over again. This link, while it's talking about centos, would still apply (i.e. using CPAN). However, I'm not sure if it'll fix your problems -- it really depends on what's crying about dependencies. https://superuser.com/questions/6271...-server/629474 -- |_|O|_| Registered Linux user #585947 |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5 4AEE 8E11 DDF3 1279 A281 |
#434
|
|||
|
|||
[OT] Apple registered developers
On 08/08/2018 14:00, Ivan Shmakov wrote:
nospam writes: In article , Mark Lloyd wrote: so what? if a developer can't be bothered to pay $99 to become a registered developer then their software isn't worth using. That sounds like nonsense. Willingness to pay $99 (provide personal information, and "agree" to some legal junk few can even understand) has nothing to do with their quality of software. why should users trust *anything* from a developer who refuses to provide information about themselves? if a developer can't be bothered to become a registered developer, then they're not serious about their product. Well, there're developers that I trust more than Apple. Some even participate in one of the Newsgroups: listed. (Why, if Apple would register with them, I may consider running Apple software.) but it's not required. anyone can anything and release it in the wild but don't be surprised if very few people bother running it without knowing something about who wrote it or choose a more reputable developer. The authors of WRF (below) look reputable enough. Since you seem to be experienced with Apple products, could you please check if they're registered? Also for CORSIKA, if that's not much trouble. Neither requires registration as the software is distributed as source code which requires compiling on the target system. In theory, as they're FORTRAN and/or C code designed for UNIX systems there's a good chance they will work on a Mac. I can't tell for sure as the authors of both tools require you to register to download the code. |
#435
|
|||
|
|||
By any other name...
In article , David B wrote:
In comp.os.linux.misc Kenny McCormack wrote: In article , David B wrote: ... I have used WordPerfect on a Linux machine for a number of years. There are four ways of doing this, none of which use WINE. ... 2) Use PC WordPerfect 12 under Crossover. Everything works except macros. Crossover *is* Wine, pretty much. Of course you are entirely correct. From my limited point of view, the difference is that Crossover costs money (and will run WP 12), but the no fee version of Wine will not run any variant of WordPerfect in acceptable fashion. It'd be interesting to know why. I don't really know much about Wine or how it works, but I guess this key difference is why Crossover costs money. You probably know more about it than I do. I don't have much experience with Wine, though I've dabbled with it off and on over the years. Haven't ever tried to run WP under it... -- The difference between communism and capitalism? In capitalism, man exploits man. In communism, it's the other way around. - Daniel Bell, The End of Ideology (1960) - |
Thread Tools | |
Display Modes | Rate This Thread |
|
|