#866 Not possible to map remote content into arbitrary root-level folders

[Kos Ivantsov]

It's impossible to map project-related but non-OmegaT-specific remote content (for instance, reference PDF's or project instructions) into a local subfolder of the project root, if the subfolder is not one of the automatically created ones. OmegaT neither creates the specified folder, nor does it mirror the remote contents into already created one, even though it does fetch and store it locally in a respective folder under .repositories

If the same contents is mapped into dictionary, glossary, source, target, or tm subfolder, even if the destination is several levels deep, the mirroring happens, OmegaT creates all the necessary subfolders and puts the contents there.

<mapping local="reference" repository="/reference/"/> doesn't work, even if reference folder was created manually.
<mapping local="dictionary/level1/level2/level3/reference" repository="/reference/"/> works, even if dictionary was empty or deleted prior to adding this mapping.

It looks like a regression compared to the way non-OmegaT-specific files were treated in 3.x-compatible projects.

Ideally a repository mapped as / should be mirrored as is into <project_folder></project_folder>, so if it included <repository_root>/reference</repository_root>, there should be <project_folder>/reference</project_folder>

But if it's not possible or there are reason's not to do it, there still should be a possibility for explicit mapping into arbitrary user-specified folders.

[Alex Buloichik]

Code for copy all folders: RealProject.java:362 (loadProject method). Will change to copy all with exceptions.

[Alex Buloichik]

Need to have correct list of excluded folders for copy root project from repository. I found folders:
/.repositories
/target/
/omegat/
/omegat.project
Did I miss any OmegaT-related folder/files that should be controlled by OmegaT, and not be just a simple copy from repo to local ?

[Didier Briel]

/.repositories: of course it should be excluded.
/target/: probably yes, because it is supposed to be synchronised from local to repository.
/omegat/: it has to be treated specifically (because of project_save.tmx), but it must be possible to have any file copied from the repository, not just a predefined list.
/omegat.project: yes
/glossary/: it's similar to /omegat/. I.e., it must be possible to have any file copied, but the writeable glossary file must synchronised.

Didier

[Kos Ivantsov]

Hi all,

/target/: probably yes, because it is supposed to be synchronised from local
to repository.

It still should be possible to keep /target unversioned, or map it to a
different repository than the main one (the one that /omegat/project_save.tmx is
synchronised with).

--
Kos

[Didier Briel]

It still should be possible to keep /target unversioned,

Yes, that's a given, since I separated Create Target Documents and Commit Target Files [feature-requests:#1341]

[Kos Ivantsov]

It still should be possible to keep /target unversioned,

Yes, that's a given, since I separated synchronisation and Commit Target Files
[feature-requests:#1341]

I know, I'm only mentioning it as a reminder to keep it that way when the code
is reworked

[Alex Buloichik]

Please, see fix_866 branch in the git.

[Didier Briel]

Fixed in SVN (/trunk, [r10432]).

To get a folder, it has to contain at least an empty file (i.e., empty folders will not be downloaded).

Didier

[Didier Briel]

Closed in the released version 4.1.5 update 1 of OmegaT.

Didier