Replies: 1 comment
-
Yohh, thank you so much for this to consider. In general I am a big fan of keeping the UI as simple and clean as possible. So my preferences are always having setting options to be able to use the software as I need it. In case of renaming I would suggest the following:
In this case a setting would not be needed in my opinion but I would enjoy to have the possiblity to say "EnableWorkingWithoutSymbols" (if it is used my most of the user maybe the default value is true?) to avoid mistakes in the heat of the battle ^^ |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This discussion was originally started in #326, but moved here until we settle on how to to with this topic.
Background
The
NAB: Refresh XLF files from g.xlf
command was the first command I built in this extension, and the name for this command was just a working name. After a while I was used to that command, so I didn't think of renaming it before publishing the extension on VS Marketplace... The name has annoyed me more than once since then...Some time later I build the
NAB: Update g.xlf
for users that don't have symbols available, using VSCode only for translation. After that command was run, they executeNAB: Refresh XLF files from g.xlf
.After yet some more time I got request for a command that did both
NAB: Update g.xlf
andNAB: Refresh XLF files from g.xlf
in a single command. That ended up withNAB: Update all XLF files
.Issue
Now it seems as if the
NAB: Update all XLF files
is used by mistake by quite a few users, that actually should use the good oldNAB: Refresh XLF files from g.xlf
command.Why is this an issue?
The functionality in NAB AL Tools to update the g.xlf file is done by a custom code parser that tries to identify all code that should generate translation units in the xlf files. This parser will never be as good as the native AL Compiler (alc.exe), since it's just built by a lot of regex matching. There are a lot of different, more or less strange, formatting of code that this regex matching will fail to identify - even if we are trying to improving it when issues are reported.
Suggestions to resolve issue
NAB: Update all XLF files
NAB: Refresh XLF files from g.xlf
toNAB: Update Localization Files (XLF)
NAB: Refresh XLF files from g.xlf
command that shows an error that the user instead should useNAB: Update Localization Files (XLF)
NAB: Update g.xlf
toNAB: Update g.xlf from source code
NAB: Update g.xlf from source code
is executed, the user is prompted to executeNAB: Update Localization Files (XLF)
automatically.Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions