Downloads:
36
Downloads of v 1.0.0:
36
Last Update:
02 May 2024
Published Date:
02 May 2024
Reviewed Date:
02 May 2024
Reviewer:
Package Maintainer(s):
Software Author(s):
- Aretex Developers
Tags:
document toolkit utility convert- Software Specific:
- Software Site
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
PDFToolkit (Install)
(Maintainer updated, waiting for Reviewer)
- 1
- 2
- 3
1.0.0 | Updated: 02 May 2024
- Software Specific:
- Software Site
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
36
Downloads of v 1.0.0:
36
Published:
02 May 2024
Reviewed:
02 May 2024
Reviewer:
Maintainer(s):
Software Author(s):
- Aretex Developers
PDFToolkit (Install) 1.0.0
(Maintainer updated, waiting for Reviewer)
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
This version is in moderation and has not yet been approved. This means it doesn't show up under normal search.
- Until approved, you should consider this package version unsafe - it could do very bad things to your system (it probably doesn't but you have been warned, that's why we have moderation).
- This package version can change wildly over the course of moderation until it is approved. If you install it and it later has changes to this version, you will be out of sync with any changes that have been made to the package. Until approved, you should consider that this package version doesn't even exist.
- You cannot install this package under normal scenarios. See How to install package version under moderation for more information.
- There are also no guarantees that it will be approved.
There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.
This tool is intended to convert documents from other document type.
$packageName = 'PDFToolkit'
$ErrorActionPreference = 'Stop'; # stop on all errors
$packageArgs = @{
packageName = $packageName
softwareName = 'PDFToolkit*' # part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
fileType = 'MSI' # only one of these: MSI or EXE (ignore MSU for now)
# MSI
silentArgs = "/qn /norestart"
validExitCodes= @(0, 3010, 1605, 1614, 1641) # https://msdn.microsoft.com/en-us/library/aa376931(v=vs.85).aspx
}
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']
if ($key.Count -eq 1) {
$key | % {
$uninstallString = "$($_.UninstallString)"
$executablePath = $uninstallString.Split(' ')[0] # Extract the executable path from the UninstallString
if ($packageArgs['fileType'] -eq 'MSI') {
$packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
$packageArgs['file'] = ''
} else {
$packageArgs['file'] = $executablePath
}
Uninstall-ChocolateyPackage @packageArgs
}
} elseif ($key.Count -eq 0) {
Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
Write-Warning "$($key.Count) matches found!"
Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
Write-Warning "Please alert package maintainer the following keys were matched:"
$key | % {Write-Warning "- $($_.DisplayName)"}
}
PDFTOOLKIT
Version 1.0.0
Copyright (c) 2024 Aretex
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
md5: 72EAB9A46203A728452A9C06012CEB25 | sha1: 5713DF257F38B96383163355C2D126A5404E7D1E | sha256: 5E7D8F8D02FD69D0D19A4B9A3F2F0686B9B9F39EF5BDA638F434378F3F962FD9 | sha512: F171B96811B44F54B5568971579A5610DCE3F0E95726BA1C02C2A9FAC049229F2F5766B55308E1A5E31195ACE915EA83BA41E18245D4A68C1BC5905CAE48CB7A
VERIFICATION
Verification is intended to assist users in verifying that the embedded file is identical to the version available for download from the original site.
To independently verify the integrity of the embedded file, follow these steps:
1. Download the original file from the official website or source where it is provided. https://github.com/aretexit/PDF-Toolkit-Design/releases
2. Calculate the checksum/hash of the downloaded original file. You can use tools like `md5sum`, `sha256sum`, or similar utilities to generate the checksum.
3. Compare the checksum/hash of the downloaded original file with the checksum/hash provided for the embedded file.
4. If the checksums/hashes match, it indicates that the embedded file is identical to the original file available for download.
5. If the checksums/hashes do not match, there may be differences between the embedded file and the original file. Please contact the provider for clarification or obtain the file from the official source again.
It is recommended to verify the integrity of the embedded file before use to ensure authenticity and reliability.
Log in or click on link to see number of positives.
- PDFToolkitInstall.MSI (d3064365d578) - ## / 54
- PDFToolkitInstall.MSI (5e7d8f8d02fd) - ## / 59
- pdftoolkit.1.0.0.nupkg (537df6b998dd) - ## / 57
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
This package has no dependencies.
Ground Rules:
- This discussion is only about PDFToolkit (Install) and the PDFToolkit (Install) package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or PDFToolkit (Install), or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
ImChloeLazaro (maintainer) on 24 Apr 2024 02:50:49 +00:00:
User 'ImChloeLazaro' (maintainer) submitted package.
chocolatey-ops (reviewer) on 24 Apr 2024 03:25:56 +00:00:
pdftoolkit has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl
, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
ImChloeLazaro (maintainer) on 24 Apr 2024 03:34:29 +00:00:
User 'ImChloeLazaro' (maintainer) submitted package.
chocolatey-ops (reviewer) on 24 Apr 2024 04:06:54 +00:00:
pdftoolkit has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl
, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
ImChloeLazaro (maintainer) on 24 Apr 2024 04:52:31 +00:00:
User 'ImChloeLazaro' (maintainer) submitted package.
chocolatey-ops (reviewer) on 24 Apr 2024 05:24:10 +00:00:
pdftoolkit has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl
, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
ImChloeLazaro (maintainer) on 24 Apr 2024 05:27:43 +00:00:
User 'ImChloeLazaro' (maintainer) submitted package.
chocolatey-ops (reviewer) on 24 Apr 2024 05:59:23 +00:00:
pdftoolkit has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl
, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 24 Apr 2024 06:21:16 +00:00:
pdftoolkit has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/429eb4e8f49f8f2af1602ca27da6a2e3 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 24 Apr 2024 07:03:57 +00:00:
pdftoolkit has passed automated virus scanning.
ImChloeLazaro (maintainer) on 24 Apr 2024 07:26:57 +00:00:
User 'ImChloeLazaro' (maintainer) submitted package.
chocolatey-ops (reviewer) on 24 Apr 2024 08:01:41 +00:00:
pdftoolkit has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl
, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 24 Apr 2024 08:18:30 +00:00:
pdftoolkit has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/81c2aa3778722b25682e4cc4566b034b for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 24 Apr 2024 08:33:00 +00:00:
pdftoolkit has passed automated virus scanning.
ImChloeLazaro (maintainer) on 29 Apr 2024 05:30:31 +00:00:
Good day Team! can I know if how many days to review the package to make it public?Thank you
flcdrg (reviewer) on 01 May 2024 23:38:43 +00:00:
The package description implies that this is just for internal use by a specific company (Artex)?
If that is the case, then the Chocolatey Community Repository is not the appropriate place to host this package. You might investigate other package hosting options - https://docs.chocolatey.org/en-us/features/host-packages
David
ImChloeLazaro (maintainer) on 01 May 2024 23:42:02 +00:00:
Hello David, yes it is made for aretex but if other people want to use this you can use this pdftoolkit so this is intended to publish on public
ImChloeLazaro (maintainer) on 01 May 2024 23:44:12 +00:00:
Hello David, yes it is made for aretex but if other people want to use this you can use this pdftoolkit so this is intended to publish on public
ImChloeLazaro (maintainer) on 01 May 2024 23:57:06 +00:00:
User 'ImChloeLazaro' (maintainer) submitted package.
flcdrg (reviewer) on 02 May 2024 00:09:04 +00:00:
Please resolve these to allow this package to be approved:
tools\VERIFICATION.txt
should contain instructions on how the user can independently verify that the embedded file is the same as available for download from the original site.tools\LICENSE.txt
should contain a copy of the software license, and that license must allow redistribution.tools\chocolateybeforemodify.ps1
as it isn't being usedsummary
fieldAlso, if possible:
docsUrl
,mailingListUrl
,bugTrackerUrl
and/orprojectSourceUrl
with appropriate links.thanks,
David
ImChloeLazaro (maintainer) on 02 May 2024 00:17:35 +00:00:
User 'ImChloeLazaro' (maintainer) submitted package.
ImChloeLazaro (maintainer) on 02 May 2024 00:24:23 +00:00:
User 'ImChloeLazaro' (maintainer) submitted package.
chocolatey-ops (reviewer) on 02 May 2024 00:59:32 +00:00:
pdftoolkit has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl
, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 02 May 2024 01:21:39 +00:00:
pdftoolkit has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/834149acc636f08411a36656efa9bbb0 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 02 May 2024 05:15:59 +00:00:
pdftoolkit has passed automated virus scanning.