![]() You also need to install MODI (Microsoft Office Document Imaging) If you cannot find this in the Greenshot software once the MODI components are installed, then try uninstalling Greenshot and reinstalling it. Once this is installed then the Greenshot software is supposed to activate the plug-in that gives it the OCR functionality. SharePoint Designer 2007 ( you can find a description and a link toĮssentially it looks as if you need to download and install something that contains the MODI components. Office 2003 / 2007 installer or as an option from the free Microsoft MODI can be installed as an option from the Microsoft Select this destination the OCR logic from Microsoft will try toĭetect the text on the screenshot and Greenshot will place this on theĬlipboard. The plugin (if installed) and you will have an OCR destination. If this is installed Greenshot will activate We are depending on a component from Microsoft called MODI (Microsoft In the "release/1.3" it's quite hard to add for outsiders, but maybe we can manage this together.For the Greenshot OCR (Optical Character Recognition) plug-in to work We can make the list when the plug-in loads, or first when the mouse is over the OCR destination.Ĭurrently we would need this for the branch "release/1.3", I was trying to make things easier in the develop branch but this is a bit volatile at the moment. ![]() I actually like the idea, take the user-profile language as a default and add the available languages to select. I think adding the possible languages to the dynamic destination picker would be an option where we can at least provide some of our users a way to do OCR with different languages.(We still need to optimize the process for our translations) The issue here, is the settings UI real-estate, there is currently in 1.x no place to add something like that and on top of that we need a translation for the "OCR Language" label, and this is always an issue with the amount of languages we have. We need to check at every start, if the language is still available though, maybe someone removed a language. Add a drop down to the settings, with all available languages.Hey, thanks for describing this in such detail! I've read it that it came in, but due to work and the many things I do in the community I just didn't get to it yet. I should also note that I'm not a Professional C# developer, just a hobbyist, so not much might come from this in the end ). That's why I am asking for some thoughts about it. Filter out the results which contain small or no amounts of text. It would be possible to iterate through all languages and run an OCR pass with each. So the language would probably have to be abstracted in some way. OcrEngine also expects and returns which is part of the Windows SDK which is currently not referenced by GreenshotPlugin. Currently IOcrProvider does not have any facility for discovery of supported languages or giving language hints to the OcrProvider. We would then call OcrEngine.Tr圜reateFromLanguage to recognize text with that specific language. We could get the list of available languages via OcrEngine.AvailableRecognizerLanguages and populate a drop down for the OCR Button with a list of available languages. So for example: if the active Windows language is English, Chinese or Korean text won't be recognized, even if the corresponding OCR language is installed. Is your feature request related to a problem? Please describe.Ĭurrently the Windows 10 OCR plugin calls OcrEngine.Tr圜reateFromUserProfileLanguages, which seems to select the first installed Language with OCR support and use that. This GitHub repository is for developers, if you want to request a feature for Greenshot as a user please do so in our JIRA issue system here:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |