emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Esteban Ordóñez" <quiliro@riseup.net>
To: Christian Moe <mail@christianmoe.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [HELP] Translate/extend `org-clock-clocktable-language-setup' for Spanish/Dutch/more languages
Date: Mon, 05 Dec 2022 14:33:18 +0000	[thread overview]
Message-ID: <f804223bfb2cb087862550f5412042d4@riseup.net> (raw)
In-Reply-To: <87k0363qoy.fsf@christianmoe.com>

El 2022-12-05 08:50, Christian Moe escribió:
> Ihor Radchenko writes:
> 
>> Esteban Ordóñez <quiliro@riseup.net> writes:
>>
>>> El 2022-12-04 06:17, Ihor Radchenko escribió:
>>>
>>>> #+BEGIN: clocktable :scope file :maxlevel 2
>>>> #+CAPTION: Clock summary at [2022-12-04 Sun 14:16]
>>>> |   Headline   |   Time    |
>>>> |--------------+-----------|
>>>> | *Total time* | *0h 0min* |
>>>> #+END:
>>>
>>> It is still not clear what "Clock summary at" refers to.  Perhaps
>>> someone fairly proficient in the English language could use it in a
>>> sentence.  That sentence needs to specifically convey the sense of what
>>> "Clock summary at" means in org-mode.  Then I could translate it to
>>> Spanish correctly.  Nevertheless, the translation is probably fair
>>> enough.
>>
>> In other words, the caption is trying to say that the table below lists
>> summary of clocked time as of [...] date; how much time is spent doing
>> various tasks before [...] date.
>>
>> Hope it clarifies things.

It does.  Thank you very much, Christian.

So "Clock summary at" is more like "Clock summary up to"?

That would translate to "Resumen de tiempos hasta" in Spanish.  But is
seems like a long text, even if it is gramatically correct.


  reply	other threads:[~2022-12-05 14:34 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-27  0:06 [HELP] Translate/extend `org-clock-clocktable-language-setup' for Spanish/Dutch/more languages Ihor Radchenko
2022-11-27  9:02 ` gerard.vermeulen
2022-11-28  5:10   ` Ihor Radchenko
2022-11-28  5:47     ` gerard.vermeulen
2022-12-04 11:14       ` Ihor Radchenko
2022-12-04 11:21         ` Ihor Radchenko
2022-11-27  9:15 ` Esteban Ordóñez
2022-11-28  5:26   ` Ihor Radchenko
2022-11-28 10:21     ` Esteban Ordóñez
2022-12-04 11:17       ` Ihor Radchenko
2022-12-05 13:08         ` Esteban Ordóñez
2022-12-05 13:15           ` Ihor Radchenko
2022-12-05 13:34             ` Esteban Ordóñez
2022-12-05 13:37               ` Esteban Ordóñez
2022-12-05 13:44                 ` Ihor Radchenko
2022-12-05 16:47                   ` Esteban Ordóñez
2022-12-05 13:50             ` Christian Moe
2022-12-05 14:33               ` Esteban Ordóñez [this message]
2022-12-05 15:25                 ` Christian Moe
2022-12-05 16:51                   ` Esteban Ordóñez
2022-12-14 13:17       ` [HELP] Things to help Org that do not involve programming Ihor Radchenko
2023-02-03  9:09         ` Kevin Brubeck Unhammer
2023-02-11 11:51           ` Ihor Radchenko
2022-11-28  5:01 ` [HELP] Translate/extend `org-clock-clocktable-language-setup' for Spanish/Dutch/more languages Ihor Radchenko
2022-11-29  0:07 ` Jonathan Gregory
2022-12-04 11:24   ` Ihor Radchenko
2022-12-04 17:44     ` Jonathan Gregory
2022-12-10 13:26       ` Ihor Radchenko
2022-11-30  0:19 ` Rudolf Adamkovič
2022-12-04 11:26   ` Ihor Radchenko
2022-12-12 12:34     ` Ihor Radchenko
2022-12-13 21:35     ` Rudolf Adamkovič
2022-11-30 15:01 ` Max Nikulin
2022-12-04 11:27   ` Ihor Radchenko
2022-12-06 11:12     ` Max Nikulin
2023-02-03  8:55 ` Kevin Brubeck Unhammer
2023-02-03  9:52   ` Christian Moe
2023-02-03 11:01     ` Kevin Brubeck Unhammer
2023-02-11 11:56   ` Ihor Radchenko
  -- strict thread matches above, loose matches on Subject: below --
2022-12-01  6:44 Pedro Andres Aranda Gutierrez
2022-12-12 12:18 ` Ihor Radchenko
2022-12-12 12:32   ` Pedro Andres Aranda Gutierrez
2023-02-02 11:05   ` Ihor Radchenko
2023-02-04  2:02     ` Esteban Ordóñez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f804223bfb2cb087862550f5412042d4@riseup.net \
    --to=quiliro@riseup.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@christianmoe.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).