"No line found in Localizable.strings" — Tilde not expanded in the path argument about swiftgen HOT 9 CLOSED

Ha indeed I forgot to expand the ~ in the path. You can fix it by adding
some stringByExpandingTildeInPath in Sources/L10n/main.swift …
or use a path that doesn't contain ~ in the meantime

from swiftgen.

Thanks!

from swiftgen.

Reopening so I don't forget to add that stringByExpandingTildeInPath call in future versions.

from swiftgen.

Hi,

I'm also getting this issue, except that my path doesn't contain a tilde:
swiftgen-l10n Localizable.strings

// Generated using SwiftGen, by O.Halligon — https://github.com/AliSoftware/SwiftGen

import Foundation

// No line found in Localizable.strings

Do you have any idea what could go wrong? (I'm using brew's version (0.4.4))

from swiftgen.

The comment may actually be a bit misleading (I should change it one day) and is generated when there would not be any "case" generated, which could happen indeed if your Localizable.strings is empty, but also if the file is not found (because you mistyped the path or the relative path was not relative to what you thought maybe?), or if the file wasn't readable at all (access rights etc), …

I should probably generate a more explicit comment (or even generate a proper error / exit code maybe) to tell whether it's a "file not found" or "error reading file" or "no problem when reading file but no string found in it" etc.

from swiftgen.

That's strange:

# swiftgen-l10n Localizable.strin
Error: The file “Localizable.strin” couldn’t be opened because there is no such file.

# ls -l
total 16
-rw-r--r--  1 kevindelannoy  staff   244 Sep 26 15:43 InfoPlist.strings
-rw-r--r--@ 1 kevindelannoy  staff  3062 Sep 30 20:30 Localizable.strings

# swiftgen-l10n Localizable.strings
// Generated using SwiftGen, by O.Halligon — https://github.com/AliSoftware/SwiftGen

import Foundation

// No line found in Localizable.strings

I also tried to type in absolute path but I have the same result.

Also, Localisable.strings just contains "test" = "Test123";

from swiftgen.

Ah, very strange indeed. Is your Localizable.strings properly saved as a UTF-16 file, not an UTF-8 file? (as that's how Localizable.strings files are expected to be encoded by Xcode anyway)

(Note for self: add better error messages, including for cases where the was couldn't be read because of a bad encoding)

from swiftgen.

Yup, that was encoding!

Thanks @AliSoftware 👍

from swiftgen.

Closing as I opened dedicated issues for the UTF8 encoding problem (#21) and the tilde not expanded (#22)

from swiftgen.