For unix, a start would be the error tables, all of the files ending in .et.
As that was the easiest place to begin internationalization of the unix client, the com_err library gained i18n support, but those are the only strings it would be able to translate at this point. Other tools will need additional work done before other strings can be translated. I can't comment meaningfully on the Windows side of things. On Wed, Oct 19, 2011 at 8:14 AM, Karel Nykles <[email protected]> wrote: > Hi all, > > At DESY there was an interest for translation and localization of the > OpenAFS documentation. Our site is also interested in localization of > OpenAFS Windows client. > > We can assign a student for this work, so what should we do and what is > currently possible? > > Thanks for response. > > Best regards, > Karel Nykles > University of West Bohemia > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info > -- Derrick _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
