#864 segmentation.conf and filters.xml not mirrored in team projects

[Kos Ivantsov]

When the repository mapped as / contains omegat/segmentation.conf and omegat/filters.xml under version control, these files are ignored when 4.1-compatible Team project is used. They never make it to <project_folder>/omegat/</project_folder>, even though they are fetched from the server and are stored in <project_folder>/.repositories/<main_repo>/omegat/</main_repo></project_folder>.

Mapping these two files directly to the expected local files or specifying them by <includes> doesn't have any effect. Mapping them into directory other than /omegat does mirror them:
<mapping local="dictionary/segmentation.conf" repository="/omegat/segmentation.conf"/> (which is useless, of course, but this way segmentation.conf does end up in dictionary folder).

This bug makes it impossible for PM to force the same segmentation rules to all the team members without using extra tools and asking other members to take additional steps.

[Didier Briel]

In 4.1.2 update 1, both omegat/segmentation.conf and omegat/filters.xml are copied correctly when using Download Team Project. Can you check again?

Didier

[Didier Briel]

Fixed in SVN (/trunk, rev. 10082).

segmentation.conf and filters.xml are systematically copied from the repository.

Now that this is fixed, alternatively to Download Team Project, it is possible to open a 4.x team project simply by putting omegat.project in an empty directory and opening it.

Didier

[Didier Briel]

Fixed in the released version 4.1.2 update 2 of OmegaT.

Didier