Open BafDyce opened 7 years ago
Good idea! I'll review and merge your PR ASAP. Thanks.
Just a quick thought I had in the morning: It might be more suitable if I'd do the string manipulation inside the \newcommand
(line 288) instead of where I've included it right now.
The current approach would require the same if-else structure whenever we want to do something with \homepage
. (so, e.g. if someone would like to include the information somewhere else in the cv again he'd need to copy the code). I think it would be cleaner to modify the command so that it takes one argument and provides two named arguments (e.g. \@homepageUrl
and \@homepageText
). I'm just not 100% sure if this will work as I expect.
However, I can try to do this in the afternoon?
Will this fix the bug where https:// is rewritten to https//? The colon is removed for some reason in the linked URL, which causes a DNS resolver issue.
Up to now, the template always inserted a 'http://' in the url for the \homepage{} attribute. Therefore, it was not possible to specify 'https://example.com' as this would have resulted in 'http://https://example.com'.
The new approach allows to specify the homepage-url in any of the following ways (which will result in the specified strings)
Note that the third row is equivalent to the current behavior.