Marc
unread,Jul 20, 2021, 12:05:38 PM7/20/21Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to okapi-users
Dear all,
in translate5 we are using Okapi Longhorn for file format conversion.
We currently start to develop the customization of file filters through
the GUI of translate5 (so far you would have to use Rainbow, if you want
to create a custom bconf for a project import with translate5).
We had a look at the bconf and it is clear, that it contains all the
files that are contained in the folder that Rainbow created, if you
"install" a bconf.
So pipeline, srx, custom fprm-files and the extensions-mapping.txt.
So far so clear.
What is not clear: At the beginning, the end and in between the
different files that are "packaged" into a bconf there are some binary
bytes.
Could someone explain the logic behind those? And/or point us to the
code in the okapi github, that generates these bytes? What information
do they encode except that they seem to be file boundaries?
Thank you very much in advance!!!
best
Marc