I18n bug: files with duplicate names are overwriten during extracting vue files

[freesrz93]

Description

Zettlr/scripts/split-vue-sfc.js

Lines 43 to 46 in 6ccd6f3

	const script = match[1]
	const basename = path.basename(absPath) + '.ts'
	const outPath = path.join(OUTDIR, basename)
	fs.writeFileSync(outPath, script, 'utf-8')

I noticed the path.basename here which caused ALL VUE files are extracted to LEVEL 1 of source/tmp. So files like source/**/App.vue will be extracted to the same target, and only the last one remained. That caused a lack of msgid in static/i18n.pot

Reproducing

e.g. Just search for advanced in i18n.pot and there's not a msgid matching it.

Zettlr Version

Right off the develop branch

Specify version

No response

Installation Method

None

Your Platform

• Windows
• macOS
• Linux

Architecture

• Intel 64bit
• ARM 64bit

Operating System Version

Windows 11

Additional Information

No response

[boring-cyborg]

Thanks so much for opening up your first issue here on the repository! 🎉
We would like to warmly welcome you to the community behind the app! ☺️
We'll check in soon and have a look at your issue. In the meantime, you can
check your issue and make sure it aligns with our contribution guidelines!
Here's the comprehensive list:

NOTE: Please do not share screen captures of buggy behavior on YouTube.
If you have uploaded a video on YouTube and linked it already, don't
worry! But, we would like to ask you to remove the video from YouTube
and upload it directly to GitHub instead, by editing your comment.
Read more here.

Enhancements

An enhancement takes a feature and improves or alters its behaviour. Please
make sure to argue how your proposition will aid non-technical text workers,
and why it can't be emulated easily with other features or apps!

Feature requests

Feature requests introduce whole new features into the app. This requires a
lot of work, so these might be turned down if the implementation costs
supersede the benefits we expect to see from implementing it. Please do not
be disappointed if that happens. It likely has nothing to do with your great
request but simply with us and our missing resources!

You can of course always ask someone to implement this feature, because a PR
with a working new feature has much higher chances of being merged! :)

Bug reports

Please note that one of the main reasons for why bug reports cannot be
addressed is that there's not enough information for us to find and fix the
bug you describe, so make sure you try to pinpoint the bug as close as
possible.

The ideal bug report for us has two qualities:

1. The bug is always reproducible, at least within a certain context.
2. We know exactly what specifically goes wrong, and there is consensus on
   what should happen instead.

Please note that if you encounter behaviour that does not align with your
expectations of what would happen, this might as well be simply intended
behaviour and we need to simply clarify why the behaviour is the way it is.
This is not to be considered a bug and such issues may be closed! Suggest an
enhancement instead!

But now, have a great day and thank you again!

[nathanlesage]

Good catch!