You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Linux/Windows dual boot setup and would like to be able to sync the L2P from both OSes into the same directory. The problem is that the Linux is in English while the Windows is in German.
Check for the application language instead of the system language. Easy but might unexpectedly break other user's setups.
Check if the top level folders already exist in another language. This would lead to mixed-language L2P folders once new course rooms get synced. Plus, it might still result in duplication unless all Sync-my-L2P installations which access that folder get updated.
Add a folder language setting next to the download location setting. Ideally this should be stored in a hidden file in the L2P folder, similar to the idea from Make directories rename- and moveable #74, to ensure that the settings used by all Sync-my-L2P installations are identical.
To me option three looks the best as it is the only one that will not break any existing setups or lead to weirdnesses in the future.
The text was updated successfully, but these errors were encountered:
I have a Linux/Windows dual boot setup and would like to be able to sync the L2P from both OSes into the same directory. The problem is that the Linux is in English while the Windows is in German.
Since Sync-my-L2P checks for the system language to determine the top level folder names (e.g. "Lernmaterialien" vs "StructuredMaterials"), it would duplicate my the entire L2P folder if I would sync under Linux on top of the Windows-created folder.
https://github.com/Sync-my-L2P/Sync-my-L2P/blob/cdaf64c61f995e91018fed36ee3977657dc7fb74/utils.cpp#L156
Some possible solutions:
To me option three looks the best as it is the only one that will not break any existing setups or lead to weirdnesses in the future.
The text was updated successfully, but these errors were encountered: