Hello, One possible solution is to expand only the first time the abbreviation is found. There's also the glossary option, where all terms are aggregated.
I'd like to suggest a sort of table to include terms like API, in order to make translations somewhat uniform in this regard. Ari Constancio On 8/12/07, Karl Fogel <[EMAIL PROTECTED]> wrote: > Rafael Martilotti <[EMAIL PROTECTED]> writes: > > In chapter 4, the paragraph: > > On the other hand, if the project has specific guidelines about > > <emphasis>how</emphasis> to write good code, such as rules about > > documenting every API in a certain format, then those guidelines > > should be written down as completely as possible.</para> > > > > Should I have to translate API as Application Programming Interface ( > > Interfaz de Programación de Aplicaciones), or what? > > [CC'ing the list, as they should see all translation questions.] > > Well, it depends on whether "API" is a well known abbreviation in > Spanish, among likely readers of the book. If it is, then no need to > expand it. If not, then go ahead and add the parenthetical aside. > You are the expert, I only speak English (and a tiny bit of Chinese :-) ). > > -Karl > > _______________________________________________ > Producingoss-translators mailing list > [email protected] > http://www.red-bean.com/mailman/listinfo/producingoss-translators > _______________________________________________ Producingoss-translators mailing list [email protected] http://www.red-bean.com/mailman/listinfo/producingoss-translators
