perldoc > Email::Date::Format

man perldoc info pydoc3 ri search

The user wants me to transform a Perl module documentation HTML into an emoji-rich version. Let me analyze the structure: 1. NAME - module name and description 2. VERSION 3. SYNOPSIS - code example 4. DESCRIPTION - what it does 5. FUNCTIONS - email_date and email_gmdate 6. AUTHORS 7. COPYRIGHT AND LICENSE I need to: - Keep structure intact - Add emoji to headings (h2 for sections, h3 for sub-sections) - Add 🚀 Quick Reference as second section - Preserve code in

- Use  for function names
- Use proper HTML escaping
- Follow all the rules

Let me note that the SYNOPSIS has  tags inside code - I need to remove those and put the proper code. The rule says: "NEVER put  inside a 
 block. The copy-button will break and the code becomes invalid."

Looking at the synopsis:
```
use Email::Date::Format qw(email_date);

my $header = email_date($date->epoch);

Email::Simple->create(
  header => [
    Date => $header,
  ],
  body => '...',
);
```

The original has  links inside the code. I'll strip those links and keep just the text, since the rule says no  inside code blocks.

Now let me also note that ">" and "<" need to be properly handled - in the code `$date->epoch` should become `$date->epoch` inside 
. Actually wait, in HTML entity form, this would render as `->` when displayed. Let me put it as actual characters since it's inside 
.

Actually, looking more carefully - in the original HTML, `$date->epoch` is HTML-encoded. When the browser renders this in a 
, it shows `$date->epoch`. So I should preserve the HTML entities or use actual characters. Per rule 13, I should escape bare < and >, but inside code, I think actual characters are fine since it's not HTML markup. Let me use actual `>` and `epoch` directly inside 
, the > would need to be escaped. Let me use `>` to be safe.

Actually, looking at this more carefully - within `
`, the content is treated as CDATA-like in HTML5, but to be safe and follow the rules, I should escape < and > with < and >.

Let me construct the output now.

For the Quick Reference table:
- Use Case | Command | Description
- Generate current RFC 2822 date: `email_date()` | Returns RFC 2822 date string for current time
- Generate date from epoch: `email_date($epoch)` | Returns RFC 2822 date string for given epoch
- Generate GMT date: `email_gmdate($epoch)` | Returns RFC 2822 date string in GMT

Let me write the output now.

For AUTHORS list, I'll use proper 
 format.

Let me also note the email link: `rjbs AT cpan.org` - this has u tags around " AT " which is an obfuscation technique. I'll preserve it.

Let me draft the final HTML:

```html
📛 NAME
    Email::Date::Format - produce RFC 2822 date strings 📨

🚀 Quick Reference

Use Case
Command
Description
🕐 Current time
email_date()
RFC 2822 date string for now
⏱️ Past/future time
email_date($epoch)
RFC 2822 date string for given epoch
🌍 GMT time
email_gmdate($epoch)
RFC 2822 date string in GMT


🏷️ VERSION
    
version 1.005

📜 SYNOPSIS
  use Email::Date::Format qw(email_date);

  my $header = email_date($date->epoch);

  Email::Simple->create(
    header => [
      Date => $header,
    ],
    body => '...',
  );


📖 DESCRIPTION
    
This module provides a simple means for generating an RFC 2822 compliant datetime string. (In case you care, they're not RFC 822 dates, because they use a four digit year, which is not allowed in RFC 822.)

⚙️ FUNCTIONS

📅 email_date
  my $date = email_date; # now
  my $date = email_date( time - 60*60 ); # one hour ago

"email_date" accepts an epoch value, such as the one returned by "time". It returns a string representing the date and time of the input, as specified in RFC 2822. If no input value is provided, the current value of "time" is used.
"email_date" is exported only if requested. 📦

🌐 email_gmdate
  my $date = email_gmdate;

"email_gmdate" is identical to "email_date", but it will return a string indicating the time in Greenwich Mean Time, rather than local time.
"email_gmdate" is exported only if requested. 📦

👥 AUTHORS

👨‍💻 Casey West
👨‍💻 Ricardo SIGNES <rjbs AT cpan.org>


⚖️ COPYRIGHT AND LICENSE
This software is copyright (c) 2004 by Casey West.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
```

Wait - rule 12 says function reference lists should use `
name(args) — description
` without per-item emoji. This is more relevant for pydoc/ri-style function lists. The functions here are presented as sub-sections of FUNCTIONS, which is appropriate as h3 sub-headings with code examples.

Let me verify my output again and make sure all the code is wrapped properly.

The synopsis has the  tags inside code which need to be stripped per rule 8. So:
- `use Email::Date::Format qw(email_date);` becomes `use Email::Date::Format qw(email_date);`
- `Email::Simple->create(` becomes `Email::Simple->create(`

Good. Let me finalize.

📛 NAME
    
Email::Date::Format - produce RFC 2822 date strings 📨

🚀 Quick Reference

Use Case
Command
Description
🕐 Current time
email_date()
RFC 2822 date string for now (local time)
⏱️ Custom epoch
email_date($epoch)
RFC 2822 date string for given epoch value
🌍 GMT time
email_gmdate($epoch)
RFC 2822 date string in Greenwich Mean Time


🏷️ VERSION
    
version 1.005

📜 SYNOPSIS
  use Email::Date::Format qw(email_date);

  my $header = email_date($date->epoch);

  Email::Simple->create(
    header => [
      Date => $header,
    ],
    body => '...',
  );


📖 DESCRIPTION
    
This module provides a simple means for generating an RFC 2822 compliant datetime string. (In case you care, they're not RFC 822 dates, because they use a four digit year, which is not allowed in RFC 822.) 📅

⚙️ FUNCTIONS

📅 email_date
  my $date = email_date; # now
  my $date = email_date( time - 60*60 ); # one hour ago

    
"email_date" accepts an epoch value, such as the one returned by "time". It returns a string representing the date and time of the input, as specified in RFC 2822. If no input value is provided, the current value of "time" is used. 🕒
    
"email_date" is exported only if requested. 📦

🌐 email_gmdate
  my $date = email_gmdate;

    
"email_gmdate" is identical to "email_date", but it will return a string indicating the time in Greenwich Mean Time, rather than local time. 🌍
    
"email_gmdate" is exported only if requested. 📦

👥 AUTHORS

👨‍💻 Casey West
👨‍💻 Ricardo SIGNES <rjbs AT cpan.org>


⚖️ COPYRIGHT AND LICENSE
    
This software is copyright (c) 2004 by Casey West. ©
    
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. 🆓