Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


On Wed, Nov 03, 2010 at 08:48:02PM +0530, "surenspost@gmail.com" <surenspost@gmail.com> wrote:
Thanks to spaetz for helping out with the quirky german comments for which
google translator did not work for.
---
 sw/inc/cmdid.h | 1105 +++++++++++++++++++++++++-------------------------------
 1 files changed, 483 insertions(+), 622 deletions(-)

diff --git a/sw/inc/cmdid.h b/sw/inc/cmdid.h
index e0ef443..52be5cf 100644
--- a/sw/inc/cmdid.h
+++ b/sw/inc/cmdid.h
@@ -27,8 +27,8 @@
  ************************************************************************/
 
 /******************************************************************************
-Achtung: Ab sofort sind in diesem File keine C++-Kommentare (//) mehr
-         erlaubt, da es von swicli.c included wird!
+Attention: From now on in this file does not C comments (//) more
+         allowed because it is included of swicli.c

Hmm, this sounds like the output of a machine translator. :)

How about something like:

Attention: From now on in this file C++ comments (//) are no longer
allowed as it[1] need to check code) will be included in swicli.c.

At least the C++ -> C replace is quite misleading, IMHO.

[1] It is not clear to me what "it" means here, need to check the code
if some script really extracts part of that header, or what's going on.

Attachment: pgpx33qik6xFW.pgp
Description: PGP signature


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.