Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues in man ddate man page #24

Open
hmartink opened this issue Feb 5, 2022 · 2 comments
Open

Issues in man ddate man page #24

hmartink opened this issue Feb 5, 2022 · 2 comments

Comments

@hmartink
Copy link

hmartink commented Feb 5, 2022

`Dear ddate maintainer,
the manpage-l10n project maintains a large number of translations of
man pages both from a large variety of sources (including ddate) as
well for a large variety of target languages.

During their work translators notice different possible issues in the
original (english) man pages. Sometimes this is a straightforward
typo, sometimes a hard to read sentence, sometimes this is a
convention not held up and sometimes we simply do not understand the
original.

We use several distributions as sources and update regularly (at
least every 2 month). This means we are fairly recent (some
distributions like archlinux also update frequently) but might miss
the latest upstream version once in a while, so the error might be
already fixed. We apologize and ask you to close the issue immediately
if this should be the case, but given the huge volume of projects and
the very limited number of volunteers we are not able to double check
each and every issue.

Secondly we translators see the manpages in the neutral po format,
i.e. converted and harmonized, but not the original source (be it man,
groff, xml or other). So we cannot provide a true patch (where
possible), but only an approximation which you need to convert into
your source format.

Finally the issues I'm reporting have accumulated over time and are
not always discovered by me, so sometimes my description of the
problem my be a bit limited - do not hesitate to ask so we can clarify
them.

I'm now reporting the errors for your project. If future reports
should use another channel, please let me know.

Man page: ddate.1
Issue: B<date(1),> → B(1),
(sorry, github mangels the report here: move the (1), out of the bracket)

"If a format string is specified, the Discordian date will be printed in a "
"format specified by the string. This mechanism works similarly to the format "
"string mechanism of B<date(1),> only almost completely differently. The "
"fields are:"

Man page: ddate.1
Issue: B<ddate(1)> → B(1)
(sorry, github mangels the report here: move the (1) out of the bracket)

"B<ddate(1)> will produce undefined behavior if asked to produce the date for "
"St. Tib's day and its format string does not contain the St. Tib's Day "
"delimiters %{ and %}."

`

@danwdart
Copy link
Collaborator

danwdart commented Feb 5, 2022

Is this just a formatting error? I fail to see the problem with the English...

@hmartink
Copy link
Author

hmartink commented Feb 6, 2022

I apologizie that githubs form breaks the text.

For both paragraphs, please move the "(1)" out of the angle brackts, so it reads B< ddate >(1) (without spaces!!) and not B<date(1)>. Also punctuation in the first paragraph should be moved outside the bold part.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants