|
2062.
|
|
|
Content Filters ![](/@@/translation-newline)
===============
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
en/help_topics/content-filters.txt:1
|
|
2063.
|
|
|
Content formats ![](/@@/translation-newline)
---------------
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
en/help_topics/content-filters.txt:4
|
|
2064.
|
|
|
Bazaar's content filtering allows you to store files in a different ![](/@@/translation-newline)
format from the copy in your working tree. This lets you, or your ![](/@@/translation-newline)
co-developers, use Windows development tools that expect CRLF files ![](/@@/translation-newline)
on projects that use other line-ending conventions. Among other things, ![](/@@/translation-newline)
content filters also let Unix developers more easily work on projects ![](/@@/translation-newline)
using Windows line-ending conventions, keyword expansion/compression, ![](/@@/translation-newline)
and trailing spaces on lines in text files to be implicitly stripped ![](/@@/translation-newline)
when committed.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
en/help_topics/content-filters.txt:7
|
|
2065.
|
|
|
To generalize, there are two content formats supported by Bazaar:
|
|
|
|
(no translation yet)
|
|
|
|
Located in
en/help_topics/content-filters.txt:16
|
|
2066.
|
|
|
* a canonical format - how files are stored internally ![](/@@/translation-newline)
* a convenience format - how files are created in a working tree.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
en/help_topics/content-filters.txt:18
|
|
2067.
|
|
|
![](/@@/translation-newline)
Format conversion ![](/@@/translation-newline)
-----------------
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
en/help_topics/content-filters.txt:21
|
|
2068.
|
|
|
The conversion between these formats is done by content filters. ![](/@@/translation-newline)
A content filter has two parts:
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
en/help_topics/content-filters.txt:25
|
|
2069.
|
|
|
* a read converter - converts from convenience to canonical format ![](/@@/translation-newline)
* a write converter - converts from canonical to convenience format.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
en/help_topics/content-filters.txt:28
|
|
2070.
|
|
|
Many of these converters will provide *round-trip* conversion, ![](/@@/translation-newline)
i.e. applying the read converter followed by the write converter ![](/@@/translation-newline)
gives back the original content. However, others may provide an ![](/@@/translation-newline)
asymmetric conversion. For example, a read converter might strip ![](/@@/translation-newline)
trailing whitespace off lines in source code while the matching ![](/@@/translation-newline)
write converter might pass content through unchanged.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
en/help_topics/content-filters.txt:31
|
|
2071.
|
|
|
![](/@@/translation-newline)
Enabling content filters ![](/@@/translation-newline)
------------------------
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
en/help_topics/content-filters.txt:38
|