Frequently asked questions.
1 General Questions
1.1 What's behind the name
Applimizer?
1.2 What
happened to Applimiser?
1.3 You have misspelled
optimization.
1.4 My
browser does not display your web pages.
2 Window Information
2.1 Why are the sizes different
from the sizes in the Finder?
2.2 Why are some languages shown
in red color or are underlined?
2.3 How can I see the complete list
of applications in the summary view?
2.4 How can I see the complete list
of languages in the main window?
3
Run-time
3.1 What
happens during analysis?
3.2 How can I speed up the
analysis phase?
3.3
Is optimization as slow as analysis?
4 Optimization
4.1
Which optimization strategies does Applimizer use?
4.2 How does HTML optimization
work?
4.3 How do I
specify which language localizations to remove?
4.4 What is the ISO language code
for my language?
4.5 Does Applimizer update the
language settings in the System Preferences?
4.6 How do I deselect a language
in the list?
4.7
What happens to the optimized files?
4.8 Is it worth optimizing when
only a few percentages can be gained?
4.9 Does Applimizer always optimize
all files?
5 Known Problems with
Applications
5.1
Acrobat Distiller (Adobe)
5.2 Backup (Apple)
5.3 Installer (Apple)
5.4 Safari (Apple)
5.5 ToyViewer
6 Contacting tredje design
6.1 How can I become a beta
tester?
6.2 When will
Applimizer become available in my language?
6.3 I think I found a bug. What
should I do?
6.4 My
question is still unanswered. What can I do now?
Applimizer is derived from the words "Application" and "Optimizer".
Applimiser (with an "s") is the original version which was developed for British English (en_GB). It still exists. However, you will not see it unless your preferred Mac OS X system language is set to "British English" (or it is listed above "English").
No I didn't. Applimiser is also localized for British English. You are properly using British English (en_GB) as you preferred language (see the International pane in the System Preferences). Optimization is therefore correctly spelled with an "s".
Use Safari.
The numbers reflect two views of the same thing: Whereas the Finder reports the space that an item occupies on the disk, Applimizer reports the actual size of the files. You can verify this in the Finder's Info window.
This is additional information regarding the language de-localization.
A black color indicates that a language is not to be removed.
A red color denotes that a language will be removed when you run the optimization.
Additionally, a language may be underlined. This is the language in which an application was designed, that is the development language. In the summary view, more than one language may be underlined if you have analyzed several applications. In principle, the development language can also be removed - it would then be shown in red. However, there is an additional switch in the options window with which you can indicate that this language should always be kept.
If you cannot see all application names, you can resize the window. Alternatively, you can also rest your mouse over the list; a help tag appears with the complete list.
There is a limit on how many languages can be listed in the main window. To see the complete list of languages, rest your mouse over the list; a help tag appears with the complete list. NB. In the individual view, you can also resize the window to see all languages.
During analysis, all files inside an application bundle are processed. This includes embedded bundles, frameworks, or plug-ins. For each type of file, dedicated optimization strategies are applied. Since Applimizer is designed to give you an opportunity to see all the potential savings, all strategies must be run on a trial basis. In essence, Applimizer is executing all the optimization algorithms, but without saving any changes.
There is presently no option to speed up the analysis phase. You probably will not run Applimizer on a daily basis.
In general, optimization is faster than analysis. Depending on your optimization settings, some files are simply removed as opposed to optimized. This speeds up the process.
Example: An application has a French localization with 1000 Hypertext Markup Language (HTML) help documents. During analysis, all these HTML files are analyzed. If, during optimization, the French language localization were removed, then none of the HTML files need to be optimized; they are simply deleted.
Switching off an optimization technique in the options window also speeds up the optimization run-time.
The Applimizer User Guide describes all the techniques in detail.
The principle is quite simple: HTML contains many objects that do not print, for example comments and additional white space characters. These can be safely removed without changing the appearance of the document (more details).
Applimizer uses your global language settings as a start point, that is the languages that you have chosen in the International pane of the System Preferences.
To inspect the languages that Applimizer will keep, open the options window (click the Options button in the main window) and select the Languages tab. Any language not listed here is removed from an application during language optimization.
You can edit any language in the list simply by double-clicking it. You can enter either full language names (beware the spelling!) or ISO 639 or ISO 3166 language codes such as "en_US" or "en" for American English or English, respectively. Use the Add or Remove buttons to modify the list.
As mentioned in the paragraph above, you can specify your language of choice in the list of preferred languages through entering an ISO 639 or ISO 3166 language code.
Please note that one language may be expressed through more than one ISO code or name (separated by commas in the list). For instance, to define French as one of your languages, you could enter "fr" or "fr_FR" (or indeed "French" itself).
The codes that Applimizer supports are, in no particular order:
- en
- English
- en_US
- American English, U.S. English
- en_GB
- British English
- en_AU
- Australian English
- en_CA
- Canadian English
- en_HK
- Hong Kong English
- en_IN
- Indian English
- en_IR
- Irish English
- en_SG
- Singapore English
- fr, fr_FR
- French
- fr_CA
- Canadian French
- fr_CH
- Swiss French
- fr_BE
- Belgian French
- de, de_DE
- German
- de_AT
- Austrian German
- de_CH
- Swiss German
- it, it_IT
- Italian
- it_CH
- Swiss Italian
- nl, nl_NL
- Dutch
- nl_BE
- Flemish
- sv, sv_SE
- Swedish
- sv_FI
- Finnish Swedish
- es, es_ES
- Spanish
- es_AR
- Argentinian Spanish
- es_CL
- Chilean Spanish
- es_MX
- Mexican Spanish
- es_VE
- Venezuelan Spanish
- da, da_DK
- Danish
- pt, pt_PT
- Portuguese
- pt_BR
- Brazilian Portuguese
- no, no_NO
- Norwegian
- nb
- Norwegian Bokmal
- nn
- Norwegian Nynorsk
- he
- Hebrew
- ja, ja_JP
- Japanese
- ar
- Arabic
- fi, fi_FI
- Finnish
- el, el_GR
- Greek
- is, is_IS
- Icelandic
- mt
- Maltese
- tr, tr_TR
- Turkish
- hr, hr_HR
- Croatian
- zh
- Chinese
- zh_CN
- Simplified Chinese
- zh_TW
- Traditional Chinese
- ur
- Urdu
- hi
- Hindi
- th
- Thai
- ko
- Korean
- lt
- Lithuanian
- pl, pl_PL
- Polish
- hu, hu_HU
- Hungarian
- et
- Estonian
- lv
- Latvian
- se
- Sami
- fo
- Faroese
- fa
- Farsi
- ru, ru_RU
- Russian
- ga
- Irish Gaelic, Gaeilge
- sq
- Albanian
- ro, ro_RO
- Romanian
- cs, cs_CZ
- Czech
- sk, sk_SK
- Slovak
- sl, sl_SI
- Slovenian
- yi
- Yiddish
- sr
- Serbian
- mk
- Macedonian
- bg
- Bulgarian
- uk, uk_UA
- Ukrainian
- be
- Byelorussian
- uz
- Uzbek
- kk
- Kazakh
- az
- Azerbaijani
- hy
- Armenian
- ka
- Georgian
- mo
- Moldavian
- ky
- Kirghiz
- tg
- Tajiki
- tk
- Turkmen
- mn
- Mongolian
- ps
- Pashto
- ku
- Kurdish
- ks
- Kashmiri
- sd
- Sindhi
- bo
- Tibetan
- ne
- Nepali
- sa
- Sanskrit
- mr
- Marathi
- bn
- Bengali
- as
- Assamese
- gu
- Gujarati
- pa
- Punjabi
- or
- Oriya
- ml
- Malayalam
- kn
- Kannada
- ta
- Tamil
- te
- Telugu
- si
- Sinhalese
- my
- Burmese
- km
- Khmer
- lo
- Lao
- vi
- Vietnamese
- id
- Indonesian
- tl
- Tagalog
- ms
- Malay
- am
- Amharic
- ti
- Tigrinya
- om
- Oromo
- so
- Somali
- sw
- Swahili
- rw
- Kinyarwanda
- rn
- Rundi
- mg
- Malagasy
- eo
- Esperanto
- cy
- Welsh, Gymraeg
- eu
- Basque
- ca
- Catalan
- la
- Latin
- qu
- Quechua
- gn
- Guarani
- ay
- Aymara
- tt
- Tatar
- ug
- Uighur
- dz
- Dzongkha
- jv
- Javanese
- su
- Sundanese
- gl
- Galician
- af
- Afrikaans
- br
- Breton
- iu
- Inuktitut
- gd
- Scottish, Gaelic
- gv
- Manx, Gaelg
- to
- Tongan
- kl
- Greenlandic
If your language were not on this list, let me know and I shall add it.
No. Any changes that you make to the list of preferred languages in the options window only affect Applimizer; your global language settings in the System Preferences are not changed.
Command-click the selected language to deselect it.
This depends on the type of optimization:
Remember that a backup of the application can be made (see user guide).
Probably not. This is why Applimizer presents the optimization statistics to you before any changes are made. You can then judge for yourself.
If only a few percentages can be saved, then the disk space used by an application might not change much, or even not at all. For instance, if a small file, were optimized from 6.5 KB (kilobyte) to 6.0 KB, then it would still occupy 8 KB of disk space.
As mentioned in the paragraph above, small files might still use the same disk space, even after optimization. In the Mac OS Extended disk format, the minimum disk space used by a file is 4 KB. By default, Applimizer does therefore not optimize files that are smaller than 4 KB. However, since version 1.3, you can override this through a switch in the options window.
Should not be optimized with Applimizer, but language-optimization may work.
Don't run HTML optimzation.
Never ever remove the English localization! May best be left alone.
Don't run HTML optimization.
Do not optimize ToyViewer as it will crash Applimizer!
Simple, please contact me.
The localization process requires sufficient knowledge of your language, which I may not have. If you would like to help, please contact me.
Please send an email to tredje.bugreport@mailnull.com (don't put this address in your address book as it is temporary), or use the online contact form.
The following information would be helpful:
Why don't you post your question on this contact form?
