Bug 803319 - [kn_IN] Date format in the printed draft mail is not translated
Summary: [kn_IN] Date format in the printed draft mail is not translated
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-14 12:46 UTC by Shankar Prasad
Modified: 2015-04-21 04:34 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-15 13:37:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Shankar Prasad 2012-03-14 12:46:40 UTC
Description of problem:
Date format in the printed draft mail shows in en_US.

Version-Release number of selected component (if applicable):
evolution-3.3.91-1.fc17.x86_64

How reproducible:
Every time

Steps to Reproduce:
1.Login to kn_IN locale
2.Launch the evolution mail client
3.Complete the setup
4.Compose a new mail.
5.Print it to a file.
6.Examine the printed output
  
Actual results:
The date format is in english

Expected results:
Date format should be in Kannada (kn_IN)

Additional info:

Comment 1 Milan Crha 2012-03-15 13:37:00 UTC
Thanks for a bug report. I would not call it a bug, though, because it's content of the Date header, as is written in the message itself, same as values for Subject and To/CC headers. It's basically a raw value of the header, as stored in the message. If your timezone is different from the timezone of the Date header, then you can see two values shown there, one is the raw value, and the second, enclosed in braces, is time in your timezone, in a format as setup in Edit->Preferences->Mail Preferences->Headers, where (at the bottom) you can also check/uncheck "Show original header value", which is just for this behaviour, as with unchecked you always get the expected time format.


Note You need to log in before you can comment on or make changes to this bug.