Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unicharambigs man page missing v2 format #165

Closed
tfmorris opened this issue Dec 7, 2015 · 10 comments
Closed

unicharambigs man page missing v2 format #165

tfmorris opened this issue Dec 7, 2015 · 10 comments

Comments

@tfmorris
Copy link
Contributor

tfmorris commented Dec 7, 2015

The man page for the unicharambigs file format only includes documentation on the v1 format, not the v2 format (and is missing a description of the first line which is used for version identification).

https://github.com/tesseract-ocr/tesseract/blob/master/doc/unicharambigs.5.asc

@Shreeshrii
Copy link
Collaborator

@zdenop
Copy link
Contributor

zdenop commented Aug 31, 2016

Which file use unicharambigs file v2?

@Shreeshrii
Copy link
Collaborator

Shreeshrii commented Sep 1, 2016

I think Ray had updated the documentation (couple years back??). From what
I understand from it unicharambigs file could be either in v1 format or v2
format.

  • sent from my phone. excuse the brevity.

On 01-Sep-2016 12:38 AM, "zdenop" notifications@github.com wrote:

Which file use unicharambigs file v2?

@zdenop
Copy link
Contributor

zdenop commented Sep 1, 2016

I did not find (in langdata repository) language that use v2 of unicharambigs... So I am not sure if it make sense to write docs for it (=> propagate it) if it is not used (=> not tested).

@Shreeshrii
Copy link
Collaborator

Shreeshrii commented Sep 1, 2016

Thanks for checking langdata from 3.04.

Ray is the best person to answer whether v2 has been used/tested for any
languages.

Also, there was supposed to be a new release as per tutorial at DAS2016. Do
you know when that will be and what is included in it?

  • sent from my phone. excuse the brevity.

@zdenop
Copy link
Contributor

zdenop commented Sep 1, 2016

I hear something like end of September 2016, but you never know ;-) It will big update (probably we will drop support of compilers nor support c++11)...

@zdenop zdenop added this to the 4.00 milestone Sep 1, 2016
@Shreeshrii
Copy link
Collaborator

@zdenop Any update regarding 4.0 release? Thanks!

@zdenop
Copy link
Contributor

zdenop commented Oct 21, 2018

I found only one lang in langdata, that use v2: gle_uncial :-)

@amitdo
Copy link
Collaborator

amitdo commented Oct 21, 2018

The lstm engine does not use the unicharambigs file.

@zdenop
Copy link
Contributor

zdenop commented Oct 21, 2018

but unicharambigs is still there present e.g. in eng. And 4.0 version support also legacy engine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants