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
Thank you @AhmedZaghloul19. Although remove the header is a possible workaround, I think a better solution could be ignore the comment if there is an empty new line between the string and the comment.
I do not think we can rely on the fact that the first comment in a localisation file can be ignored because it could be the documentation information for the first localized key.
In a .strings files, comments are here to given context information for a key. I think that using comments to provide a "file header" like in some source code may not a good practice in this context (even if Xcode generate this header on file creation...).
The best option right now is to follow @AhmedZaghloul19 suggestion.
Otherwise, we would gladly accept any contribution to handle this case if you manage to implement this.
I have a simple Tutorial.strings file
My generated Strings+Generated.strings file contains the file header as comment of the first localization.
The text was updated successfully, but these errors were encountered: