PLEASE NOTE: the upgrades to this server, secure.csse.uwa.edu.au, have not yet been completed.
Hopefully the changes will be completed on THURSDAY 8th December.
Web-based programs, such as csmarks, cssubmit, and the help fora, will be unavailable at some time on Thursday 8th.
  It's UWAweek 49

help2003/help4407

This forum is provided to promote discussion amongst students enrolled in Open Source Tools and Scripting.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.

How do I ask a good question?
Displaying selected article
Showing 1 of 564 articles.
Currently 5 other people reading this forum.


 UWA week 17 (1st semester, week 8) ↓
SVG not supported

Login to reply

👍?
helpful
4:42pm Wed 27th Apr, Hanlin Z.

Hi sir, I do not 100% agree abbreviation for a country name is possible. If user try to search "Sudan", how the bash knows he/she is trying to search "Sudan" or "South Sudan"? As what u said, the bash will said multi hits, but it still not able to show user what they want (the info), since bash can not know it is a abbreviation or not. I have an idea that might solve this issue, try to find "Sudan" first, if there has a country called "Sudan" in the data set, the bash will show the info of "Sudan". otherwise, show info for other country which abbreviation matching "Sudan". but there will have another question, if we do so, when a user try to use "Sudan" as an abbreviation word, to search "South Sudan", not try to search "Sudan". at this time, the bash will match and return info of "Sudan" to the user. that is what they don't expect. so that is why i said I do not 100% agree abbreviation for a country name is possible, since always have some special cases might make ur program works to a wrong way.

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  1:17AM Sep 14 2022
Privacy policy