2009年 11月 17(火曜日)
CleanArchiver alpha その3
最近たびたびお騒がせしております。すでにホームページ本体にはアナウンス上がっていますが、CleanArchiver 3.0a6 をリリースしています。
大変申し訳ないことに 3.0a5 はちょっとミスってしまってすぐに 3.0a6 を出すことになってしまいましたが、国内海外ともにいろいろなところで取り上げられているようで、順調にダウンロード数も伸びているようです（3.0a6 は今日一日で 1000 件くらいかな）。
正式リリースまでにはまだやり残したことがいくつかあって、3.0 は年内ギリギリで出せるかどうかくらいのイメージでやっています。予定としては以下の機能は少なくとも追加したいと思っています。
- AppleScript 対応
- Automator 対応
今週中にはとりあえず動くものができそうな雰囲気ですが、これがいつリリースできるかは未定です（リリース作業が意外と面倒くさいもので・・・）。
あと、最高のケースでは正式版は日本語・英語・韓国語・ドイツ語・フランス語・イタリア語にローカライズされた状態で出せると思います。ヘルプの作成などが間に合っていなくて、関係者各位にも連絡が取れていない申し訳ない状況になってしまっていますが（と、ここに日本語で書いても意味がないのですが・・・）。
ともあれ、あせらずまったりお待ちくださいませ。
トラックバック
このエントリーのトラックバック URI を指定する
トラックバックがありません
コメント
コメント表示形式
(一覧 | スレッド)
通りがかりの者です。
CleanArchiverをダウンロードさせていただきました。
MacOSX用の圧縮ソフトが中々見あたらないもので、稀少的にもクオリティも、シンプルで大変素晴らしいソフトウェアだと思っています。
素晴らしいソフトウェアのフリーでのご提供、本当に感謝致します。メールを出すのは仰々しいかと思い、この場をお借りしてお礼を書かせていただきます。
これからも開発・アップデート等を応援致します。
それでは失礼します。
CleanArchiverをダウンロードさせていただきました。
MacOSX用の圧縮ソフトが中々見あたらないもので、稀少的にもクオリティも、シンプルで大変素晴らしいソフトウェアだと思っています。
素晴らしいソフトウェアのフリーでのご提供、本当に感謝致します。メールを出すのは仰々しいかと思い、この場をお借りしてお礼を書かせていただきます。
これからも開発・アップデート等を応援致します。
それでは失礼します。
Hello.
I saw your updates a few days ago.
At first, I would like to say thank you for consenting my previous suggest. : )
I've got your latest 3.0a6 package and tested it.
And then I found a bug with some files, when it was archived by 7zip format.
It might be fixed at the p7zip's ConvertString.cpp code.
I will attach below example file link for testing.
http://www.mediafire.com/file/mywztnndqn2/Archive sample.7z
Please examine under '02.Korean~' directory between
"Sample using CleanArchiver 3.0a6.7z"
and
"Sample using CleanArchiver with Unicode NFC.7z".
The latter is made in my modified CleanArchiver version.
If you test your 7zip on CLI with samples, you can see some warning messages.
P.S.
All attached files has been made from one sample directory. So they have to be
same contents.
And other things to ask and be wondered.
1. Windows's Winzip tries to archive all filenames even though some of them
can't be converted into specific codepage(such as CP932).
At that time, it stores them into Unicode.
Therefore when an archive files which were made by Winzip consist two kinds of
encodings, local codepage and Unicode.
The info-zip source code which I gave did that way.
And also, it tries to normalize Unicode into NFC, if filename is archived in
Unicode.
So I would recommend you to add that behavior for maximum compatibility.
Please look at
"Sample using Winzip 14.0 in Japan Locale Windows XP.zip"
and
"Sample using CleanArchiver with CP932 encoding.zip",
You can easily examine with BetterZip QuickLook Generator.
http://macitbetter.com/BetterZip-Quick-Look-Generator
You can find 'test/03. Japanese...' are seperated into two directories.
2. Info-zip save unix-related extra zip fields into archive file such GID, UID,
etc.
It sometimes interferes to read archive file properly in windows zip
applications such as 7zip, winrar, etc.
So I add option '-X' into zip command when user selects windows compatible
option.
3. Info-zip 3.0b has a feature about resource fork support, but it didn't
implemented completely.
I think it couldn't take non-ASCII filename's resource fork well.
4. In case of libiconv, it don't care about over U+10000 Unicode codepoint.
So you might use one of the normalize functions than 'iconv(UTF-8, UTF-8-MAC)'.
5. I confirmed that 'Icon\r' is still to use.
So how about combine options such as 'exclude .DS_Store', 'exclude Icon\r' and
'discard resource fork' into 'exclude Mac-specific files'?
Users might like easy and simple option.
6. I wondered 'Internet enabled DMG' is still working.
The reason I remove it in my modifed version is that.
I couldn't find the difference between the option was on and off.
7. I think compression level has 'store - not compress' method.
Some big files such as movie clip are no need to compress.
Some users maybe want it.
8. Why did you get rid of archive split option?
I know that info-zip split method are not used broadly, and 7zip's one is same
as unix's split command feature.
But users want to this function using easily GUI method.
9. What is the reason that 'more options' was removed?
I thought it might be helpful for power-user who wants more elaborate
configuration.
For example, 7zip option '-mhe=on' is enable filename encryption.
10. I added default settings save feature for each format.
When user choose one format, if it has saved preferences, it restored.
It will also give users better convenience.
11. Why did you change minimum required OS X version number to 10.5 instead of
10.4?
Is it caused by ruby script?
12. Service menu supports became more important on Snow Leopard.
Because it officially forbidden 3rd party application's context menu hack.
Sorry for my unmannered and poor English.
If you have any question, ask me anything please. : )
Sincerely,
Changbeom Park
I saw your updates a few days ago.
At first, I would like to say thank you for consenting my previous suggest. : )
I've got your latest 3.0a6 package and tested it.
And then I found a bug with some files, when it was archived by 7zip format.
It might be fixed at the p7zip's ConvertString.cpp code.
I will attach below example file link for testing.
http://www.mediafire.com/file/mywztnndqn2/Archive sample.7z
Please examine under '02.Korean~' directory between
"Sample using CleanArchiver 3.0a6.7z"
and
"Sample using CleanArchiver with Unicode NFC.7z".
The latter is made in my modified CleanArchiver version.
If you test your 7zip on CLI with samples, you can see some warning messages.
P.S.
All attached files has been made from one sample directory. So they have to be
same contents.
And other things to ask and be wondered.
1. Windows's Winzip tries to archive all filenames even though some of them
can't be converted into specific codepage(such as CP932).
At that time, it stores them into Unicode.
Therefore when an archive files which were made by Winzip consist two kinds of
encodings, local codepage and Unicode.
The info-zip source code which I gave did that way.
And also, it tries to normalize Unicode into NFC, if filename is archived in
Unicode.
So I would recommend you to add that behavior for maximum compatibility.
Please look at
"Sample using Winzip 14.0 in Japan Locale Windows XP.zip"
and
"Sample using CleanArchiver with CP932 encoding.zip",
You can easily examine with BetterZip QuickLook Generator.
http://macitbetter.com/BetterZip-Quick-Look-Generator
You can find 'test/03. Japanese...' are seperated into two directories.
2. Info-zip save unix-related extra zip fields into archive file such GID, UID,
etc.
It sometimes interferes to read archive file properly in windows zip
applications such as 7zip, winrar, etc.
So I add option '-X' into zip command when user selects windows compatible
option.
3. Info-zip 3.0b has a feature about resource fork support, but it didn't
implemented completely.
I think it couldn't take non-ASCII filename's resource fork well.
4. In case of libiconv, it don't care about over U+10000 Unicode codepoint.
So you might use one of the normalize functions than 'iconv(UTF-8, UTF-8-MAC)'.
5. I confirmed that 'Icon\r' is still to use.
So how about combine options such as 'exclude .DS_Store', 'exclude Icon\r' and
'discard resource fork' into 'exclude Mac-specific files'?
Users might like easy and simple option.
6. I wondered 'Internet enabled DMG' is still working.
The reason I remove it in my modifed version is that.
I couldn't find the difference between the option was on and off.
7. I think compression level has 'store - not compress' method.
Some big files such as movie clip are no need to compress.
Some users maybe want it.
8. Why did you get rid of archive split option?
I know that info-zip split method are not used broadly, and 7zip's one is same
as unix's split command feature.
But users want to this function using easily GUI method.
9. What is the reason that 'more options' was removed?
I thought it might be helpful for power-user who wants more elaborate
configuration.
For example, 7zip option '-mhe=on' is enable filename encryption.
10. I added default settings save feature for each format.
When user choose one format, if it has saved preferences, it restored.
It will also give users better convenience.
11. Why did you change minimum required OS X version number to 10.5 instead of
10.4?
Is it caused by ruby script?
12. Service menu supports became more important on Snow Leopard.
Because it officially forbidden 3rd party application's context menu hack.
Sorry for my unmannered and poor English.
If you have any question, ask me anything please. : )
Sincerely,
Changbeom Park
Thank you for the long comment 
I've fixed 7zip bug. The fixed version will be released soon.
> 1. Windows's Winzip tries to archive all filenames even though some of them
can't be converted into specific codepage(such as CP932).
I see. I will try the compatible way.
> Info-zip save unix-related extra zip fields into archive file such GID, UID,
etc. It sometimes interferes to read archive file properly in windows zip
applications such as 7zip, winrar, etc.
Hmm. CleanArchiver don't have idea of 'Windows compatible'. But discarding
UID, GID, etc. may be reasonable because Mac OS X users don't mind such
infomation. If they are needed, I think gzip or bzip2 are usually used.
> 3. Info-zip 3.0b has a feature about resource fork support, but it didn't
implemented completely.
Really!? I'll disable resource fork support in zip.
> 4. In case of libiconv, it don't care about over U+10000 Unicode codepoint.
So you might use one of the normalize functions than 'iconv(UTF-8, UTF-8-MAC)'.
Yes. I remember it. I would like to support over U+10000 characters, but they
are rare and this support is low priority now.
> 5. I confirmed that 'Icon\r' is still to use.
>So how about combine options such as 'exclude .DS_Store', 'exclude Icon\r' and
'discard resource fork' into 'exclude Mac-specific files'?
I can't find 'Icon\r' on Mac OS X 10.5 and I think 'Exclude Icon\r' is no
longer necessary. This file exists on 10.5?
And I can't combine all exclude options because exists the case I want to save
resource forks but delete .DS_Stores when creating Disk Images.
> 6. I wondered 'Internet enabled DMG' is still working.
> The reason I remove it in my modifed version is that.
> I couldn't find the difference between the option was on and off.
Indeed, I don't find internet-enable disk images recently...
> 7. I think compression level has 'store - not compress' method.
> Some big files such as movie clip are no need to compress.
> Some users maybe want it.
gzip and bzip2 don't support 'store' method and I don't like to add format
specific options though such options already exist... It may return.
> 8. Why did you get rid of archive split option?
> I know that info-zip split method are not used broadly, and 7zip's one is same
as unix's split command feature.
> But users want to this function using easily GUI method.
Because I think it is used rarely. I'd like to keep GUI simple.
> 9. What is the reason that 'more options' was removed?
> I thought it might be helpful for power-user who wants more elaborate
configuration.
> For example, 7zip option '-mhe=on' is enable filename encryption.
Likewise. CleanArchiver call external commands now, but CleanArchiver don't
have to do so and this implementation may be changed.
> 10. I added default settings save feature for each format.
> When user choose one format, if it has saved preferences, it restored.
> It will also give users better convenience.
I also have this idea, but this behavior may confuse other users.
> 11. Why did you change minimum required OS X version number to 10.5 instead of
10.4?
> Is it caused by ruby script?
Because I don't have 10.4 environment now.
> 12. Service menu supports became more important on Snow Leopard.
> Because it officially forbidden 3rd party application's context menu hack.
Probably, only Automator support is enough. I'm implementing now.
I've fixed 7zip bug. The fixed version will be released soon.
> 1. Windows's Winzip tries to archive all filenames even though some of them
can't be converted into specific codepage(such as CP932).
I see. I will try the compatible way.
> Info-zip save unix-related extra zip fields into archive file such GID, UID,
etc. It sometimes interferes to read archive file properly in windows zip
applications such as 7zip, winrar, etc.
Hmm. CleanArchiver don't have idea of 'Windows compatible'. But discarding
UID, GID, etc. may be reasonable because Mac OS X users don't mind such
infomation. If they are needed, I think gzip or bzip2 are usually used.
> 3. Info-zip 3.0b has a feature about resource fork support, but it didn't
implemented completely.
Really!? I'll disable resource fork support in zip.
> 4. In case of libiconv, it don't care about over U+10000 Unicode codepoint.
So you might use one of the normalize functions than 'iconv(UTF-8, UTF-8-MAC)'.
Yes. I remember it. I would like to support over U+10000 characters, but they
are rare and this support is low priority now.
> 5. I confirmed that 'Icon\r' is still to use.
>So how about combine options such as 'exclude .DS_Store', 'exclude Icon\r' and
'discard resource fork' into 'exclude Mac-specific files'?
I can't find 'Icon\r' on Mac OS X 10.5 and I think 'Exclude Icon\r' is no
longer necessary. This file exists on 10.5?
And I can't combine all exclude options because exists the case I want to save
resource forks but delete .DS_Stores when creating Disk Images.
> 6. I wondered 'Internet enabled DMG' is still working.
> The reason I remove it in my modifed version is that.
> I couldn't find the difference between the option was on and off.
Indeed, I don't find internet-enable disk images recently...
> 7. I think compression level has 'store - not compress' method.
> Some big files such as movie clip are no need to compress.
> Some users maybe want it.
gzip and bzip2 don't support 'store' method and I don't like to add format
specific options though such options already exist... It may return.
> 8. Why did you get rid of archive split option?
> I know that info-zip split method are not used broadly, and 7zip's one is same
as unix's split command feature.
> But users want to this function using easily GUI method.
Because I think it is used rarely. I'd like to keep GUI simple.
> 9. What is the reason that 'more options' was removed?
> I thought it might be helpful for power-user who wants more elaborate
configuration.
> For example, 7zip option '-mhe=on' is enable filename encryption.
Likewise. CleanArchiver call external commands now, but CleanArchiver don't
have to do so and this implementation may be changed.
> 10. I added default settings save feature for each format.
> When user choose one format, if it has saved preferences, it restored.
> It will also give users better convenience.
I also have this idea, but this behavior may confuse other users.
> 11. Why did you change minimum required OS X version number to 10.5 instead of
10.4?
> Is it caused by ruby script?
Because I don't have 10.4 environment now.
> 12. Service menu supports became more important on Snow Leopard.
> Because it officially forbidden 3rd party application's context menu hack.
Probably, only Automator support is enough. I'm implementing now.
> I've fixed 7zip bug. The fixed version will be released soon.
It's nice of you. Thanks for hard-working.
> Hmm. CleanArchiver don't have idea of 'Windows compatible'. But discarding
> UID, GID, etc. may be reasonable because Mac OS X users don't mind such
> infomation. If they are needed, I think gzip or bzip2 are usually used.
I mean that users maybe want to archive files using encoding conversion for
Windows. At that time is when 'windows compatible' feature would be needed.
I can't say always use the option.
> Really!? I'll disable resource fork support in zip.
Actually, it don't store metadata, which is generally stored in '._*' files
in zip archive. If you have a time, test with some files.
The method is simple, you need to tag files using openmeta tool or find some
already tagged file, and then archive them with '-as' option. And then extract
it using OS X Archive Utility. Finally you will find metadata have been removed.
As a result, we need to fix info-zip's resource fork part later, if you want
to use it.
> I can't find 'Icon\r' on Mac OS X 10.5 and I think 'Exclude Icon\r' is no
> longer necessary. This file exists on 10.5?
Sure, you can find it easily.
If you have XCode, just enter 'ls -lb /Developer/Icon*'.
So I combined 'exclude Icon\r' and 'exclude .DS_Store' into one option.
> Because I don't have 10.4 environment now.
You can use environment value or option to make the link using specific SDK
version.
For example, I use
'-mmacosx-version-min=10.4'
'-isysroot /Developer/SDKs/MacOSX10.4u.sdk'
option in gcc to make 10.4 compatible binary.
But if you want some nice feature only available on higher version,
you have to use it.
It's nice of you. Thanks for hard-working.
> Hmm. CleanArchiver don't have idea of 'Windows compatible'. But discarding
> UID, GID, etc. may be reasonable because Mac OS X users don't mind such
> infomation. If they are needed, I think gzip or bzip2 are usually used.
I mean that users maybe want to archive files using encoding conversion for
Windows. At that time is when 'windows compatible' feature would be needed.
I can't say always use the option.
> Really!? I'll disable resource fork support in zip.
Actually, it don't store metadata, which is generally stored in '._*' files
in zip archive. If you have a time, test with some files.
The method is simple, you need to tag files using openmeta tool or find some
already tagged file, and then archive them with '-as' option. And then extract
it using OS X Archive Utility. Finally you will find metadata have been removed.
As a result, we need to fix info-zip's resource fork part later, if you want
to use it.
> I can't find 'Icon\r' on Mac OS X 10.5 and I think 'Exclude Icon\r' is no
> longer necessary. This file exists on 10.5?
Sure, you can find it easily.
If you have XCode, just enter 'ls -lb /Developer/Icon*'.
So I combined 'exclude Icon\r' and 'exclude .DS_Store' into one option.
> Because I don't have 10.4 environment now.
You can use environment value or option to make the link using specific SDK
version.
For example, I use
'-mmacosx-version-min=10.4'
'-isysroot /Developer/SDKs/MacOSX10.4u.sdk'
option in gcc to make 10.4 compatible binary.
But if you want some nice feature only available on higher version,
you have to use it.
> I mean that users maybe want to archive files using encoding conversion for
> Windows. At that time is when 'windows compatible' feature > would be needed.
I think encoding conversion is just encoding conversion and it is not for
particular operating system. In this meaning, discarding UNIX meta-data support
may be unnecessary.
> Sure, you can find it easily.
> If you have XCode, just enter 'ls -lb /Developer/Icon*'.
> So I combined 'exclude Icon\r' and 'exclude .DS_Store' into one option.
I've found it...
Icon\r is similar to resource forks. I don't want to exclude it when I create
Disk Images though I want to exclude .DS_Stores. So 'Discard resource forks'
and 'Exclud Icon Files' should be combined if I combine options.
> You can use environment value or option to make the link using specific SDK
version.
I don't feel like to release software for not tested OS X version and what I
mind is not whether it can be compiled or not. (Probably, it works on 10.4,
too.)
> Windows. At that time is when 'windows compatible' feature > would be needed.
I think encoding conversion is just encoding conversion and it is not for
particular operating system. In this meaning, discarding UNIX meta-data support
may be unnecessary.
> Sure, you can find it easily.
> If you have XCode, just enter 'ls -lb /Developer/Icon*'.
> So I combined 'exclude Icon\r' and 'exclude .DS_Store' into one option.
I've found it...
Icon\r is similar to resource forks. I don't want to exclude it when I create
Disk Images though I want to exclude .DS_Stores. So 'Discard resource forks'
and 'Exclud Icon Files' should be combined if I combine options.
> You can use environment value or option to make the link using specific SDK
version.
I don't feel like to release software for not tested OS X version and what I
mind is not whether it can be compiled or not. (Probably, it works on 10.4,
too.)
All right.
I might have a different view to CleanArchiver.
And I don't mind to say that you must follow it.
So I will keep the fork version of CleanArchiver for another users.
Would I do this continually, please?
I might have a different view to CleanArchiver.
And I don't mind to say that you must follow it.
So I will keep the fork version of CleanArchiver for another users.
Would I do this continually, please?
> Really!? I'll disable resource fork support in zip.
I've misunderstood in it.
Actually, legacy ways of accessing resource fork by adding postfix '/rsrc' and
'/..namedfork/rsrc' are still alive in OS X 10.5.
I don't know whether it is worked in 10.6
But other metadata such as spotlight comments or others are not stored with
above method except only resource fork.
If you just want to archive resource fork only, use info-zip's '-as' option.
Anyway, what kind of program still use old-fashioned resouce fork nowadays? I'm
just curious.
I've misunderstood in it.
Actually, legacy ways of accessing resource fork by adding postfix '/rsrc' and
'/..namedfork/rsrc' are still alive in OS X 10.5.
I don't know whether it is worked in 10.6
But other metadata such as spotlight comments or others are not stored with
above method except only resource fork.
If you just want to archive resource fork only, use info-zip's '-as' option.
Anyway, what kind of program still use old-fashioned resouce fork nowadays? I'm
just curious.
> All right.
> I might have a different view to CleanArchiver.
> And I don't mind to say that you must follow it.
> So I will keep the fork version of CleanArchiver for another users.
> Would I do this continually, please?
Sure. You can do freely under the license.
It is the Open Source, isn't it?
I think what one want to use should be created (or extended) by him.
But I think our views are not so different.
I don't tell that split archive support is unnecessary, for example.
I need simply more time to consider what is better for CleanArchiver.
The main window is too small to do all things in it.
How it works is more important than what it can do for me.
----
> But other metadata such as spotlight comments or others are not stored with
above method except only resource fork.
Actually, I can't delete all metadata with 'cat < /dev/null > file/rsrc'
command.
'@' attribute in 'ls -l' doesn't disappear in this way.
Some metadata seems to be left yet.
> I might have a different view to CleanArchiver.
> And I don't mind to say that you must follow it.
> So I will keep the fork version of CleanArchiver for another users.
> Would I do this continually, please?
Sure. You can do freely under the license.
It is the Open Source, isn't it?
I think what one want to use should be created (or extended) by him.
But I think our views are not so different.
I don't tell that split archive support is unnecessary, for example.
I need simply more time to consider what is better for CleanArchiver.
The main window is too small to do all things in it.
How it works is more important than what it can do for me.
----
> But other metadata such as spotlight comments or others are not stored with
above method except only resource fork.
Actually, I can't delete all metadata with 'cat < /dev/null > file/rsrc'
command.
'@' attribute in 'ls -l' doesn't disappear in this way.
Some metadata seems to be left yet.
Thanks for your answer.
I intended to support exchanging files between Windows & Linux and Mac without
any encoding problem.
So I want to make a archive file which is extracted well with archive
applicatons in Windows and Linux platform.
As a result, I specially concentrate on supporting Unicode normalization
filenames in archive application.
Because there are a lot of archive applications on OS X( also much more in
Windows), but many of them haven't fitted my purpose.
So I've suggested Winrar, 7zip, info-zip developer to support these
compatibility, but some of them think it's a trivial issue or will be considered
later as minority users use it currently.
And I started to do it by myself.
It's a modified version of CleanArchiver.
----
> Actually, I can't delete all metadata with 'cat < /dev/null > file/rsrc'
command.
> '@' attribute in 'ls -l' doesn't disappear in this way.
> Some metadata seems to be left yet.
I can't understand your meaning. I know what the command result is, but the
entire your intention.
I mean that other metadata such as 'com.apple.metadata' or
'com.apple.quarantine' are not stored with info-zip archive.
Info-zip stores only 'com.apple.ResourceFork' metadata using 'filename/rsrc'
path method. It's old and limited to get full metadata.
So if it can be stored all metadata with datafork, it must be need to use
copyfile() function or getxattr() directly. find a manpage copyfile(3)
getxattr(2).
If you wonder it, you can test it simply.
1. get a one of openmeta related application.
http://code.google.com/p/openmeta/wiki/OpenMetaApplications
2. tag a some file using it. It will make some 'com.apple.metadata' metadata.
3. you can see metadata contents using 'xattr -l filenames'
4. zip the files using CleanArchiver with 'Save resource fork' option enabled.
5. extract it with basic OS X archive utility.
6. examine the files again with 'xattr -l filenames'
Actually I have a lot of thing to say, but I'm not a good English speaker.
Best regards.
I intended to support exchanging files between Windows & Linux and Mac without
any encoding problem.
So I want to make a archive file which is extracted well with archive
applicatons in Windows and Linux platform.
As a result, I specially concentrate on supporting Unicode normalization
filenames in archive application.
Because there are a lot of archive applications on OS X( also much more in
Windows), but many of them haven't fitted my purpose.
So I've suggested Winrar, 7zip, info-zip developer to support these
compatibility, but some of them think it's a trivial issue or will be considered
later as minority users use it currently.
And I started to do it by myself.
It's a modified version of CleanArchiver.
----
> Actually, I can't delete all metadata with 'cat < /dev/null > file/rsrc'
command.
> '@' attribute in 'ls -l' doesn't disappear in this way.
> Some metadata seems to be left yet.
I can't understand your meaning. I know what the command result is, but the
entire your intention.
I mean that other metadata such as 'com.apple.metadata' or
'com.apple.quarantine' are not stored with info-zip archive.
Info-zip stores only 'com.apple.ResourceFork' metadata using 'filename/rsrc'
path method. It's old and limited to get full metadata.
So if it can be stored all metadata with datafork, it must be need to use
copyfile() function or getxattr() directly. find a manpage copyfile(3)
getxattr(2).
If you wonder it, you can test it simply.
1. get a one of openmeta related application.
http://code.google.com/p/openmeta/wiki/OpenMetaApplications
2. tag a some file using it. It will make some 'com.apple.metadata' metadata.
3. you can see metadata contents using 'xattr -l filenames'
4. zip the files using CleanArchiver with 'Save resource fork' option enabled.
5. extract it with basic OS X archive utility.
6. examine the files again with 'xattr -l filenames'
Actually I have a lot of thing to say, but I'm not a good English speaker.
Best regards.
初めまして、OS10.6にて複数を個別にzip圧縮できないか悩んでいたところ、こちらのソフトにたどり着きました。
大変助かりました感謝いたします。
大変助かりました感謝いたします。
カレンダー
|
5月 '22 | |||||
| 月 | 火 | 水 | 木 | 金 | 土 | 日 |
| 1 | ||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| 9 | 10 | 11 | 12 | 13 | 14 | 15 |
| 16 | 17 | 18 | 19 | 20 | 21 | 22 |
| 23 | 24 | 25 | 26 | 27 | 28 | 29 |
| 30 | 31 | |||||
クイック サーチ
コメント
コメント:
日, 26.01.2014 15:12
コメント:
木, 02.06.2011 02:41
初めまして、OS10.6にて複数を個別にzip圧
縮できないか悩んでいたところ、こちらのソ
フトにたどり着きました。
大変助か [...]
カテゴリ
Powered by
