Manual:Image administration/pt-br

Este arquivo descreve como MediaWiki lida e armazena imagens, e dá algumas informações sobre configuração.

O mesmo se aplica a qualquer outro tipo de arquivo que possa ser carregado. Uma vez que todos os arquivos são armazenados com um artigo correspondente no namespace imagem, e que é identificado como uma imagem. Antes de MediaWiki 1.14, a "Image:" namespace foi usado em vez disso. "Image:" is still retained as an alias for backward compatibility.

Carregamento e Uso de Imagens
Veja: Help:Images

Habilitar Carregamento de Imagens
Para carregar imagens, três condições devem ser conhecidas:


 * 1) O MediaWiki deve ter o envio ativado. Altere em  para true.
 * 2) O tipo de arquivo deve ser permitido. Mais informações:.
 * 3) O usuário deve estar em um grupo com o "upload" direito. Por padrão, isso é dado a todos os usuários conectados.

Imagens são enviadas com o Special:Upload.

Veja, '''

Parâmetros relevantes para a manipulação de imagens
Esses parâmetros são relevantes:



Thumb em imagens
MediaWiki prorrogando a sintaxe permite que imagens sejam automaticamente 'miniaturizadas' (verManual:Configuring file uploads para ajuda geral em arquivos uploads).

Uma imagem com thumb exige o ImageMagick ou GD library - nem fazem parte da instalação padrão do MediaWiki, embora algumas versões do PHP incluam o GD. ImageMagick é recomendado, uma vez que produz uma melhor qualidade nos thumbnails; ele pode ser baixado a partir de imagemagick.org. O GD está incluído em algumas versões do PHP, e Recomenda-se usar GD em sistemas Windows. Um download autônomo do GD está disponível a partir de libgd.org.

Em versões mais recentes isto não é necessário.

Se você utilizar o ImageMagick, definir como true em LocalSettings.php. Certifique-se de que o aponta para a variável (absoluta) localização do comando para converter a sua instalação e que o comando é executável pelo servidor. For example, Windows users will want to change the default to "C:\ImageMagick\convert.exe" (or similar).

To re-create old thumbnail files before you used ImageMagick you can use.

If rendering fails silently, check and increase.

GraphicsMagick can now also be used as an alternative to ImageMagick. You will need to set $wgImageMagickConvertCommand to the (absolute) location of the 'gm' command. E.g.:

$wgImageMagickConvertCommand = "/usr/bin/gm";

GIF
For thumbnailing GIF-Animations under windows, you need to install ImageMagick as described above.

SVG


MediaWiki supports SVG image rendering: if enabled, SVG images can be used like other image files — they will automatically be rendered as a PNG file and thumbnailed as needed on the fly. If you're on a shared host and no SVG renderer is pre-installed, you should probably ask your provider to install it for you.

Para ativar o suporte a SVG:


 * 1) Permitir upload de arquivos SVG no arquivo LocalSettings.php:   Note que o MediaWiki irá recusar arquivos SVG contendo JavaScript, por motivos de segurança.
 * To avoid a false positive, add  to the  file.
 * 1) ːSe você receber uma mensagem de erro dizendo o arquivo está corrompido, certifique-se que o tipo de detecção está funcionando corretamente.
 * 2) Add   to  and set the renderer you want to use.
 * Available options are ImageMagick, ImagickExt , sodipodi , inkscape , batik , rsvg , and imgserv.
 * Por exemplo:
 * 1) * librsvg is fast but not very accurate. It has a ridiculously large chain of dependencies, so you may not want to bother unless you have a repository that includes it and resolves the dependencies for you. The Wikimedia projects use rsvg.
 * 2) * Batik is the most accurate SVG renderer available, although its anti-aliasing is sometimes suboptimal. Its SVG parsing is more strict, causing it to reject "almost valid" SVG files that other renderers accept (e.g. commons:File:UbuntuCoF.svg). Batik relies on Java, and is much slower than rsvg, though this may not be a huge issue unless you're constantly adding SVG files. See SVG benchmarks. Requires a lot of work to get running, if not included in your distribution.
 * 3) * Inkscape also does an accurate job of SVGs, half the speed of rsvg, but was designed for interactive graphical use; however, it comes with inkview which is a viewer/converter program - it requires a writable home directory for the user it's run as. Since it will be running as user  or something similar, it will try to create   and   directories in the corresponding home directory, and will fail silently, crash or hang indefinitely if it is not able to. Inkscape is preferable to rsvg (a) on Windows (it comes as a standalone package) or (b) if you have important SVGs drawn in Inkscape that do not render correctly in rsvg. Inkscape has as complicated a dependency chain as librsvg &mdash; use only if it's in your distribution or available as a complete standalone package.
 * 4) * Sodipodi is the program Inkscape was forked from. The same considerations apply. Sodipod is no longer under active development.
 * 5) * Since version 6.x.x ImageMagick renders SVGs, but imperfectly. This is the default, but avoid it if possible. However, it does work. On Windows, $wgConvertPath must be set to avoid a conflict with Windows' own convert.exe. One simple alternative in this scenario is to add to LocalSettings.php the line, which also allows for spaces in the path.
 * 6) * The PHP Imagick extension supports SVG rendering, however the same considerations as for the regular ImageMagick apply.
 * 7) * The GD library is not capable of converting SVG images to the PNG format, at least according to Joen Asmussen's June 2008 NoScope blog.
 * 8) * Most current web browsers except Internet Explorer (until version 9) can display SVGs directly. Using librsvg to render SVGs to a PNG will give much more accurate results, as well as less bandwidth consumption. Direct SVG display is not supported in MediaWiki by default, unless you install NativeSvgHandler extension.
 * 1) * Most current web browsers except Internet Explorer (until version 9) can display SVGs directly. Using librsvg to render SVGs to a PNG will give much more accurate results, as well as less bandwidth consumption. Direct SVG display is not supported in MediaWiki by default, unless you install NativeSvgHandler extension.

Set  = false if SVG rendering is not needed and you wish to make your users download the svg file in order to view it.

Solução de problemas
If you see a blank square instead of SVG (Chrome) or no image at all (Firefox) and all PNG links lead to 404 error and you don't see any other error message anywhere please check variable. Setting it to false may make SVG transformation deferred always. Make sure that proc_open and symlink PHP methods are enabled (they may be disabled in php.ini for security or performance reasons).

JPEG (usando GD)
Simply add the following line to LocalSettings.php, this will cause auto fall back to GD library.

For errors with JPEG thumbnails, see JPEG (using GD).

TIFF
A geração de miniaturas de arquivos TIFF requer MediaWiki 1.15.0 ou posterior.


 * 1) Allow upload of TIFF files in the LocalSettings.php file:
 * 2) Add   to LocalSettings.php and set to either jpg or png to specify which type of thumbnail you wish to have generated.
 * 3) Making thumbnails of TIFF files may require system resources beyond those needed for thumbnailing JPEG, GIF, or PNG files. Consider appropriate settings for   and

Apagando imagens
Files, like wiki pages, can only be deleted by users with the " (delete)" permission ( by default). Deletion of files is done by deleting the associated description page (or by clicking the "" link in the "" table).

Apagando um revisão individual
Se um arquivo foi alterado, há um histórico de revisão dos arquivos que é exibido na página do artigo do arquivo. Cada revisão tem um link "". Se isso for clicado, a revisão e o arquivo serão excluídos.

Information about old revisions of files are stored in the table while information on old revisions of the pages are stored in the  table.

Restauração de imagens
Da MediaWiki na versão 1,8 até 1,10, arquivos excluídos de imagens/arquivos (e, portanto, sua restauração) está desabilitado por padrão, mas pode ser ativada por definição em: $wgSaveDeletedFiles = true.

Desde MediaWiki na versão 1,11, que é ativado por padrão, e $wgSaveDeletedFiles é desaprovado. Instead, the behavior is controlled by.

Information about deleted images are stored in the filearchive table.

Eliminação de arquivos arquivados
Since MediaWiki version 1.11, deleted images are still stored on the server by default. If you want to delete selected archived images, you can do so using the maintenance script. If you want to delete all of them completely, you can do that with the script. If you delete archived files, you can not undelete those files anymore.

Razões para excluir um arquivo
When choosing to delete a file, as described above, users will be asked to provide a reason for deletion. The available reasons can be edited on the MediaWiki:Filedelete-reason-dropdown of your wiki.

Data storage
Whenever an image is uploaded, several things are created:


 * 1) An article in the file namespace with the name of the file, e.g. File:MyPicture.png. This page is stored and can be edited like any other page.
 * 2) The file itself is stored in a folder on the file system with whitespaces merged and replaced with.
 * 3) If necessary and thumbnailing is available, thumbnailed versions of the file will be created when necessary (such as for the usage on the file description page. These are stored in the thumb directory of the image directory, in a separate directory for each main file.

If is enabled (by default), MediaWiki creates several subdirectories in the images directory.

The directory names are from the first two characters of the md5 hash of the final filename.

Folders
All image files are stored in a folder determined by (, by default).

Description of named image subfolders:


 * archive: This is the storage place for files that have been replaced by newer versions.
 * temp: used for temporary storage of files during image uploading. (Due to, these files may not always be automatically deleted)
 * thumb: Thumbnails (automatically generated) for the files. If these are deleted, they are automatically regenerated when needed.

Depending on the configuration, there may be additional image subfolders:
 * math: Folder to store your rendered TeX input, see also Manual:Enable TeX or Math.
 * x/xy: If  is set to true (which is the default), images will be stored in subfolders of the images, thus making file paths look like  . See  for more details on why this might be desired and how this system works.

Database tables

 * The file description page is stored as any page in the page, text, revision etc. tables
 * image table: Holds some metadata such as the size of the file and the upload date.
 * oldimage table: This is stores information for files that have been replaced with newer versions.
 * filearchive table: holds the information on the deleted files.
 * imagelinks table: Records what pages use a file.

Space usage
Files need considerably more space than articles. The following calculations assume a block size of 4KB with Linux/Unix servers.

The default setting is $wgHashedUploadDirectory = true.

Space requirements for all directories:


 * image directories: 0-f/x0-f: max. 16*16 = 256 directories = 256*4 KB = 1024 KB
 * archive directories: 0-f/x0-f: max. 16*16 = 256 directories = 256*4 KB = 1024 KB
 * thumb directories: 0-f/x0-f: max. 16*16 = 256 directories = 256*4 KB = 1024 KB
 * temp directories: 0-f/x0-f: max. 16*16 = 256 directories = 256*4 KB = 1024 KB

Therefore, the basic amount of space needed without any images uploaded is 4 MB in theory (although the directories are created only when needed).

For each file we need:
 * size of the original image file + 2 KB average overhead

For files that need to be thumbnailed:
 * size of the created thumbnail(s) + 2 KB average overhead (each)
 * directory for thumbnail (4KB) (each image has its own thumbnail directory)

Examples:
 * image 20778 Byte png (small size, no thumb): 24 KB for the image: Total 24 KB
 * image 123.000 Byte jpeg (big size, auto thumb): 124 KB for the image, 4KB for the thumb directory, 64 KB for the thumb: Total: 192 KB

File Access
Uploaded files are generally served directly by the web server, not through MediaWiki. While there may be a minimal level of security through obscurity with path encryption (eg. /c/c4/...) if $wgHashedUploadDirectory is set, the path can be calculated easily from the file name and does not provide true protection.

For limiting access to authorized users, see Image Authorization

Licensing
A feature of MediaWiki allows the Special:Upload Page to streamline licensing of images. Wikipedia's Upload Page has a Licensing drop down box below image summary. This feature is turned off in default MediaWiki. To turn this feature on a sysop needs to edit Licenses in the MediaWiki namespace (example: MediaWiki:Licenses). S/he can do this by going to the MediaWiki:Licenses page of their wiki and clicking 'create' or 'edit'.

The page MediaWiki:Licenses expects a certain format in a wiki list.

Line 1 will produce "License text" and substitute the license 1 template in the image page and transclude license 2.

Line 2 will show a greyed out header with text "Header 1:"

Line 3 will produce "Attribution ShareAlike 2.5" and transclude template cc-by-sa-2.5 on the image page.

For detailed real world example, see Wikipedia:MediaWiki:Licenses or Commons:MediaWiki:Licenses.

Foreign Repositories
It is possible to access files stored in foreign repositories, without needing to upload them to the wiki, by setting the $wgForeignFileRepos array. This feature offers several possibilities:
 * ForeignAPIRepo accesses files from a remote MediaWiki installation, such as Wikimedia Commons, through its API
 * ForeignDBRepo accesses files through a database, and is useful for creating wiki families
 * FSRepo accesses files from a local folder

In all cases, one would be able to embed files into a page using ordinary image syntax and specifying the name of the file in the foreign repository. Note that some of the above implementations are still experimental, and might not be suitable for production sites.

MediaWiki Version
This applies to:
 * MediaWiki 1.9.x and above
 * other versions not verified