Encoding Issue Fixed

[eshajena3]

🔖 PR Title:

Encoding issues across Student Announcement, Tech Notes & Other Sections

---

📄 Description:

This PR fixes character encoding issues where strange/broken characters (e.g., →, …) were appearing in:
Student Announcements page (mobile view)
Tech Notes section (Windows & mobile views, search placeholder text, and other areas)
The fix ensures proper encoding across pages, so all arrows, ellipses, and special characters render correctly on all devices.

• Bug Fix ✅

---

🧑‍💻 What changes were made?

• Replaced misencoded characters with proper equivalents.
• Ensured encoding consistency between mobile and Windows views.
• Make some changes to the College Notes where some words are missing, like Semester 1 and Semester 2 at the ECM Section

---

🖼️ Screenshot or Screen Recording (max 15 seconds)

BEFORE


AFTER

---

💡 Tech Stack Used:

• HTML / CSS

---

List of File Changed :

no. of files changed

Tech Notes, College Notes, Student Announcements, User Experience Table

These are sections that I have made changes to.

🔗 Issue Reference:

381

Closes #381

---

🧩 Contribution Type:

• Frontend 🎯

• Bug Fix 🐛

---

🙏 Additional Info (if any):

Fixed broken characters (→, …) caused by inconsistent encoding.

Verified fix on mobile and Windows views.

[vercel]

@eshajena3 is attempting to deploy a commit to the vaibhavbabele's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

👋 Hi @eshajena3, thank you for opening this Pull Request!
🔧 Please ensure the following:

• ✅ Resolve any merge conflicts, if they exist.make sure you have updated your local repo to avoid conflicts. and solve in your local repo. do not solve in github editor.try to solve in your local repo in vs code or any other editor.
• 🧾 Clearly mention the issue number you are solving (e.g., Fixes #issue_number).
• 📎 Please update your PR description if anything is unclear or incorrect.
• 📷 Attach a screenshot or screen recording of your fix.
• 💬 Kindly share the PR link in the Discord server manually for better tracking.
• if follow the guidelines and fit to project then label according to pr otherwise close the pr.

Happy Contributing! 🚀

[VAIBHAVBABELE]

Can you update more changes in website because it not consider for point only 4 changes.

[eshajena3]

Can you update more changes in website because it not consider for point only 4 changes.
You can reply like this:

Hi @VAIBHAVBABELE,
Thank you for the feedback . Sure, I can make more changes in the website as suggested.

[eshajena3]

HELLO! @VAIBHAVBABELE I have made this changes in the website ,like the UI Alignment issues, and the encoding characters
And also added the team section to privacy policy page.

BEFORE:

AFTER:

Any further changes required please let me know

[github-actions]

⚠️ Merge Conflict Detected!
Hi @eshajena3, your pull request currently has a merge conflict with the base branch. Please resolve the conflict so your PR can be merged.
---
## How to Resolve a Merge Conflict (Step-by-Step)
1. Checkout your PR branch:
bash git checkout issue-381-fix

  2. **Fetch the latest changes from the main branch:**
     ```bash
     git fetch origin
     git pull origin main
     ```
  
  3. **Git will show conflict markers in files with conflicts. Open those files, and manually edit them to resolve the differences. Conflict sections look like:**
     ```
     <<<<<<< HEAD
     Your changes
     =======
     Changes from base branch
     >>>>>>> main
     ```
  
  4. **After resolving the conflicts, mark them as resolved:**
     ```bash
     git add <file(s)-you-resolved>
     ```
  
  5. **Commit the resolution:**
     ```bash
     git commit -m "Resolve merge conflict"
     ```
  
  6. **Push your updated branch:**
     ```bash
     git push origin issue-381-fix
     ```
  
  ---
  
  🔗 [GitHub Docs: Resolving merge conflicts](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)
  
  If you need any help, please ask your mentors by replying here!
  
  ---
  
  *This is an automated message to help you resolve merge conflicts and get your PR ready for review. Thank you!*