Fixed some typos

This commit is contained in:
Jens Klingen 2017-02-04 22:29:37 +01:00
commit bb61d2b4a6
2 changed files with 11 additions and 11 deletions

View file

@ -2,7 +2,7 @@
layout: faq
status: publish
published: true
title: What is the best way to control Greenshot's configuration at install time?
title: How can I control Greenshot's configuration during installation and beyond
# override permalink for to keep old URLs intact
permalink: /faq/what-is-the-best-way-to-control-greenshots-configuration-at-install-time/
tags: []
@ -12,7 +12,7 @@ tags: []
This documentation will help you if want to have more control over Greenshots configuration, for instance to pre-set a language or specifiy settings for your companies JIRA/Confluence server.
Except for the functionality that Greenshot is started when Windows starts, all it's settings are stored in [.ini files](https://en.wikipedia.org/wiki/INI_file).
Every added plug-in will has it's own section in the configuration, making sure that developers of plug-in don't need to concern themselves with how the configuration is written.
Every added plug-in will have its own section in the configuration, making sure that plug-in developers don't need to concern themselves with how the configuration is written.
Greenshot has an intelligent configuration system, and it is readable and even changeable by humans!
To support manual editing the greenshot.ini automatically adds comments to every setting when this is written by Greenshot.
@ -22,11 +22,11 @@ If a setting or even a configuration file is missing Greenshot will either take
This has the nice advantage that if things no longer work, a setting or the complete configuration can simply be removed.
With our system it's possible to supply specific settings as default, or even make them non changeable.
To understand the possibilities, you first need to know where, how and in what order Greenshot reads it's configuration.
To understand the possibilities, you first need to know where, how and in which order Greenshot reads its configuration.
Greenshot knows of 3 different files, which are loaded in the following order:
1. greenshot-defaults.ini: this specifies the defaults which are used if no other setting are available. (At first start)
1. greenshot-defaults.ini: this specifies the defaults which are used if no other settings are available. (At first start)
2. greenshot.ini: this is the normal file, with all the settings of the user, which is written by Greenshot. This overrules the settings in the greenshot-defaults.ini file.
3. greenshot-fixed.ini: has settings which will overrule all settings in the files above.

View file

@ -7,7 +7,7 @@ permalink: /faq/is-greenshot-clean/
tags: []
---
Every now and than we get reports of users who have anti-virus software which detects _something_ in Greenshot,
Every now and then we get reports of users who have anti-virus software which detects _something_ in Greenshot,
and they are wondering how secure Greenshot actually is.
First, we strongly recommend to always download Greenshot from our [official website](http://getgreenshot.org/)
@ -15,21 +15,21 @@ First, we strongly recommend to always download Greenshot from our [official web
bundling adware or even malware with the original installer. Also the installers for download are often outdated or "nightly builds" which might be buggy and are not intended to be used by a wide audience.
Athough there is no 100% garantee of building an application which is not infected. We have set a high standard, I would say much higher as some software you must pay for.
Although there is no 100% guarantee of building an application which is not infected. We have set a high standard, I would say much higher as some software you must pay for.
The following describes how we work to keep Greenshot clean:
1. Greenshot only contains program code that which we place into our Github Open Source repository, everybody can look into it meaning there are no secrets.
2. Only WE decide what ends up in our repository, and with that what ends into Greenshot, the community can supply us with changes but those are approved by us before moved into Greenshot.
3. Thanks to the nice people at [AppVeyor](https://www.appveyor.com/) Greenshot is build on a clean Windows image, not on our PCs. This has 2 advantages:
1. Greenshot only contains program code which we place into our Github Open Source repository, everybody can look into it meaning there are no secrets.
2. Only **we** decide what ends up in our repository, and with that what ends into Greenshot. The community can supply us with changes but those are approved by us before moved into Greenshot.
3. Thanks to the nice people at [AppVeyor](https://www.appveyor.com/) Greenshot is built on a clean Windows image, not on our PCs. This has 2 advantages:
* The Windows installation is never used by people and reset every time *before* a build starts. This makes sure that the Windows installation is not infected.
* There is no chance that some modification to Greenshot, which is on our system but not pushed to github, ends up in our product.
* There is no chance that some modification ends up in Greenshot, which is on our system but not pushed to github.
4. We check Greenshot with [Virus Total](https://www.virustotal.com/) before we make it available to the public
5. We sign our product with a code signing certificate, since 1.2.9, so people can detect if someone tampered with the files.
So, as long as you download via *our* [site](https://getgreenshot.org/downloads) you should be fine.
About those people who reported that their anti-virus software detected something, upto now I think we did our work as:
About those people who reported that their anti-virus software detected something, up to now I think we did our work as:
* some never replied back to our question from *where* they downloaded Greenshot.
* some downloaded Greenshot from elsewhere, not from our site.