From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id D48EE7FB0A for ; Tue, 9 Dec 2014 07:42:38 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of asai@is.ocha.ac.jp) identity=pra; client-ip=133.65.64.10; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="asai@is.ocha.ac.jp"; x-sender="asai@is.ocha.ac.jp"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of asai@is.ocha.ac.jp designates 133.65.64.10 as permitted sender) identity=mailfrom; client-ip=133.65.64.10; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="asai@is.ocha.ac.jp"; x-sender="asai@is.ocha.ac.jp"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@web.is.ocha.ac.jp) identity=helo; client-ip=133.65.64.10; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="asai@is.ocha.ac.jp"; x-sender="postmaster@web.is.ocha.ac.jp"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AoMAAE6ZhlSFQUAKl2dsb2JhbABZg1hYxhaHNhYBAQEBAREBAQEBAQgWB0KEBAQTKDkLNzQFIAEFAVeIDgcBBQivbYMlPTGdM4VICpBPgwuBFQWJQYglbYROAYE9jj83hTRgAYJCAQEB X-IPAS-Result: AoMAAE6ZhlSFQUAKl2dsb2JhbABZg1hYxhaHNhYBAQEBAREBAQEBAQgWB0KEBAQTKDkLNzQFIAEFAVeIDgcBBQivbYMlPTGdM4VICpBPgwuBFQWJQYglbYROAYE9jj83hTRgAYJCAQEB X-IronPort-AV: E=Sophos;i="5.07,543,1413237600"; d="scan'208";a="92457073" Received: from web.is.ocha.ac.jp ([133.65.64.10]) by mail3-smtp-sop.national.inria.fr with ESMTP; 09 Dec 2014 07:42:34 +0100 Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) by web.is.ocha.ac.jp (Postfix) with ESMTP id C1E4B99685B for ; Tue, 9 Dec 2014 15:42:10 +0900 (JST) Received: by mail-pd0-f177.google.com with SMTP id ft15so6680026pdb.36 for ; Mon, 08 Dec 2014 22:42:29 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-type:content-disposition:user-agent; bh=WAkAAZ2eycvUAXwomSmi4NAU/WV+46SGfjdh8knr/YY=; b=W+/sOCz/HQOyQjOsYrSilGS1IOGa4/fFILlQTRqr8V5I0FSyIpgwgVVw5+8uyoiITw Khya7CyE3Ck3CnsCHKABUdXZTKKkoAVIn7Cn5WiGJTnx8wbhCkJ8iyDfuz35fukZZkfT G4GXGfxZkSDEormm1QYic/hrOsqa+3jH2NxNqEvmtFSxPxhLVR7H4XZPFIPcekE409Dj VBEzVAKVoxnSjwCM/DflZr5tgZH2+MKB2udhFFbROi4aJnyje8Gq3ZwYvqCGqREtK0NB 9+4rXwwqlahAlgHUmnvwrPpIB/8e9DN9u0zgkTrPEqrCmc71rTZdbrPba+cUB/cLgg6y 0rDw== X-Gm-Message-State: ALoCoQlU0VYqDCH+IoPyUR4J+lGDHE9lwKHPXNQV8ohpywm7N0ceWszkYJNDdAwW1/zrpk8/X2VsZU6M6RM8O/MOCn4oLvFzzCc+O5vIVt1UWQXL5aVkBCXRu8pMQluDrpCVcrNgOaZs X-Received: by 10.70.43.229 with SMTP id z5mr27618020pdl.25.1418107349965; Mon, 08 Dec 2014 22:42:29 -0800 (PST) X-Received: by 10.70.43.229 with SMTP id z5mr27617986pdl.25.1418107349682; Mon, 08 Dec 2014 22:42:29 -0800 (PST) Received: from localhost ([133.65.65.2]) by mx.google.com with ESMTPSA id nc9sm426239pbc.55.2014.12.08.22.42.28 for (version=TLSv1.1 cipher=RC4-SHA bits=128/128); Mon, 08 Dec 2014 22:42:29 -0800 (PST) Date: Tue, 9 Dec 2014 15:42:23 +0900 From: Kenichi Asai To: caml-list@inria.fr Message-ID: <20141209064223.GA501@pllab.is.ocha.ac.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) Subject: [Caml-list] OCamlDoc: @-tags handled only in the standard elements? I thought I could provide documents in two languages using custom tags in OCamlDoc, but there still remains a problem. It appears that the custom tags (in my case, @en and @jp) are not handled in - the very first comment, - special comments between elements, and - comments for type constructors, etc. Is there any way to support custom tags in all the places including the above? -- Currently, it seems not, as the OCamlDoc says: http://caml.inria.fr/pub/docs/manual-ocaml/ocamldoc.html Section 15.2.1: > (** Special comments can be placed between elements and are kept > by the OCamldoc tool, but are not associated to any element. > @-tags in these comments are ignored.*) Section 15.2.3: > Some elements support only a subset of all @-tags. Tags that are not > relevant to the documented element are simply ignored. For instance, > all tags are ignored when documenting type constructors, record > fields, and class inheritance clauses. Similarly, a @param tag on a > class instance variable is ignored. Why aren't all the comments handled in the same way? It appears to be easier to handle all the comments in the same way. Is there any chance that it will become as such? Sincerely, -- Kenichi Asai