Jump to content

Talk:Adobe Document Cloud

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
(Redirected from Talk:Acrobat.com)

Adobe documentation problem

[edit]

Hi, everyone

While I was ensuring consistency in Acrobat.com article I encountered a few issues with file extensions quoted. A number of very strange extensions, which have included below, are listed in Acrobat.com FAQ which is used as the primary source for this article. These strange file extensions look invalid. Unfortunately, at this time, I am unable to connect to Acrobat.com (I still don't know why), so I'm unable to investigate their validity.

For encyclopedic accuracy, it is imperative that we investigate these issues and clarify them with credible sources. Here is the problems that I have encountered.

Acrobat.com FAQ states:

But what is this PRJ file format? Which Microsoft Office product uses .prj files? (It is definitely not a Microsoft Project file extension: The file extension of Microsoft Project is .mpp, as stated in that article.) Furthermore, I visited http://filext.com/file-extension/PRJ Filext.com and http://www.file-extensions.org/prj-file-extension but these web pages also do not list .prj as a Microsoft Office file extension. Even Microsoft does not recognize this file format: http://shell.windows.com/fileassoc/0409/xml/redir.asp?Ext=prj


Now in this statement, multiple questionable file extensions are listed:

  • VB:
    VB is listed twice as an executable file. However, VB is the file extension of Visual Basic source code. It is a harmless text and cannot be executed or inflict any harm, unless compiled with Visual Basic. But didn't Adobe mean to list VBS and VBE instead? VBS and VBE are the file extensions of VBScript and may be executed when double-clicked.
  • WS:
    WS is not an executable file in Microsoft Windows but WSF and WSC are. See Windows Scripting Host
  • MS:
    MS is also not an executable file but MSI and MSP are. See Windows Installer
  • CRT, INS and ISP
    These files are listed as executable or system. But are these? These files are totally alien to me and Wikipedia has no article about them.
  • REGT::
    This file listed as a video type but is is? I found nothing about this file type in Wikipedia, filext.com or file-extensions.org.

If anyone has a secondary source about Adobe Share and Adobe PDF Create format support, please let us know. Fleet Command (talk) 10:33, 21 August 2009 (UTC)[reply]

That is most peculiar...they usually don't make such mistakes...especially in FAQs.Smallman12q (talk) 02:07, 18 October 2009 (UTC)[reply]

Acrobat.com

[edit]

Fix the sources! — Preceding unsigned comment added by Rolandhelper (talkcontribs) 12:35, 7 June 2012 (UTC)[reply]

Why don't you add third part, independent, and reliable references? Be Bold! mabdul 17:13, 7 June 2012 (UTC)[reply]

File:Adobe CreatePDF.png Nominated for speedy Deletion

[edit]

An image used in this article, File:Adobe CreatePDF.png, has been nominated for speedy deletion for the following reason: Wikipedia files with no non-free use rationale as of 12 June 2012

What should I do?

Don't panic; you should have time to contest the deletion (although please review deletion guidelines before doing so). The best way to contest this form of deletion is by posting on the image talk page.

  • If the image is non-free then you may need to provide a fair use rationale
  • If the image isn't freely licensed and there is no fair use rationale, then it cannot be uploaded or used.
  • If the image has already been deleted you may want to try Deletion Review

To take part in any discussion, or to review a more detailed deletion rationale please visit the relevant image page (File:Adobe CreatePDF.png)

This is Bot placed notification, another user has nominated/tagged the image --CommonsNotificationBot (talk) 12:27, 12 June 2012 (UTC)[reply]

Conflict of interest

[edit]

Half this article was written by Adobe employees User:CHubbardAdobe — Preceding unsigned comment added by 93.136.101.103 (talk) 00:24, 4 October 2017 (UTC)[reply]