This is Google’s page describing the .bdic format:
It doesn’t directly address the topic of endianess, but it does say the following:
"The .bdic files are always UTF-8 internally, and the convert_dict tool converts things appropriately when it runs.”
I must admit that the topic of endianess goes a bit beyond my expertise, but my understanding is that it is primarily an issue for executable files. As the .bdic is only a data file, and as the data encoded inside it is in UTF-8 as described above, would that mean that it is safe to assume that these are arch:all?
--
Soren Stoutner
soren@stoutner.com
Attachment:
signature.asc
Description: This is a digitally signed message part.