[Desktop-packages] [Bug 819995] Re: "Print to file" PDF metadata broken

2017-06-06 Thread Yusuf Bolu
After 5 years from my first comment above, the annoying bug is still here. 
Creator: cairo 1.14.6
Created: Thu 01 Jan 1970 01:59:59 EET

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/819995

Title:
  "Print to file" PDF metadata broken

Status in cairo package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 11.04 Natty Narwhal 64bit

  libgnomeprint2.2-0 - 2.18.8-0ubuntu1

  It seems libgnomeprint sends wrong date, Jan 1st 1970 to PDF metadata when 
printing to file (PDF)
  This behaviour is reproducible for me on both 64bit and 32bit versions of 
11.04
   
  Using dialog "print to file" choosing PDF as output format "Creation Date" 
and "Last edited" is always set to  "Thu 01 Jän 1970 00:59:59 CET" which is 
afaik Date 0 for Unices.
  I am using german localization but in case of needed screenshots I can of 
course change to english.
  This behaviour happens on my main machine (64bit) and my old notebook (32bit) 
looking to my self produced PDFs from 10.10 definitely show the same behaviour, 
I could also look on old backups for even older version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/819995/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 177929] Re: Should autodetect filename character encoding in zip files

2011-12-14 Thread Yusuf Bolu
I am using Mint 10 (Julia) based on Ubuntu 10.10. I had problem when trying to 
extract files with Turkish letter (ş, ç, ö, ğ ...) from and archive. It gave 
naming error. There was question marks in place of those letters.
I search archive in software manager and I uninstalled many relevant (at 
least I thought so) components like p7zip, unzip, unrar, file-roller etc. Then 
I installed deb package of Peazip from its website. I didn't like it then I 
uninstalled it and installed file-roller only (from software manager). I don't 
know how but the problem has disappeared.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/177929

Title:
  Should autodetect filename character encoding in zip files

Status in File Roller:
  Confirmed
Status in “file-roller” package in Ubuntu:
  Triaged
Status in “xarchiver” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: file-roller

  Many compressed file such as zip don't specify filename encoding. But
  file-roller read every file as UTF-8, so it sometimes makes encoding
  problem.

  I think may be, you could think that it's not a big problem or it's
  not a bug or we don't need those feature. If you deal with only
  English it's not a problem at all. But it's a big problem for East
  Asian people such as Chinese, Japanese and Korean. Because zip file is
  still popular. And many people compress zip file in Windows, and share
  the zip files. Windows don't use UTF-8.

  Many CJK people want to uncompress these zip files. There are some way
  to solve this problem (by another software). But all are too complex
  to Ubuntu newbies. I wish file-roller support encoding select
  function.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/177929/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp