Filters - Several filters components are implemented, including for: HTML,, Microsoft Office files, Java properties files.These tools are making use of the Okapi components and provide ready-made platforms for plugging in your own components. Applications - Lastly, the framework also provides end-user applications that can be utilized out-of-the-box.Some are basic and low-level parts that can be re-used when programming more high-level components, while others are plug-ins that can be used directly in scripts or applications. Components - The Okapi Framework also includes a growing set of components that implement the different interface specifications.Whenever possible the Okapi Framework make use of existing standards such as XLIFF, SRX, TMX, etc. Using open standards for as many formats as possible increases interoperability. Format Specifications - Storing and exchanging data is an important part of the localization process. For example: all filters have the same API to parse input files, so you can write utilities that use any of the available filters. Implementing these interfaces allows you to seamlessly plug new components in the overall framework. A few of them are defined as high-level specifications. Interface Specifications - The framework's components and applications communicate through several common API sets: the interfaces.The Okapi Framework is organized around the following parts:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |