# Preface Windows is an after thought not a priority at my company
I am writing a script that will take an input parameter into the function. The strings are a POSIX based timezone string that contains both open and close parenthesis and either the plus or the minus symbol for the timezone offset value. What is the best way to handle these types of strings coming from the pipeline or as a parameter. Here are some examples of the strings.
Adak – HAST – (GMT/UTC -10)
Adak – HAST – (GMT/UTC -10) Daylight Savings Time
Anchorage – AKST – (GMT/UTC -9)
Anchorage – AKST – (GMT/UTC -9) Daylight Savings Time
Anguilla – AST – (GMT/UTC -4)
Antigua – AST – (GMT/UTC -4)
Araguaina – BRT – (GMT/UTC -3)
Argentina/Buenos_Aires – ART – (GMT/UTC -3)
Argentina/Catamarca – ART – (GMT/UTC -3)
Argentina/Cordoba – ART – (GMT/UTC -3)
Argentina/Jujuy – ART – (GMT/UTC -3)
Argentina/La_Rioja – ART – (GMT/UTC -3)
Argentina/Mendoza – ART – (GMT/UTC -3)
Argentina/Rio_Gallegos – ART – (GMT/UTC -3)
Argentina/Salta – ART – (GMT/UTC -3)
Argentina/San_Juan – ART – (GMT/UTC -3)
Argentina/San_Luis – WARST – (GMT/UTC -3)
Argentina/San_Luis – WARST – (GMT/UTC -3) Daylight Savings Time
Once the script receives this parameter string it will need to compare and match it to a table which ties it into the Microsoft equivalent Windows Server Time Zones. Of which there only seems to be 97.