The file bibform.xml contains information on how Word should display the "Edit Source" dialog. The thing is, the open xml specification defines a Source as a flat element. As a result, you can assign any field to any source if you
wanted. So even crazy combinations as the theater where your journal article was first broadcasted can be made. What the creators of Microsoft Word did was make a subselection of what fields can be assigned to what source. And the result of their selection
is what is stored in bibform.xml. The file is located on your system in the following directory:
where LCID is a 4 digit code identifying your language. Assuming a default installation of the United States - English (1033) version, this is
C:\Program Files\Microsoft Office\Office12\1033\Bibliography
BibType takes things a step further in that it makes bibform.xml language independent. Unless you have the need to spread your
bibform.xml in multiple languages, you better leave this alone.
It is great that you can fully extend your bibform.xml to your liking. However, what if someone else wants to use your style? You can send them your
bibform.xml, but what if their version of Word is in a different language? Then their copy of
bibform.xml will be located in different subdirectory as it has a different LCID. Moreover, the description of the fields and the examples will be in their language. They could use your
bibform.xml but then their UI would suddenly be in two languages. Not really user friendly.
The above problem is why I made BibType. BibType is a command line utility that takes 2 input files:
- A types.xml which defines sets of fields assigned to specific sources. Basically, it is a slimmed down version of bibform.xml where all language specific information is stripped out.
- An instance of bibform.xml in a specific language.
Based on those two files, it generates a new bibform.xml file which is a localized version. That is, it creates a version where all the strings will be in the language of the original
bibform.xml it got as input. It just generates a file. You are responsible for where you put that file.
I used to include a types.xml with the collection of all styles, but as there is no real request for extending the
bibform.xml functionalty in an internationalised way I removed it. The version that was included is the same one that is offered as an example file on the download page of BibType.
My advise is, only extend bibform.xml if you really have to, and even then, only do it in your own language. BibType isn't a bad tool, but to fully use its potential, you would have to wrap it in an installer which automatically
generates the new bibform.xml and copies it to the appropriate destination. For most common Word users, the concept of the tool is too complicated to fully grasp. It is not something they should have to be bothered with.