[Bf-docboard-svn] bf-manual-translations: [5649] trunk/blender_docs/locale/fr/LC_MESSAGES/render: (fr) removing empty fuzzy pragma
Daniel Thonon
noreply at blender.org
Sun Nov 15 23:52:53 CET 2020
Revision: 5649
https://developer.blender.org/rBMT5649
Author: dthonon
Date: 2020-11-15 23:52:53 +0100 (Sun, 15 Nov 2020)
Log Message:
-----------
(fr) removing empty fuzzy pragma
Modified Paths:
--------------
trunk/blender_docs/locale/fr/LC_MESSAGES/render/cycles/gpu_rendering.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/cycles/object_settings/adaptive_subdiv.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/cycles/object_settings/cameras.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/cycles/optimizations/reducing_noise.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/cycles/render_settings/film.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/cycles/render_settings/simplify.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/alpha.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/color.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/geometry.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/alpha/along_stroke.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/alpha/crease_angle.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/alpha/curvature_3d.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/alpha/distance_from_camera.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/alpha/distance_from_object.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/alpha/index.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/alpha/material.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/alpha/noise.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/alpha/tangent.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/color/along_stroke.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/color/crease_angle.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/color/curvature_3d.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/color/distance_from_camera.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/color/distance_from_object.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/color/index.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/color/material.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/color/noise.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/color/tangent.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/geometry/2d_offset.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/geometry/2d_transform.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/geometry/backbone_stretcher.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/geometry/bezier_curve.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/geometry/blueprint.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/geometry/guiding_lines.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/geometry/index.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/geometry/perlin_noise_1d.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/geometry/perlin_noise_2d.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/geometry/polygonization.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/geometry/sampling.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/geometry/simplification.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/geometry/spatial_noise.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/modifiers/geometry/tip_remover.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/strokes.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/texture.po
trunk/blender_docs/locale/fr/LC_MESSAGES/render/freestyle/parameter_editor/line_style/thickness.po
Modified: trunk/blender_docs/locale/fr/LC_MESSAGES/render/cycles/gpu_rendering.po
===================================================================
--- trunk/blender_docs/locale/fr/LC_MESSAGES/render/cycles/gpu_rendering.po 2020-11-15 22:41:31 UTC (rev 5648)
+++ trunk/blender_docs/locale/fr/LC_MESSAGES/render/cycles/gpu_rendering.po 2020-11-15 22:52:53 UTC (rev 5649)
@@ -4,7 +4,6 @@
# package.
# FIRST AUTHOR <EMAIL at ADDRESS>, 2019.
#
-#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Blender 2.82 Manual 2.82\n"
@@ -370,448 +369,3 @@
"An unknown error can have many causes, but one possibility is that it is "
"a time-out. See the above answer for solutions."
msgstr ""
-
-#~ msgid "Brachend Path Tracing"
-#~ msgstr ""
-
-#~ msgid "NVIDIA"
-#~ msgstr ""
-
-#~ msgid ""
-#~ ":abbr:`CUDA (Compute Unified Device "
-#~ "Architecture)` and Optix are supported "
-#~ "for GPU rendering with *NVIDIA* graphics"
-#~ " cards."
-#~ msgstr ""
-
-#~ msgid ""
-#~ "CUDA requires graphics cards with "
-#~ "compute capability 3.0 and higher. To"
-#~ " make sure your GPU is supported, "
-#~ "see the `list of NVIDIA graphics "
-#~ "cards <https://developer.nvidia.com/cuda-gpus>`__ "
-#~ "with the compute capabilities and "
-#~ "supported graphics cards. CUDA GPU "
-#~ "rendering is supported on Windows, "
-#~ "macOS, and Linux."
-#~ msgstr ""
-
-#~ msgid ""
-#~ "Optix requires Geforce or Quadro RTX "
-#~ "graphics card with recent NVIDIA "
-#~ "drivers, and is supported on Windows "
-#~ "and Linux."
-#~ msgstr ""
-
-#~ msgid ""
-#~ ":abbr:`OpenCL (Open Computing Language)` is"
-#~ " supported for GPU rendering with "
-#~ "*AMD* graphics cards. Blender supports "
-#~ "graphics cards with :abbr:`GCN (Graphics "
-#~ "Core Next)` generation 2 and above. "
-#~ "To make sure your GPU is "
-#~ "supported, see the `list of GCN "
-#~ "generations "
-#~ "<https://en.wikipedia.org/wiki/Graphics_Core_Next#Iterations>`__ "
-#~ "with the GCN generation and supported"
-#~ " graphics cards."
-#~ msgstr ""
-
-#~ msgid "What renders faster, NVIDIA or AMD, CUDA or OpenCL?"
-#~ msgstr ""
-
-#~ msgid ""
-#~ "Currently NVIDIA with CUDA is rendering"
-#~ " fastest, but this really depends on"
-#~ " the hardware you buy. Currently, "
-#~ "CUDA and OpenCL are about the same"
-#~ " in the newest mid-range GPUs. "
-#~ "However, CUDA is fastest in the "
-#~ "respect of high-end GPUs."
-#~ msgstr ""
-
-#~ msgid ""
-#~ "In case of problems, be sure to"
-#~ " install the official graphics drivers "
-#~ "from the NVIDIA or AMD website, or"
-#~ " through the package manager on "
-#~ "Linux."
-#~ msgstr ""
-
-#~ msgid ""
-#~ "This error may happen if you have"
-#~ " a new NVIDIA graphics card that "
-#~ "is not yet supported by the "
-#~ "Blender version and CUDA toolkit you "
-#~ "have installed. In this case Blender "
-#~ "may try to dynamically build a "
-#~ "kernel for your graphics card and "
-#~ "fail."
-#~ msgstr ""
-
-#~ msgid "The NVIDIA OpenGL driver lost connection with the display driver"
-#~ msgstr ""
-
-#~ msgid ""
-#~ "Blender supports two different technologies"
-#~ " to render on the GPU depending "
-#~ "on the particular GPU manufacture."
-#~ msgstr ""
-
-#~ msgid ""
-#~ "While a graphics card is rendering, "
-#~ "it cannot redraw the user interface, "
-#~ "which makes Blender unresponsive. We "
-#~ "attempt to avoid this problem by "
-#~ "giving back control over the GPU "
-#~ "as often as possible, but a "
-#~ "completely smooth interaction cannot be "
-#~ "guaranteed, especially on heavy scenes. "
-#~ "This is a limitation of graphics "
-#~ "cards for which no true solution "
-#~ "exists, though we might be able to"
-#~ " improve this somewhat in the future."
-#~ msgstr ""
-
-#~ msgid ""
-#~ "There maybe be multiple causes, but "
-#~ "the most common is that there is"
-#~ " not enough memory on your graphics"
-#~ " card. Typically while using GPU "
-#~ "rendering the GPU can only use the"
-#~ " amount of memory that is on "
-#~ "the GPU. This is usually much "
-#~ "smaller then the amount of system "
-#~ "memory that the CPU uses. In the"
-#~ " case that the GPU runs out of"
-#~ " memory Blender will automatically try "
-#~ "to also use system and GPU memory."
-#~ " This has a performance impact but"
-#~ " it is still faster than using "
-#~ "CPU rendering. This feature does not "
-#~ "work on OpenCL rendering."
-#~ msgstr ""
-
-#~ msgid "What renders faster, Nvidia or AMD, CUDA or OpenCL?"
-#~ msgstr ""
-
-#~ msgid ""
-#~ "Currently Nvidia with CUDA is rendering"
-#~ " fastest, but this really depends on"
-#~ " the hardware you buy. Currently, "
-#~ "CUDA and OpenCL are about the same"
-#~ " in the newest mid-range GPUs. "
-#~ "However, CUDA is fastest in the "
-#~ "respect of high-end GPUs."
-#~ msgstr ""
-
-#~ msgid ""
-#~ "This usually means there is not "
-#~ "enough memory to store the scene "
-#~ "on the GPU. We can currently only"
-#~ " render scenes that fit in graphics"
-#~ " card memory, and this is usually "
-#~ "smaller than that of the CPU. See"
-#~ " above for more details."
-#~ msgstr ""
-
-#~ msgid ""
-#~ "One way to reduce memory usage is"
-#~ " by using smaller resolutions for "
-#~ "textures. For example, 8k, 4k, 2k, "
-#~ "and 1k image textures take up "
-#~ "respectively 256MB, 64MB, 16MB and 4MB"
-#~ " of memory."
-#~ msgstr ""
-
-#~ msgid ""
-#~ "To enable GPU rendering, go into "
-#~ "the :menuselection:`Preferences --> System -->"
-#~ " Cycles Render Devices`, and select "
-#~ "either *CUDA*, *Optix* or *OpenCL*. "
-#~ "Next, you must configure each scene "
-#~ "to use GPU rendering in "
-#~ ":menuselection:`Properties --> Render --> "
-#~ "Device`."
-#~ msgstr ""
-
-#~ msgid ""
-#~ ":abbr:`CUDA (Compute Unified Device "
-#~ "Architecture)` and Optix are supported "
-#~ "for GPU rendering with Nvidia graphics"
-#~ " cards."
-#~ msgstr ""
-
-#~ msgid "Optix"
-#~ msgstr ""
-
-#~ msgid ""
-#~ "For RTX graphics cards with hardware "
-#~ "ray tracing support (e.g. Turing), Optix"
-#~ " can be used for better performance."
-#~ " Optix support is still experimental "
-#~ "and does not yet support all "
-#~ "features, see below for details."
-#~ msgstr ""
-
-#~ msgid ""
-#~ "Optix requires Geforce or Quadro RTX "
-#~ "graphics card with recent Nvidia "
-#~ "drivers, and is supported on Windows "
-#~ "and Linux."
-#~ msgstr ""
-
-#~ msgid ""
-#~ "Optix support is experimental and does"
-#~ " not yet support the following "
-#~ "features:"
-#~ msgstr ""
-
-#~ msgid "Using CPU memory for bigger scenes"
-#~ msgstr ""
-
-#~ msgid ""
-#~ "There maybe be multiple causes, but "
-#~ "the most common is that there is"
-#~ " not enough memory on your graphics"
-#~ " card. Typically while using GPU "
-#~ "rendering the GPU can only use the"
-#~ " amount of memory that is on "
-#~ "the GPU. This is usually much "
-#~ "smaller than the amount of system "
-#~ "memory the CPU can access. With "
-#~ "CUDA and Optix devices, if the GPU"
-#~ " memory is full Blender will "
-#~ "automatically try to use system memory."
-#~ " This has a performance impact, but"
-#~ " will usually still result in a "
-#~ "faster render than using CPU rendering."
-#~ " This feature does not work for "
-#~ "OpenCL rendering."
-#~ msgstr ""
-
-#~ msgid "What renders faster, Nvidia or AMD, CUDA, Optix or OpenCL?"
-#~ msgstr ""
-
-#~ msgid ""
-#~ "CUDA requires graphics cards with "
-#~ "compute capability 3.0 and higher. To"
-#~ " make sure your GPU is supported, "
-#~ "see the `list of Nvidia graphics "
-#~ "cards <https://developer.nvidia.com/cuda-gpus>`__ "
-#~ "with the compute capabilities and "
-#~ "supported graphics cards. CUDA GPU "
-#~ "rendering is supported on Windows, "
-#~ "macOS, and Linux."
-#~ msgstr ""
-
-#~ msgid ""
-#~ "For RTX graphics cards with hardware "
-#~ "ray tracing support (e.g. Turing), OptiX"
-#~ " can be used for better performance."
-#~ " OptiX support is still experimental "
-#~ "and does not yet support all "
-#~ "features, see below for details."
-#~ msgstr ""
-
-#~ msgid ""
-#~ "There maybe be multiple causes, but "
-#~ "the most common is that there is"
-#~ " not enough memory on your graphics"
-#~ " card. Typically while using GPU "
-#~ "rendering the GPU can only use the"
-#~ " amount of memory that is on "
-#~ "the GPU. This is usually much "
-#~ "smaller than the amount of system "
-#~ "memory the CPU can access. With "
-#~ "CUDA and OptiX devices, if the GPU"
-#~ " memory is full Blender will "
-#~ "automatically try to use system memory."
-#~ " This has a performance impact, but"
-#~ " will usually still result in a "
-#~ "faster render than using CPU rendering."
-#~ " This feature does not work for "
-#~ "OpenCL rendering."
-#~ msgstr ""
-
-#~ msgid ""
-#~ "OptiX requires graphics cards with "
-#~ "compute capability 5.0 and higher. To"
-#~ " make sure your GPU is supported, "
-#~ "see the `list of Nvidia graphics "
-#~ "cards <https://developer.nvidia.com/cuda-gpus#compute>`__"
-#~ " Optix works best on RTX graphics "
-#~ "cards with hardware ray tracing support"
-#~ " (e.g. Turing and above). OptiX "
-#~ "support is still experimental and does"
-#~ " not yet support all features, see"
-#~ " below for details."
-#~ msgstr ""
-
-#~ msgid ""
-#~ "CUDA requires graphics cards with "
-#~ "compute capability 3.0 and higher. To"
-#~ " make sure your GPU is supported, "
-#~ "see the `list of Nvidia graphics "
-#~ "cards <https://developer.nvidia.com/cuda-gpus#compute>`__"
-#~ " with the compute capabilities and "
-#~ "supported graphics cards. CUDA GPU "
-#~ "rendering is supported on Windows, "
-#~ "macOS, and Linux."
-#~ msgstr ""
-
-#~ msgid ""
-#~ "OptiX requires Geforce or Quadro RTX "
-#~ "graphics card with recent Nvidia "
-#~ "drivers, and is supported on Windows "
-#~ "and Linux."
-#~ msgstr ""
-
-#~ msgid ""
-#~ "AMD OpenCL GPU rendering is supported"
-#~ " on Windows and Linux, but not "
-#~ "on macOS."
-#~ msgstr ""
-
-#~ msgid ""
-#~ "There maybe be multiple causes, but "
-#~ "the most common one is that there"
-#~ " is not enough memory on your "
-#~ "graphics card. Typically while using GPU"
-#~ " rendering the GPU can only use "
-#~ "the amount of memory that is on"
-#~ " the GPU. This is usually much "
-#~ "smaller than the amount of system "
-#~ "memory the CPU can access. With "
-#~ "CUDA and OptiX devices, if the GPU"
-#~ " memory is full Blender will "
-#~ "automatically try to use system memory."
-#~ " This has a performance impact, but"
-#~ " will usually still result in a "
-#~ "faster render than using CPU rendering."
-#~ " This feature does not work for "
@@ Diff output truncated at 10240 characters. @@
More information about the Bf-docboard-svn
mailing list